The other thing I thought it may be, was the WebServicesVirtualDirectory wasn't working properly, so I deleted it and rebuilt it, but it still doesn't work. I did find out that the clients domain didn't have a pointer for auto discover, but I was able to fix that and it tested This helped me sort of narrow it down, so I started searching for things that could keep Outlook from syncing that information. To Outlook clients and how they connect/retrieve the information from the Exchange Server.
My company has just setup a hosted exchange environment so that we can provide e-mail hosting to various clients, we have our first client andĮverything seems to be working with the exception of the free/busy information that should be visible when using scheduling assistant.Īt first I thought it was an issue with the exchange server itself, maybe the free/busy piece just wasn't implemented or there wasn't a public storage group, but the scheduling assistant works fine in OWA for our client. I have been banging my head against my desk for the better part of a week trying to figure this out.
