Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Outlooks 2003 client cannot book a meeting in a certain Exchange 2010 SP2 room

Answered Outlooks 2003 client cannot book a meeting in a certain Exchange 2010 SP2 room

  • Wednesday, May 02, 2012 6:58 PM
     
     
    Sign In to Vote
    0

    I have several users that are still using Outlook 2003 and for one conference room and only one, they get a "Unable to open free/busy information. Unable to directly book a resource for this meeting"

    We have many conference rooms and this only happens on one. People with Outlook 2007 and Outlook 2010 as well as OWA can book with no issues.

    I have cleared out the cached GAL on the users PC's, run Outlook with /cleanfreebusy switch.

    What else am I missing?

     

All Replies

  • Friday, May 04, 2012 1:28 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    It appears the conference room is setup correctly, the issue might be caused by Public folder since Outlook 2003 retrieve free/busy information from it.

    Is the problemaitc Outlook 2003 client's mailbox resided on Exchange server 2010? Where does the public folder points to?

    Please verify the Application event log on the Mailbox server where the affected mailbox resided on and check if there is any error recorded.

    Also check if there is public folder replication related issue.

    Hope it is helpful.

    Fiona Liao

    TechNet Community Support

     
  • Friday, May 04, 2012 1:32 PM
     
     Answered
    Sign In to Vote
    0

    Finally found the answer this morning. It seems that Outlook 2003 and 2007 where trying to do direct booking. I set the following registry key on both those sets of users and it started working again.

    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\options\Calendar\ EnableDirectBooking Dword 0 for 2007 and HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\options\Calendar\ EnableDirectBooking Dword 0 for 2003

    I set this in a group policy, changed the mailbox permissions for default user to reviewer and voila!