Hi I have a user who is using outlook 2007. He is connected to our exchange server. The user tries to create a new appointment or meeting request and then adds a meeting room which is a resource account. The calendar displays the schedule of that meeting room without any problem. The problem occurs when the user hovers the mouse over a time slot that is busy. Normalyl when you put your mouse over a booked time slot for a resource it gives you the details of that meeting. But for this user it does not show the details. When he puts his mouse over the blue busy time slot, nothing pops up for him. The permissions are all ok. The everyone group is allowed to edit and read the resource. The user can actually open up the shared calendar in his outlook, its only when he is creating the appointment the problem occurs. Also this only happens with this particular room, the user does not have this problem with other resources. Any ideas what could be wrong here? Thanks

Is this Exchange 2007? Issue a get-MailboxCalendarSettings command in Powershell for that room and see what is set for DeleteComments switch. If its set to true and this room doesnt auto accept, the details are removed when the appt is booked for that room.

Hey, If the othe user check the particular room, whether the same issue occurs? If the issue still occurs, I recommend you compare the setting of the conference room with other rooms. Thanks, Mike

It is exchange 2003.

No its only one user who has this problem. Not sure what is preventing him from seeing the room details.

For exchange 2003, it is normal behavior that you can only see Free/Busy status of a room. It is because Exchange Retrieve Free/Busy from Public Folder instead of Availability service which used by Exchange 2007. Thanks, Mike

And these are mailboxes you are using a resources? If so, you could always logon to that resource mailbox with the /cleanfreebusy switch directly and see if that fixes it ( I know it only affects one user) Another test is have this user logon directly to that mailbox and see if the problem continues.