5 year ago I upgraded from Exch2000 to Exch2007 sp1 by installing new servers and migrating the mailboxes. At that time I there were 2 active Public Folders, plus Outlook2000 & 2003 clients, so I had to keep the public folders after the exch2k7 install. 3 months ago I updated to Exch2007 sp3. The same day, Free/Busy essentially stopped working. Now, users intermittently get the gray lines when trying to view another person's calendar. All clients have been Outlook2007 for 3 years. Since the issue is intermittent, it is hard to test anything when it occurs, but with all users that we have run 'Test Email Autoconfiguration' on, they have all tested successfully to the availability service. How can I fix the Free/Busy issue without messing up the legacy Public Folders that are in use? Thanks for any suggestions

Hello, For Exchange 2007, users on Outlook 2007 or later version never use the public folder to access the free/busy information. Instead, they use availability service(EWS). When the issue occur, you need to check the autodiscover and availability service status by: a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select Test Email Autoconfiguration. b. Confirm that your email address is in the address field, uncheck Use Guessmart and secure Guessmart authentication boxes. Then click the Test button. c. Once it runs, check the Log tab and Results tab. In addition, you need to check the application log to see if there are any related error event IDs when the issue happens. Thanks, Simon Wu Exchange Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Could the 'legacyexchangedn' setting have anything to do with this issue? My users have different settings for this entry depending on if they have been in the system since Exch5.5, Exch2000 or were created new in Exch2007. I have checked the users reporting the free/busy issue and they are a mix of legacy, old and new users.

Hello, No, the 'legacyexchangedn' is only used by the Outlook 2003 clients to local the public folder to retrieve the Free/Busy info. Thanks, Simon Wu Exchange Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Then I am at a loss. Since the issue is intermittent, there is no commonality and I hesitate to keep logging turned on all the time for the users who have had the issue because it may take days for it to show up again. If the users consistently test successfully at getting to the EWS folder, what else could cause this issue? Thanks for your help!

Another thought.....we just started using activesync, so I recently ran the commands to change the EWS path to the url reflected in my SAN certificate. However today when I ran: Get-webservicesvirtualdirectory | fl I noticed that the 'Internalnlbbypassurl' was set to: https://mobile.mydomain.com/ews/exchange.asmx However, the 'InternalUrl' was set to: https://mobile.mydomain.com/ews/asmx and when I run the Test Autoconfig for Outlook, the 'availability service' path was missing 'exchange'. I set the internalurl to 'https://.....exchange.asmx' and so far everyone I have run "test-outlookwebservices' on has passed everything. Also, when I do the Test Autoconfig, it is correctly pointing to exchange.asmx. Do you think that the differences I explained above could cause the free/busy issue, especially the intermittent part?