OriginatingServer : EAI-PDC.eafg.local how do i change it to : EAI-DC-01.eafg.local to the new PDC running windows server 2003 R2

Hi, Can u elaborate what are u trying to do? BTW IF you are asking about setting some specific DC for exchange server then u can use something like this: Set-ExchangeSever serverName -StaticDomainControllers "DC1,DC2" for further reference plz see http://technet.microsoft.com/en-us/library/bb123716(EXCHG.80).aspx Regards, Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

You need to provide more information. What are you trying to accomplish? What version of AD and Exchange are you using? Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

recently I've added another Dc and moved the FSMO to this new server named EAI-DC-01 before the FSMO was on EAI-PDC. Now I'll be shutting down or removing the old PDC (EAI-PDC). I want to make sure Exchange should not face any problem cotnacting the AD.

Hi, You can set static DCs and GCs with this command. Set-ExchangeSever serverName -StaticDomainControllers "NewDC" --StaticGlobalCatalogs "NewDC" -StaticConfigDomainController "NewDC " Configure it, and then verify it using Get-ExchangeSever serverName | FL and then temporarily shut down the old dc for few days to verify that exchange is running fine and keep this settings if it works. You can later set any of above to $null to revert the changes. For details plz visit the link mentioned in my previous post. Regards, Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

As long as you are not seeing any issues in the new DC you should be good. You can verify the FSMO roles by using the following command: Netdom Query FMSO I hope you didn’t configure the static DC on the existing server. If so, please change it to the new DC , better to go with auto discover option. What version of Exchange are you using?Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

As long as you are not seeing any issues in the new DC you should be good. You can verify the FSMO roles by using the following command: Netdom Query FMSO I hope you didn’t configure the static DC on the existing server. If so, please change it to the new DC , better to go with auto discover option. What version of Exchange are you using? Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

Apart from FSMO role transfer and Set-ExchangeSever serverName -StaticDomainControllers "<your domain controller name>", you have to consider windows time server as well. go through the below link, I hope it will help you out. http://www.the-little-things.net/?p=7

Hi Vministrator, I agree with the friend above. You could specify the new DC, shut down the old DC for some days and see if there is some problem. I also suggest you to run Exbpa to do a health check. The OriginatingServer property indicates which DC the data was read from and is used primarily for troubleshooting. It is updated with each AD call, so it could change with each read. Hope this helps. Thanks, Elvis