I built a Client Access server in our Production Site. I then moved it to our DR site and am getting errors. I moved the server from one AD site to another and gave it a new IP address. How can I fix this? This is also happeneing on a Hub Transport server too. I did the same process for the Hub Transport. I have verified all TCP/IP settings and DNS records. Could not find any Global Catalog in forest domainname.com.

Hello, Have you followed belowguide to move it? How to Move a Client Access or Hub Transport Server to a Different Site http://technet.microsoft.com/en-us/library/cc164355(EXCHG.80).aspx

I am not moving a subnet to a new site, only the server by giving it a new IP address and physically moving itto a new facility. When I query the CAS that has been moved from a different CAS that has not moved I can view it in the EMC. Everything looks good and I can manage it. When I check the event logs on the server that has been moved everything in there looks good to, below I have attached an event log that states the server even found the correct GC for it's new site. Event Type:InformationEvent Source:MSExchange ADAccessEvent Category:Topology Event ID:2081Date:10/30/2008Time:1:58:45 PMUser:N/AComputer:ClientAccessServerName Description:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1432). Exchange Active Directory Provider will use the servers from the following list: Domain Controllers:servername.domainname.com <---This is the correct server name.Global Catalogs:servername.domainname.com<---This is the correct server name.

Dear customer: Did the issue resolved? If not, please move the CAS server according to the previous link and check the effect. If anything is unclear, please feel free to let me know. Rock Wang - MSFT

Unfortunately I cannot follow the document as the server has already been moved and both the EMC and EMS will not function due to the following error. This is the error I get everytime I open EMC or EMS.Not to mention some of the steps in that KB do not apply like moving a subnet to a new site. --------------------------------------------------------Microsoft Exchange Error--------------------------------------------------------The following error(s) were reported while loading topology information: get-ExchangeServerFailedError:Could not find any Global Catalog in forest domainname.com. Global catalog not found in forest "domainname.com". get-UMServerFailedError:Could not find any Global Catalog in forest domainname.com. Global catalog not found in forest "domainname.com". --------------------------------------------------------OK--------------------------------------------------------

Alright, so my work around to resolve this worked. I moved our DR subnet to the Production site where these servers were orginally built. I moved the DR domain controller to that site as well. I forced AD replication so the changes would take affect and then rebooted the DR domain contoller, CAS and HT. When all three servers came back up I was able to login to both the CAS and HT and use the EMC and EMS. I then removed Exchange from both servers and moved both the subnet and DC back the their original site. I will then reinstall the Exchange Roles on the servers in their new sites. What a pain in the a$$. Moving server between sites should not be this hard.

Dear customer: I am so glad to know the issue has been solved. Thanks for your knowledge sharing. Thanks again and have a great day! Rock Wang - MSFT