Question : OMA problem in Exchange 2010 - HTTP Error 500.24

Hi Experts,

A new 2008 server 64bit.  Exchange 2010 installed
All the users have been migrated from sbs 2003 exchange and all are working thru Outlook to connect to the new info store on Exchange 2010.  OWA works fine to connect to Exchange 2010 also.  

The problem I am having is with Exchange-server-ActiveSync.  When browsing to "https://localhost/Exchange-server-ActiveSync" it comes up with the customary security certificate error.  After clicking continue it just shows "Internet Explorer cannot display the webpage"

In IIS I created a new virtual directory called oma and pointed it to the same location as the EAS was pointing to.  When browsing to "https://localhost/oma" it shows

HTTP Error 500.24 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode. Detailed Error Information
Module ConfigurationValidationModule
Notification BeginRequest
Handler AirSyncHandler
Error Code 0x80070032
Requested URL https://localhost:443/oma
Physical Path C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\sync
Logon Method Not yet determined
Logon User Not yet determined

When browsing to "https://mail.company.com.au/oma"  it will show
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

I have been struggling with this for the last week, though I am not very confident with Exchange 2010.

Please Help!!

Answer : OMA problem in Exchange 2010 - HTTP Error 500.24

I assume the goal here is to have all the users home directories on an Windows Share so that no user data resides on the Mac, and when a user LOGS IN, the proper home folder is just in place.

While there are ways to get a folder mounted (obviously), I do not believe there is a way to automatically log into an account where the home folder lives on a remote server.

For grins, I created a home folder for a new account, moved it to a Windows Share volume, and tried all kinds of tricks to alias or links back to it. Closest I got was to put a real home folder on the Mac, and link all the folder back to the server. However, there were problems in writing to the folder, and preferences and such were messed up on boot and not loaded properly when the use logged in.

I am just not sure how this can be done automatically and be ready at login time.