So you're running native Exchange, and can't get O...

2006-07-18T17:23:00.000-07:00

So you're running native Exchange, and can't get OMA synch to work? You're not using SBS, but have created the exchange-oma v-dir and it still doesn't work?

Ok, here is the deal. Configure the /Exchange directory with forms based auth, and SSL and all that jaz

Configure the \Exchange-oma v-dir without forms based auth, and no SSL required, but lock it down to the IP address of the server only (both the internal and external IP addresses are required, if you have them).

Then you'll have to play in the registry (being very carful of course, the registry can cause problems with your system if you don't update it properly.

Point your registry explorer at hklm \system \currentcontrolset \service \massync \Parameters and create a dWORD called "ExchangeVDir", and set the contents of the key to "/Exchange-oma" without the quotes.

Then from a command prompt, run "iisreset".

Let me know if that works, or if i have your scenario all wrong.

Great article!

I've set up my OMAover HTTP ...

2006-07-18T15:09:00.000-07:00

Great article!

I've set up my OMAover HTTP on the SBS2003-SP2, based on numerous "how to config" articles found on the net. On SBS, like in my case the server is a standalone exhange, with the /exchange-oma VDIR on the same Exchange / box. I still get the dreaded : Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange Server 2003. Currently your mailbox is stored on an older version of Exchange server.

WHY?! The registry/webdav shoulkd communicate withe OMA vdir!!!! Everything that I've read about this should be in place.

Comments on SeanDaniel.com: What's in a Synch?

So you're running native Exchange, and can't get O...

Great article!I've set up my OMAover HTTP ...

Great article!

I've set up my OMAover HTTP ...