Hi,

I need change Exchange 2013 to use different DC and GC. Can you help me how can i do it?

This example powershell command dont work
Set-ExchangeServer -Identity casXX -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com

But CurrentGlobalCatalogs,CurrentDomainControllers,CurrentConfigDomainController still set on old domain controller.

Hi

and this command:

Set-AdServerSettings -ViewEntireForest $true -PreferredGlobalCatalog gc1.contoso.com

Thank you for your reply,

but Command "Set-AdServerSettings" change only the current Exchange Management Shell session.  I need shutdown old DC -> roles has been transfered to new DC.

• Edited by Matocha Jií 21 hours 37 minutes ago

Thank you for your reply,

but Command "Set-AdServerSettings" change only the current Exchange Management Shell session.  I need shutdown old DC -> roles has been transfered to new DC.

Exchange will find the correct DC to use dynamically. No need to statically set it unless there is a compelling reason.

I would set all the static settings you may already set to $null.

Then Check Event 2080 on the Exchange Server to verify its using the new DC and the old on as well.

Then shut down the old DC and ensure everything looks ok. If necessary restart the AD Topology Service. If you are worried about user access, test after hours

Hi,

if i disable all network on old DC, then servers OS run from new DC but exchange service dont work from new DC.

Hi,

if i disable all network on old DC, then servers OS run from new DC but exchange service dont work from new DC.

Did you restart the AD Topology service?

Are any DCs still set statically?

What does dsacess event 2080 show?

Exchange isn't installed on a DC is it?

Thank you for your reply,

but Command "Set-AdServerSettings" change only the current Exchange Management Shell session.  I need shutdown old DC -> roles has been transfered to new DC.

• Edited by Matocha Jií Sunday, February 01, 2015 2:12 PM

Thank you for your reply,

but Command "Set-AdServerSettings" change only the current Exchange Management Shell session.  I need shutdown old DC -> roles has been transfered to new DC.

• Edited by Matocha Jií Sunday, February 01, 2015 2:12 PM

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator 21 hours 38 minutes ago
• Unmarked as answer by Matocha Jií 21 hours 31 minutes ago

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, February 06, 2015 2:11 PM
• Unmarked as answer by Matocha Jií Friday, February 06, 2015 2:18 PM

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, February 06, 2015 2:11 PM
• Unmarked as answer by Matocha Jií Friday, February 06, 2015 2:18 PM

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, February 06, 2015 2:11 PM
• Unmarked as answer by Matocha Jií Friday, February 06, 2015 2:18 PM
• Marked as answer by Matocha Jií 3 hours 53 minutes ago

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, February 06, 2015 2:11 PM
• Unmarked as answer by Matocha Jií Friday, February 06, 2015 2:18 PM
• Marked as answer by Matocha Jií Friday, February 27, 2015 7:58 AM

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Unfortunately exclude old domain controller dont work. Exchange server still connected on old domain controller.

Hi Matocha,

Thank you for your question.

We could use the following command to eliminate old domain controller to check if Exchange server could point to new domain controller:

Set-Exchange Identity <server_name> -StaticDomainControllers adxNEW.domain.com -StaticGlobalCatalogs adxNEW.domain.com -StaticConfigDomainController adxNEW.domain.com -StaticExcludedDomainControllers <old DC>

Then we restart the service of Microsoft Exchange Active Directory Topology and use Get-ExchangeServer Status <server_name> | FL to check if we have been modified it.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Unfortunately exclude old domain controller dont work. Exchange server still connected on old domain controller.

What about my previous questions?

What does dsacess event 2080 show?

Exchange isn't installed on a DC is it?

Hi,

domain controller is on another server. Please be patient-> i will check event log later.

Hi,

domain controller is on another server. Please be patient-> i will check event log later.

Hi,

even log shows:

       Process Microsoft.Exchange.Directory.TopologyService.exe (PID=8756). 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:
adxOLD.mydomain.com CDG 1 7 7 1 0 1 1 7 1
ADXbdc.mydomain.com CDG 1 7 7 1 0 1 1 0 1
ADXNEW.mydomain.com CDG 1 7 7 1 0 1 1 0 1       
Out-of-site:

Hi,

domain controller is on another server. Please be patient-> i will check event log later.

Hi,

even log shows:

       Process Microsoft.Exchange.Directory.TopologyService.exe (PID=8756). 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:
adxOLD.mydomain.com CDG 1 7 7 1 0 1 1 7 1
ADXbdc.mydomain.com CDG 1 7 7 1 0 1 1 0 1
ADXNEW.mydomain.com CDG 1 7 7 1 0 1 1 0 1       
Out-of-site:

That looks good. You should be able to remove the old DC.

After hours, I would down it, the restart the Exchange Services or reboot the Exch Server and test.

Hi,

i set value StaticExcludedDomainControllers and restart one cas server from exchange farm. But exchange service still works from old AD server  :-(

Do you have any idea?

Thank you for your help

Hi Matocha,

We could go to the following location and removed the Exchange Management Console Snap in.

User\Administrator\AppData\Roaming\Microsoft\MMC

Then we log off and log back in with the same user account to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Jim,

its works but i must exclude old domain controller on all exchange servers. Thank you for your help.