Outlook 2010 Calendar - Unable to See Free/Busy Scheduling

Question

I am having an issue where random user cannot see others Free/Busy Scheduling in Outlook Calendar 2010. The set up is pretty simple with one domain.

I have been Googling all morning, I am unable to find even one good explanation why this is happening. I have done anything, and did not fix it.

Any thoughts on this? Would really appreciate your help in advance.

Thanks guys.

UPDATE: I did try to delete the Outlook Profile, as well as all the user profile for this particular users from 3 Terminal Servers. The user profile had been rebuild OK, and I also recreated the Outlook profile manually. It is still doing the same things.

Solution

Finally, I found the answer for my problem with Free/Busy Scheduling in Outlook 2010 Calendar. I have been looking everywhere that I know about in Exchange 2010. It is something to do my Proxy Server and the Exchange Update that reset couple of my settings.

For the Proxy Server issue, I have reapplied the Group Policy to all users. Somehow, my GP has been reset too, and I don't know why.

For the Exchange 2010 settings, I have changed the EDP Internal URL and my HTTP redirect to the correct address.

Hopefully this can help anyone who has the same issues, although it might be different cause.

Thanks everyone for your help.

Comments

[Nixphoe]

Anything in the event log, with either your exchange server, or the user's computer?

[Arief]

@Nixphoe, I did look them through, and nothing really obvious to indicate the issues. I have doing this as well all morning, reading them almost one by one.

[Nixphoe]

Is it random users cannot see anyone elses free/busy scheduling? or is it only certain people can not see it? Have you checked to see if Exchange Cached mode is set for the exchange profile? Have you tried running outlook with the /cleanfreebusy command-line switch?

[Arief]

@Nixphoe, It is randomly happen. I need to check the Cached Mode on this user that I'm working on. I can't do the /cleanfreebusy as the cmd is restricted for the user. The thing is, the user can see anyone free/busy through the OWA. What do you think? The OWA for this user is working 100%. And also, when I try to run the Email Auto Configuration, I got an error: Autoconfiguration was unable to determine your settings.

[Nixphoe]

Are both of the users connecting with RDP? Did you find if they are using cached mode? If you have access to Start > Run, you should still be able to run the /cleanfreebusy command from there.

[Arief]

@Nixphoe, They are both connecting with RDP. All TS users are not using the cached mode. No, the users do not have access to cmd, it's restricted.

[Ben Pilbrow]

Can you Shift+Right Click (it might be Ctrl, I forget) on the Outlook icon in the system tray and see what test autoconfiguration status comes back with on both an affected and non-affected user. For good measures too, run Test-ServiceHealth on the Exchange server and check that's ok.

[Arief]

I just found out that the user is actually on the Terminal Services. The other users on the TS do not have the problem. So far, this evening, I found that actually 2 users are now having this problem.

[Arief]

if it is really a DNS resolution issues, why it is only affecting these 2 users.

[Arief]

we are using Exchange 2010.

[learnningprogramming]

Obviously, I had no idea this was a TS environment. I still think there may be a link with autodiscover given you've seen 2 issues with reaching it (inability create a profile via autodiscover and inability to reach free/busy). Maybe not with autodiscover or Exchange itself but maybe with the terminal server and occasional name resolution issues or something like that. Hard to troubleshoot that further remotely.