Exchange 2010 coexistance with 2003

Posted on 2012-08-31
Medium Priority
Last Modified: 2012-09-04
Hi ,

Can somebody help me in resolving this issue

User migrated to 2010 cannot see the free/busy in scheduling assistant for the users who are still on 2003 but can see for those who are on 2010. Same as with the users who are on 2003.

Auto discover connectivity test passed for Attempting to test potential Autodiscover URL https://autodiscover.*****.net/AutoDiscover/AutoDiscover.xml

Any help from anybody please
Question by:jmanes

Expert Comment

ID: 38356279
Have you configured the replication of the free/busy folder (in the public folders)?

Author Comment

ID: 38356292
I just did that ..Let me see the results and i will get back here again.

By the way ,thanks for the prompt response
LVL 18

Expert Comment

ID: 38357166
All the public folder replicas should be in sync. This is always the tedious bit of the migration. There are ways to speed up replication, by specifying replicate always and verifying that the contents are all in sync.

Once everything is in sync, information should be displayed correctly.
LVL 33

Accepted Solution

Exchange_Geek earned 2000 total points
ID: 38357794
Hang on, if this is something related to E2003 - confirm if the free/busy is working for you're local E2010 box OR not.

Once confirmed, check as mentioned above is replica list added on Free/busy Administrative Groups (understand there would be two groups added under Schedule Free/Busy system folder under PF Tree)

You'll need to add replica of both servers (E2k3 and E2k10) on both Administrative Groups.

Force PF replication.

If E2k3 guys are facing an issue too, then it is a difficult story that we can lead here.


Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In my humble opinion (IMHO), TouchDown from Symantec is the best in class for this type of application, but Symantec has end-of-lifed it and although one can keep using it, it will no longer be supported or upgraded.  Time to look for alternatives t…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month9 days, 16 hours left to enroll

569 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question