Site - Registry Entry

  • Thread starter Thread starter Brendon Rogers
  • Start date Start date
B

Brendon Rogers

We're running a single native W2K active directory domain with multiple
sites. We have a central IT dept where we build and prepare servers as
domain controllers before sending them to the relevant site. Once on site we
do the necessaries in AD Sites & Services to create a new site and associate
it with the new DC.

I am already aware that FRS doesn't sort out its new site-membership
automatically and I was wondering if there are any other gotchas?

Why I ask is I notice on one of these relocated DC's the following registry
entry:

HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName -
this is still set to the server's original site location where it was built
and not its new site where it is now located.

However, if I run NLTEST /DSGETSITE on the server it correctly reports its
new site. REPLMON.EXE also shows the servers in their correct new sites.
 
This can also be define in a Group Policy an a few related settings.

Administrative Templates\System\Net Logon\Site Name

Specifies the Active Directory site to which computers belong. An Active
Directory site is one or more well-connected TCP/IP subnets that allow
administrators to configure Active Directory access and replication. To
specify the site name for this setting, click Enabled, and then enter the
site name. When the site to which a computer belongs is not specified, the
computer automatically discovers its site from Active Directory. If this
setting is not configured, it is not applied to any computers, and computers
use their local configuration.

Administrative Templates\System\Net Logon\DC Locator DNS Records\Automated
Site Coverage by the DC Locator DNS SRV Records

Determines whether domain controllers (DC) will dynamically register DC
Locator site-specific SRV records for the closest sites where no DC for the
same domain exists (or no Global Catalog for the same forest exists). These
DNS records are dynamically registered by the Net Logon service, and they
are used to locate the DC. If this setting is enabled, the DCs to which
this setting is applied dynamically register DC Locator site-specific DNS
SRV records for the closest sites where no DC for the same domain, or no
Global Catalog for the same forest, exists. If you disable this setting,
the DCs will not register site-specific DC Locator DNS SRV records for any
other sites but their own. If this setting is not configured, it is not
applied to any DCs, and DCs use their local configuration.

Administrative Templates\System\Net Logon\DC Locator DNS Records\Sites
Covered by the GC Locator DNS SRV Records

Specifies the sites for which the global catalogs (GC) should register
site-specific GC locator DNS SRV resource records. These records are
registered in addition to the site-specific SRV records registered for the
site where the GC resides, and records registered by a GC configured to
register GC Locator DNS SRV records for those sites without a GC that are
closest to it. The GC Locator DNS records and the site-specific SRV
records are dynamically registered by the Net Logon service, and they are
used to locate the GC. An Active Directory site is one or more
well-connected TCP/IP subnets that allow administrators to configure Active
Directory access and replication. A GC is a domain controller that contains
a partial replica of every domain in Active Directory. To specify the sites
covered by the GC Locator DNS SRV records, click Enabled, and enter the
sites' names in a space-delimited format. If this setting is not
configured, it is not applied to any GCs, and GCs use their local
configuration.

Administrative Templates\System\Net Logon\DC Locator DNS Records\Sites
Covered by the DC Locator DNS SRV Records

Specifies the sites for which the domain controllers (DC) register the
site-specific DC Locator DNS SRV resource records. These records are
registered in addition to the site-specific SRV records registered for the
site where the DC resides, and records registered by a DC configured to
register DC Locator DNS SRV records for those sites without a DC that are
closest to it. The DC Locator DNS records are dynamically registered by
the Net Logon service, and they are used to locate the DC. An Active
Directory site is one or more well-connected TCP/IP subnets that allow
administrators to configure Active Directory access and replication. To
specify the sites covered by the DC Locator DNS SRV records, click Enabled,
and then enter the sites names in a space-delimited format. If this setting
is not configured, it is not applied to any DCs, and DCs use their local
configuration.


Administrative Templates\System\Net Logon\DC Locator DNS Records\Sites
Covered by the Application Directory Partition Locator DNS SRV Records

Specifies the sites for which the domain controllers (DC) housing
application directory partition should register the site-specific,
application directory partition-specific DC Locator DNS SRV resource
records. These records are registered in addition to the site-specific SRV
records registered for the site where the DC resides, and records registered
by a DC configured to register DC Locator DNS SRV records for those sites
without a DC that are closest to it. The application directory partition
locator DNS records and the site-specific SRV records are dynamically
registered by the Net Logon service, and they are used to locate the
application directory partition-specific DC. An Active Directory site is one
or more well-connected TCP/IP subnets that allow administrators to configure
Active Directory access and replication. To specify the sites covered by
the DC Locator application directory partition-specific DNS SRV records,
click Enabled, and then enter the site names in a space-delimited format.
If this setting is not configured, it is not applied to any DCs, and DCs use
their local configuration.

Other registery keys related to theres policys may can be any help full!

HKLM\Software\Policies\Microsoft\Netlogon\Parameters!SiteName
HKLM\Software\Policies\Microsoft\Netlogon\Parameters!AutoSiteCoverage
HKLM\Software\Policies\Microsoft\Netlogon\Parameters!SiteCoverage
HKLM\Software\Policies\Microsoft\Netlogon\Parameters!GcSiteCoverage
HKLM\Software\Policies\Microsoft\Netlogon\Parameters!NdncSiteCoverage


--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

Brendon Rogers said:
We're running a single native W2K active directory domain with multiple
sites. We have a central IT dept where we build and prepare servers as
domain controllers before sending them to the relevant site. Once on site we
do the necessaries in AD Sites & Services to create a new site and associate
it with the new DC.

I am already aware that FRS doesn't sort out its new site-membership
automatically and I was wondering if there are any other gotchas?

Why I ask is I notice on one of these relocated DC's the following registry
entry:
HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName -
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top