I'm tracking down some warnings that appear when running Test-SystemHealth in the Management Shell. Here's the ones I'm having trouble solving: WARNING: The AD Topology service on server EXCHSRVR is hard-coded to use Active Directory domain controller server(s ): DC.SERVER.local. This configuration isn't recommended because it has limited fail-over options. WARNING: The Microsoft Exchange Active Directory Topology service on server EXCHSRVR is hard-coded to use the following Active Directory global catalog server(s): DC.SERVER.local. This configuration is not recommended because it provides limited fail-over options. WARNING: The AD Topology Service on server EXCHSRVR is hard-coded to use Active Directory Domain Controller server(s)DC.SERVER.local for configuration. This configuration is not recommended as it provides limited fail-over options. The Exchange Server is a single box in a 2008 R2 Domain environment. I'm not sure what details will help/needed. I've checked the Domain Controller settings under 'Organization Configuration' and 'Server Configuration' in the Exchange Management Console. It is set for default. Also, I've looked at 'Hub Transport' under 'Server Configuration' and can see in the properities, under the 'System Settings' tab DC.SERVER.local listed. But can't find where you can change it. Thanks for any help.

Can't be done in the GUI, has to be done in the Shell. Run this: get-exchangeserver -identity EXCHSRVR |fl Then look for the values starting "Static". If there are values in there, then null them out: set-exchangeserver -identity EXCHSRVR -StaticDomainControllers $null etc You will probably have to restart the Exchange services for the change to take effect. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi, simon's answer is correct. If you can not see any change after you actually do some change (static domain controller is still there), try to use this command: get-exchangeserver -identity EXCHSRVR -status |fl Because this is not an AD setting, we need to call in to the Active Directory Topology server to pull this information. The Exchange product group determined that there was too much of performance hit when we called into the Active Directory Topology service, which calls into the Remote Registry Service to warrant populating this information. To offset that, they added the –status switch. Please leave the message if you have any further question.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks Guys, I went ahead and ran 'get-exchangeserver' command. But, the static entries are all either blank or {}. Here's part of the report: ErrorReportingEnabled : StaticDomainControllers : {} StaticGlobalCatalogs : {} StaticConfigDomainController : StaticExcludedDomainControllers : {} CurrentDomainControllers : {} CurrentGlobalCatalogs : {} CurrentConfigDomainController : I'm going to keep searching on this and hope to track it down. Please let me know if you have any other suggestions. Thanks.

Hi, How many DC do you have? I think the setting relate to Active directory services depends on your Domain Topology. If you only have one DC, exchange server have to use that one only.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Jason, I have two Domain Controllers in the local office and a third in a second office (different subnet via WAN connection). So there's at least the two locals to pick from. James

Hi, So you can find 2 servers on one site and another server on the second site? check it from AD sites and Services You can use the Set-ExchangeServer cmdlet to configure a static list of domain controllers to which an Exchange 2010 server should bind or a list of domain controllers that should be excluded. Set-ExchangeServer -Identity EX-HUB01 -StaticDomainControllers:dc1.domain.com,dc2.domain.com -StaticGlobalCatalogs:dc1.domain.com,dc2.domain.com -StaticConfigDomainController:dc1.domain.com As a result, both of two servers on your local site are configured in the list. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Jason, I looked over and ran the Set-ExchangeServer command. Though it runs without error, I'm not seeing any changes in either Test-SystemHealth or Get-ExchangeServer. I'll try a reboot later today when I can bring the system down (hopefully) briefly and check again. Thanks. James

Did a reboot and had quite the Exchange meltdown. Had to revert back to a previous registery copy. Not sure if it was Set-ExchangeServer commands or something else. Looks like the Static pointers are pointing to both DCs. But Test-SystemHealth still complains there's only one DC hard-coded. Here's the full result back from Test-SystemHealth: [PS] C:\Windows\system32>Test-SystemHealth WARNING: The AD Topology service on server EXCHSRVR is hard-coded to use Active Directory domain controller server(s) DC1.local. This configuration isn't recommended because it has limited fail-over options. WARNING: The Microsoft Exchange Active Directory Topology service on server EXCHSRVR is hard-coded to use the following Active Directory global catalog server(s): DC1.local. This configuration is not recommended because it provides limited fail-over options. WARNING: The AD Topology Service on server EXCHSRVR is hard-coded to use Active Directory Domain Controller server(s) DC1.local for configuration. This configuration is not recommended as it provides limited fail-over options. WARNING: SSL is enabled on the IIS root directory of Client Access server EXCHSRVR.local. This will break HTTP redirection from other Client Access servers unless it is disabled. WARNING: The value for the 'SiteName' setting on server EXCHSRVR.local is hard-coded to . This configuration is not recommended. WARNING: The TEMP path on server EXCHSRVR.local is located on the same drive as the system partition. This may cause performance problems. Current TEMP path: %SystemRoot%\TEMP. WARNING: The TMP path on server EXCHSRVR.local is located on the same drive as the system partition. This may cause performance problems. Current TMP path: %SystemRoot%\TEMP. WARNING: Exchange server EXCHSRVR.local appears to be running as a virtual machine. Please review the system requirements detailed at http://go.microsoft.com/fwlink/?LinkId=148058. WARNING: Active Directory server DC2.local is down or unreachable. This error could also be the result of a network or permissions problem. Error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) WARNING: Active Directory server DC1.local is down or unreachable. This error could also be the result of a network or permissions problem. Error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Some of these warnings don't worry me (like the TMP path). Hopefully this helps with some ideas. (and I'm not blindly missing something) Damn Friday the 13th! James

Hi, WARNING: The value for the 'SiteName' setting on server EXCHSRVR.local ishard-coded to . This configuration is not recommended. http://technet.microsoft.com/en-us/library/aa995781(EXCHG.80).aspx WARNING: The AD Topology service on server EXCHSRVR is hard-coded to use ActiveDirectory domain controller server(s) DC1.local. This configuration isn't recommended because it has limited fail-over options http://support.microsoft.com/?kbid=250570 I will do some test later. For my consideration, check if you have Instance0 and Profiles\Default\UserDC1 in your registry. if there have, delete them. Don't forget backup registry before you do any change. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, WARNING: The value for the 'SiteName' setting on server EXCHSRVR.local ishard-coded to . This configuration is not recommended. http://technet.microsoft.com/en-us/library/aa995781(EXCHG.80).aspx WARNING: The AD Topology service on server EXCHSRVR is hard-coded to use ActiveDirectory domain controller server(s) DC1.local. This configuration isn't recommended because it has limited fail-over options http://support.microsoft.com/?kbid=250570 I will do some test later. For my consideration, check if you have Instance0 and Profiles\Default\UserDC1 in your registry. if there have, delete the them. Don't forget backup registry before you do any change. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Jason, I also came accross the 'sitename' article and will try it. I'm not sure what the make of the 2nd article. It explains a few things but the info and registery entries are out dated. Also, the entries on 'Instance0' and 'Profiles\Default\UserDC1' are present in the registery. I'll delete them out and see what happens. Thanks.