NEED HELP - EXCHANGE ACTIVESYNC (EAS) will not connect to Exchange Server

You don't need to use another computer, just follow the instructions in the link and you can do everything on the surface itself. If you already have the cert you can get it onto the surface through flash drive\email\skydrive and just install it, just make sure you install it to Trusted Root Certification Authorites, or the mail won't work.

Wow, there is a lot of misinformation on this board..... Surface does connect to Exchange and has since day 1. The problem is that you are using self signed certificates, and surface does not accept self signed certificates unless you install them yourself. This is done for security, it had nothing to do with joining domains or anything like that, there is no bug. Exchange mail has worked on my surface since October 26th. Make sure you install the cert under 

"Trusted Root Certification Authorities"

http://www.lonecpluspluscoder.com/2012/10/how-to-make-a-self-signed-ssl-certificate-work-with-windows-rts-mail-app-on-a-microsoft-surface-rt/

http://blog.brightpointuk.co.uk/adding-exchange-email-account-windows-rt

Hi KarlProp,

So I would just export the cert via Internet Explorer on my laptop and then install it on the Tablet via the instructions in the link? If that's the case, how do tell the tablet which file to use? There doesn't seem to be a folder / file structure to allow for a file to be saved.

Do you think this would also fix my inability to connect with Lync?

Thanks! If it works there will be more exclamation marks. :)

Wow, there is a lot of misinformation on this board..... Surface does connect to Exchange and has since day 1. The problem is that you are using self signed certificates, and surface does not accept self signed certificates unless you install them yourself. This is done for security, it had nothing to do with joining domains or anything like that, there is no bug. Exchange mail has worked on my surface since October 26th. Make sure you install the cert under 

"Trusted Root Certification Authorities"

http://www.lonecpluspluscoder.com/2012/10/how-to-make-a-self-signed-ssl-certificate-work-with-windows-rts-mail-app-on-a-microsoft-surface-rt/

http://blog.brightpointuk.co.uk/adding-exchange-email-account-windows-rt

WOW yourself KarlProp - your GOOD step-by-step (your link above) helped me connect to Exchange Server 2003.  I AM FINALLY CONNECTED AND HAPPY.  Microsoft did not help at all - 2 of their "Support Engineers" just confused the issue by not understanding the difference between connecting Surface RT to a domain and connecting Surface RT to Exchange Server (which is itself on a domain).

BOTTOM LINE: it's ridiculous to expect IT managers to modify server settings to get Surface to work. Surface should be the device to be modified. Most requests to modify a server will be met with, "You should have bought an iPad." 

New devices come out all the time. Just because some work with an existing configuration doesn't mean that configuration should work with everything.

Back in the day when Blackberry was the only way to get secure remote e-mails, people made the same argument with ActiveSync: "Why should my IT staff have to enable or buy ActiveSync when Blackberry already has it working? Everyone should just be compatible with the BES."

Same situation. We know the Surface RT client does work with Exchange servers (perhaps Exchange 2003 is an exception). Is the right solution for MS to patch a functional mail client, or for the IT staff in a company to make a single line change to ActiveSync so it is Surface RT compatible?

Again, possible Exchange 2003 issues aside, this is a problem that could potentially be quickly fixed by opening an IT ticket, or (unfortunately) using a device that is "supported" by your IT department.

If anyone that has an open ticket with MS on the issue now can share what exactly MS found, and which version(s) of Exchange server and which policies it pertains to, I would appreciate it.

I think Microsoft would be the FIRST to say that Surface should work with any service that iPad, iPhone, Blackberry, Droid, etc. work flawlessly with. It's understandable there's bugs. Keeping my fingers crossed they will solve this soon. Stay tuned.