Outlook 2013 - cannot use RoomLists and Suggested Times

Hi,

maybe someone has a clue on what is wrong here.

In OWA, we can use the new features RoomList and Suggested Rooms when using the Calendar Assistant to plan a new meeting. The room list can be first be chosen, and the fields for the rooms are then populated as expected, you can choose one of the rooms.

The following is true for every Outlook Session on PCs/virtual Clients, they are configured to use Online Mode: In Outlook 2013, when using: New Meeting - Scheduling Assistant, the feature "Choose an available room" stays complete empty and does not show the room list. Also the box below that, labeled "suggested Times", does not load or display content. Instead, an error message is displayed in it: "Suggestions cannot be provided because free/busy data could not be retrieved."

Laptops use the exact same Outlook version, but run in cached mode. Here, if you deconfigure "Communication using http" in the OL profile, the lookup for suggested times works _once_ until Restart, then the button is automatically added, the profile automatically made good again, and the suggestion function is broken again.

If you deconfigure the button "Connect to Microsoft Exchange using http" in the Outlook Profile under the connection tab on an _online mode PC_, the profile is broken and not automatically made good again. So no temporary workaround is possible here.

We do not run policies that may keep Outlook 2013 from using the functions. In fact we do only rule cached or online mode.

Our Room List is free of special characters and short enough, so no problems that other people have found in their environments.

We have found some older articles reporting broken functionality, when applying or not applying hotfixes. We have checked several of that and it is not the source of our problem.

Also, we are currently within one domain, so no complicated setup using one or more forests or even other domains, configuration of free/busy accounts should not be an issue here.

Our best guess is it may have to do with using Exchange webservices or MAPI for the connection, see both ways described communicating over http or not above, but we have not found an error or wrong configuration here.

Can you please advise on where to search next?

  • Edited by itstaes 18 hours 2 minutes ago
April 1st, 2015 9:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics