We are upgrading exchange 2003 to exchange 2010 We installed a new server 2008 R2 and followed upgrade instructions from Exchange 2003 that is installed on w2k3 machine. we moved all mailboxes to the new server and everything is working fine. The servers are working together for two weeks now. We are now trying to remove the old server. It looks like the new server cannot work without the old one. The new server is configured as global catalog. but it seems that the new exchange 2010 refuses to use its global catalog and only uses the old one (Hub transport->right click on the server->system settigns gives the name of the old server as global catalog and it does not list the new server at all) here is the DSAccess message: Process MAD.EXE (PID=2544). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: OLDSERVER CDG 1 7 7 1 0 1 1 7 1 SECONDARY CD- 1 6 6 0 0 1 1 6 1 NEWSERVER CDG 1 0 0 1 0 0 0 0 0 Out-of-site: There are no firewalls. everything is on the same domain, same location. The desired configuration should include only the new server and the secondary as backup. We would like to remove the old server. We tried many of the solutions discussed on this forum and others, and nothing helped. Any help will be appreciated. Eyal.

Hi Eyal, his is not recommended to install exchange on DC base server. First i would suggest you to reboot the old server and then check again. Finally you can manually point GC and DC in exchange 2007/2010 . Please find below information to proceed. http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/349ca379-f435-417f-a41a-98fccde450ef/ Set-ExchangeServer:: http://technet.microsoft.com/en-us/library/bb123716.aspx Anil

Thanks for your answer. We have tried this solution and nothing happened: we rebooted the old server, also the new one. we also tried setting manually the global catalog using Set-ExchangeServer command. Eyal.

Based on your DSAccess output, the NEWSERVER is not capable of "answering" the exchange server. Are you sure this DC is healthy? Any firewalls or AV client blocking communications? Take a look at this article: http://howdouc.blogspot.com/2011/01/exchange-active-directory-topology.htmlTim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

I have ForeFront for Exchange 2010. I don't think it is harmful. no firewalls. I have just found a post about turning ipv6 on (it was off). I turned it on and things look a bit better now, but I'm still not sure. Could it be the case? Eyal.

Since you are trying to decommission the OLDServer, have you transferred the FSMO roles to one of the other DC's? Also, I recommend having at least 2 GC's (enable GC on SECONDARY) in your environment since Exchange requires a GC to function properly. Please post the details of Event 2080 again to be sure that Exchange can use the DC.Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

Hi Eyal, What is status about your problem. Anil

Eventually, enabling ipv6 solved the problem. We still have other problems, but at least now the new exchnage server works witouht the old GC. here is the new topology, after enabling ipv6: Process MAD.EXE (PID=2544). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: OLDSERVER CDG 1 7 7 1 0 1 1 7 1 SECONDARY CD- 1 6 6 0 0 1 1 6 1 NEWSERVER CDG 1 7 7 1 0 1 1 7 1 Out-of-site: Thanks, Eyal.