WooHoo!! Finally got OMA to work w/ SSL and Forms Based

netsyd · 02-08-06, 11:39 PM

Been fighting with this for days...

I wanted forms based authentication and I had to keep SSL enabled for OWA (Outlook Web Access). Unfortunately these two things break OMA (Outlook Mobile Access). What a freaking nightmare of stupid error codes.

Anyway, for those of you with similiar issues / desires, I posted the steps I took on my site (listed below).

Basically it's pretty simple once you get it all figured out:

To avoid the SSL certificate is not correct/does not match the server issue (Support code: 80072f0d)- The certicate needs to match the FQDN of the server and you need to import the certificate onto your PPC. You can do this by exporting the trusted certificate out of the certificates mmc snapin on the server, then copying that export to your ppc.

To avoid the Support Code: 85010014 (general error code) problem you need to enable a new oma virtual directory on IIS and make a registry change on the server... this fixes the issue with SSL/Forms based authentication.
Here's the microsft article on the SSL/Forms Based problem - http://support.microsoft.com/default...b;en-us;817379 - Note this does not help your errors if you experience them from Outlook, this is if you are trying to sync a PPC to an Exchange server... the desktop outlook 85010014 error is something completely different.

stevenator65 · 02-09-06, 12:09 AM

Netsyd, I'm glad you got all your acronyms working! That's awesome. I have no idea what they are but they sound like they're very helpful to you. I celebrate for you w/a toast!

netsyd · 02-09-06, 12:55 AM

My wife gave me the same look LOL.... Then she went to bed because she was "tired". I think she just wanted me stop talking!

Thanks for the toast

02-09-06, 01:01 AM

That's an excellent article! We also wrestled with this a lot, and spoke to MS and the whole 9 yards. Nice job.

netsyd · 02-09-06, 01:19 AM

Well normally this would have been something I quitely went on my way with, but I spent hours on the web searching for solutions and it was all bits and pieces which inevitably ended up with someone on a final post going... "can anyone help?"

Aximsite gets a lot of foot traffic, and consistently ranks near the top on google, so I figured one sucess story might brighten someone up with the thought that it really can be done if they were searching like I was.

Now that this is working, I have access to do remote wiping, which is cool if my axim ever gets stolen, but I also can maintain secure outlook web access and still be able sync from a hotspot. Without this working your outlook web access transmits passwords plaintext - not a wise move. I'm going to do some packet captures later and see what kind of traffic I can catch between the axim and exchange... I get the feeling it still transmits plaintext.

I guess I'm just happy because the questions never got fixed most everywhere I searched ... but me sitting at home with my solitary exchange server finally got it going. :)

02-09-06, 01:53 AM

I don't think you can do remote wipe until there's an MSFP for the device right?

And hey - I mentioned and linked to your article at our site:
SMA Link

netsyd · 02-09-06, 09:51 AM

Originally Posted by patrickj

I don't think you can do remote wipe until there's an MSFP for the device right?

And hey - I mentioned and linked to your article at our site:
SMA Link

Yes ... that would be correct. The MSFP (hopefully to be released by Dell) is going to be required before this is really an option. I imagine it will be supported by Dell simply because of the number of Axims purchased by businesses and government...

If not the Treo 700 (or something similar) was next on my list, so someone will support it! :approve:

Thanks for linking to it ... hopefully it'll get seen by someone who needs it!