Env: TRansitioning from Windows 2003 DCs to 2008 DCsDomain/Forest Level: Windows 2003There used to be two W2k3 GC DCs and I added a Windows 2k8 GC DC. After I successfully moved the FSMO roles to the W2k8 DC and demoted the two W2k3 DCs, Exchange server is not communicating properly I followed all the troubleshooting/checking provided by Frances He in a similar case here:http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/2efdaed2-d803-4c2b-a369-bc46919cbb75and everything looks good. I restarted the W2k8 GC DC . When I run the command:Get-ExchangeServer -status | fl current*I get the error: "the exchange topology service on server... did not return a suitable domain controller"IN the event viewer there severl type of topology errors:error 2114 Source MS Exchange AD accessMSEXCHANGEADTOPOLOGYSERVICE.EXE PID=1268I even statically assigned the domain controller to it with this commandsSet-ExchangeServer -Identity EX-server-StaticDomainControllers:w2k8dc.domain.com -StaticGlobalCatalogs:w2k8dc.domain.com -StaticConfigDomainController:w2k8dc.domain.comI restarted and it took about 1 hour for this server to come back to desktop (DNS is properly pointing to the same W2k8 DC that is the DNS server as well)After this I tested and same errors and it shows the static DC assignments .What could have gone wrong?? Replication was working all the way before demoting the Two W2k3 dc's and they were gracefully demoted.ThanksJohn

Did you assigned the subnet to the site where the DC and Exchange belongs?CapecolMCSA - MCTS Exchange Server 2007 - 2010Blog: http://capecol.spaces.live.com/default.aspx

where do I do that? These is a W2k8 DC and exchange server located in the same site and subnet

Go to Active Directory Sites & Services, then on the Subnets session create the Subnet that belongs to the Exchahnge and DC, when the Subnet is being created assign it to the appropiate Site...most probably is that there is only 1 site named Default First Site Name...CapecolMCSA - MCTS Exchange Server 2007 - 2010Blog: http://capecol.spaces.live.com/default.aspx

hi,first check that the network configration of the exchange server that the DNS is the same as the new one.2nd go to exchange organization in the mangment console & point to the new domain controller.then try restarting the exchange serveryou can also run the best practice analyzer.