Having read the highlights of this thread, I'm immediately confused as to why you don't simply delete the errant reg. value[1] since it's functionality, as I've understood it to this point, is relevant to members, not DCs.
As for deleting the NETLOGON.DNS and .DNB files; I've found this a solution in the more extreme of DC/DDNS issues, none of which were remotely related to the "DynamicSiteName" value ... having said that, deleting the NETLOGON.DNS has proved a successful remedy more often than not and has shown itself to yield no detrimental lingering behaviors. [1] to clarify my use of the term "value": when used in the context of the registry it defines a named placeholder to maintain some data of a defined type -- in this case "DynamicSiteName", the content of the value is commonly referred to as the "data". "Keys" are the registry equiv. of folders. -- Dean Wells MSEtechnology * Email: [EMAIL PROTECTED] http://msetechnology.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M. Sent: Saturday, August 06, 2005 6:48 PM To: [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC Hi Steve, Thanks for your additional pointers! All of the DCs (using the AD Sites and Services GUI) all show this server in the site it was moved to. Yet, the moved DC seems to think that it still in the old site. There are registry entries in the registry that still identify the old site. My goal is to get this DC to a stable condition and then DCPromo it out. Since I don't plan on having this server in any other site, maybe the "sitename" registry would be an OK way to go? I am still confused why things don't happen automatically in a logical fashion. I would expect the netlogon.dns file to reflect the new site. Yet it doesn't. This DC was the only one in the old site. Would that make a difference? I recall at one time (for a completely different reason) deleting the netlogon.dns (and netlogon.dnb too?) files was a solution. Would that be a wise thing to do? Since there are no more computers in the old site, would it make sense at this point to just delete the site or would that mess up the situation even more? I will check out your references tomorrow. (I am at a family function right now and was really anxious to see if anyone had responded to my query.) Thanks for the help! -mike ________________________________ From: [EMAIL PROTECTED] on behalf of Steve Linehan Sent: Sat 8/6/2005 10:02 AM To: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC Ok I see in your original message that you state you did try to move it via sites and services, missed that. When you did this what server was the Sites and Services MMC focused on your DC or another DC in the domain? Did the UI update to show the server in the correct site after the move or did it simply remain the same? If you focus on another DC and make the change and then wait for replication does the site get updated? Is the server that you are trying to move healthy from a replication standpoint? The SiteName parameter was put in the registry for troubleshooting and testing purposes and while it can be used it can also cause confusion later if you decide to make another change as that value always overrides. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] on behalf of Steve Linehan Sent: Sat 8/6/2005 9:48 AM To: [email protected]; [email protected]; [email protected]; [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC In addition just so no one thinks this recently changed the behavior was also described in the Windows 2000 Distributed Systems Guide as well: http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/ en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en -us/distrib/DistSystems.asp "If a domain controller's IP address or the subnet-to-site associations are changed after Active Directory is installed on the server computer, the domain controller does not change sites automatically. It must be moved to the new site manually if that site is the desired location." Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] on behalf of Steve Linehan Sent: Sat 8/6/2005 9:44 AM To: [email protected]; [email protected]; [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC The following documentation describes this behavior as well: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/ activedirectory/stepbystep/adsrv.mspx "All newly promoted DCs are placed in the Site container that applies to them at the time of installation. For example, a server bound for California might have been initially built and configured in the Maui, Hawaii, data center-therefore, the Configure Your Server wizard places the server in the Maui site. After it arrives in California, the server object can be moved to the new site using the Sites and Services snap-in." If you do not want to use the UI a script was included in the Branch Office Guide called movesite.vbs that will accomplish the same thing. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] on behalf of Steve Linehan Sent: Sat 8/6/2005 9:38 AM To: [email protected]; [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC We do not recommend changing the dynamicsitename parameter and hard coding it using the SiteName parameter is also not recommended since later you may forget that this is set and no matter what you do the DC will assume it is in the site you put in the key even if that site does not really exist. As I stated below Domain Controllers are special when they are promoted they look at the site and subnet mappings and place themselves in the correct site. After that you must manually move them through the Sites and Services Snapin. Simply launch the MMC navigate to the old site and look under the servers folder, select the server you want to move and drop him in your new site. Are you stating that you did this and the server did not show up in the new site? There are many reasons why DCs do not dynamically change sites most revolving around keeping a stable replication environment. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] on behalf of Thommes, Michael M. Sent: Sat 8/6/2005 7:09 AM To: [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC Hi Steve, (Maybe I should add this issue to the "OT-Biggest AD Gripes" thread!) Each of the actions I've taken so far, in my mind, should have gotten this DC back to the appropriate site. But it still thinks it should be in the original site! One item I find is the HKLM\SYSTEM\CCS\Services\Netlogon\Parameters\DynamicSiteName still points to "site2". I did run across a Microsoft article that talks about this and to never change a dynamically determined value. Instead. you can create a a new value in the same place in the registry named "SiteName", REG_SZ with the value you want. Have you (or someone else) found the need to do this? Mike Thommes ________________________________ From: [EMAIL PROTECTED] on behalf of Steve Linehan Sent: Fri 8/5/2005 4:51 PM To: [email protected] Subject: RE: [ActiveDir] concern about re-ip'd DC DC do not change their sites dynamically. You will need to move the DC to its new site manually via sites and services. When they are promoted they look at the site definitions but after that it is a manual process. Thanks, -Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M. Sent: Friday, August 05, 2005 3:57 PM To: [email protected] Subject: [ActiveDir] concern about re-ip'd DC Hi, I have a Domain Controller that was located in a different AD site (site2) via its IP (naturally!). This DC was shut down about 2 weeks ago. I have since powered it back up offnet, given it a new IP (which is defined as a different site (site1)), and rebooted it on net. Some hours later, it still seems to think it is in the original site (site2), at least that is what I see in AD Sites and Services. Some minutes later...based on some googled and eventide.net info, I put in a specific subnet entry in ADSS for this new IP and associated it with site1. A reboot produced no change. So then I went to AD Sites and Services and did a GUI move of this DC from site2 to site1. Another reboot - no change. I see the dynamically created netlogon.dns file STILL has site2 identified! Any hints on how to "convince" this DC that it should be in site1? Anybody else experience this type of behavior? TIA! Mike Thommes List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
