Link to home
Start Free TrialLog in
Avatar of Bwalters613
Bwalters613

asked on

Free/Busy information missing on certain users after exchange upgrade.

Hi, I just upgraded to a new server with exchange 2007, I have removed the old server running exchange 2003 from the site. I followed the migration process and all seemed to work fine. My only problem is that I have 4 users that I cannont see the free/busy data on when I try to schedule a meeting. If I mouse over the user it says "no free/busy information could be retrieved" I have verified all calender permissions on each users mailbox. This worked fine on the old system. I have no events logged in the event viewer, it is very clean. The 4 users in question are setup identical to the other users that are working fine. I think I am missing something very simple but I am currently braindead and would appreciate any help you could give.
ASKER CERTIFIED SOLUTION
Avatar of Interserv
Interserv

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Bwalters613
Bwalters613

ASKER

They are set to show fee/busy and still same issue.
You might want to make sure that autodiscover is pointing to the correct Availability Service.  You can see this via the Test E-mail AutoConfiguration tool in Outlook 2007 (press CTRL and right-click the Outlook icon in the System tray).
I am using outlook 2003, The autoodiscovery is working because I didn't have to reconfigure the outlook clients after the upgrade. The clients automatically switched to the new server.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry for the late reply, Believe it or not but it seemed to fix itself. It took 4 days but at the end it was all fixed. Not sure if it was a replication issue. That seems like a possibility.