Exchange 2003 Ent. linked to a particular domain controller
We had a domain controller go down with other domain controllers still available on the network. However, Exchange went down because there were registry entries pointing it directly to the domain controller that was not available. HKEY_LOCAL_MACHINE,
CurrentControlSet, Services, MSExchangeDSAccess, Instance0, Value name = ConfigDCHostName and then the Value data had the name of the DC that went down. We also found two more entries just below that within the registry under HKEY_LOCAL_MACHINE, CurrentControlSet,
Services, MSExchangeDSAccess, Profiles, Default, disk1.domain.net.1 (and .2) where there were Value Names of HostName with a Value Data of the DC that went down.
We should be able to bring a domain controller down without it negatively impacting our Exchange server as long as another domain controller is available on the network (with Global Catalog, DNS, WINs, etc).
Thoughts?
April 27th, 2010 3:46pm
My thought is to not statically configure Exchange to use any particular domain controller. Exchange is not so configured, so I would surmise that you or someone else created the static entry. You are, of course, certainly
welcome to remove it. See this KB for more information: http://support.microsoft.com/kb/830930 .
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.
"wknight80" wrote in message
news:677ee313-9966-4081-94cb-a38dd3a5e9d0...
We had a domain controller go down with other domain controllers still available on the network. However, Exchange went down because there were registry entries pointing it directly to the domain controller that was not available. HKEY_LOCAL_MACHINE,
CurrentControlSet, Services, MSExchangeDSAccess, Instance0, Value name = ConfigDCHostName and then the Value data had the name of the DC that went down. We also found two more entries just below that within the registry under HKEY_LOCAL_MACHINE, CurrentControlSet,
Services, MSExchangeDSAccess, Profiles, Default, disk1.domain.net.1 (and .2) where there were Value Names of HostName with a Value Data of the DC that went down.
We should be able to bring a domain controller down without it negatively impacting our Exchange server as long as another domain controller is available on the network (with Global Catalog, DNS, WINs, etc).
Thoughts?
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2010 7:05pm
Hello,
Hardcoding Exchange server to specific DC is not a good option.
Please find the below steps
1. HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess.
2. Delete the key "Instance0".
3. Delete the key "Profiles".
4. Start Microsoft Exchange System Attendant Service
If possible reboot the exchange server
Thanks,
Dinesh.
April 27th, 2010 7:55pm