Error seeing Free / Buisy schedule on Outlook 2003/2007

I've Exchange 2007 EE SP1 installed in my org. here but haven't installed client access role yet. Only mailbox and hub on one server. I've problem seeing free/busy schedule on outlook 3003 as well as 2007. On Outlook 2003, I can see free/busy info of other user but not the "Room" type user. On outlook 2007, I can't see any free busy info of other users. Not sure client access role is required or not for outlook 2007, but why Outlook can't see Room user's info. Any help.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Yes, Client Access server role needs to be installed on the Exchange server.

The Client Access Server role is also home to other important services such as the Autodiscover and Availability services. The availability service in Exchange 2007 is largely concerned with how users access the free/busy information of other users.

mdexchAuthor Commented:
Hi Sekhar,

Thanks for  your reply.
Does Outlook 2003 uses client access server or gets data from Public folder? I do have public folder created on Exchange 2007.

mdexchAuthor Commented:
I just installed client access role on a seperate server, but I still can't see "Room" user's free/busy data on outlook 2003. However on outlook 2007, now I can see other's free/busy info.

Yes, you need to setup a public folder DB. You can follow the below MS KB article to resolve the problem: 

OR you can follow any of the below options to resolve the issue.

I will explain you little briefly. The problem is with Outlook 2003. It doesn't understand native Exchange 2007 Free/busy overhaul where OL2007 does. E2k7 w/OL2007 are designed to pull together other's FB directly from each others calendars using the server side Availability Service, not from a centralized System folder as with E2k3.  OL2003 was designed around E2k & E2k3 architecture with a centralized FB system folder structure. And all OL2003 clients go to the closest server to them based on what is in the local Mail Profile (windows messaging subsystem RegKey). Your options are:

a) To stand up another E2k3 server for hosting the system folders which may then require you to run GUIDGen utility, Or
b) Have the OL2003 users use OWA for scheduling their meetings, or
c) Upgrade your OL2003 clients to OL2007 create a new mail profile for them and call it done.

The option c is the best option which I suggest.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.