11.26. Transferring the ISTG to Another Server

Problem

You want to move the ISTG for a site to another domain controller. This happens automatically if you take the current ISTG offline, but you may want to transfer the role to a server that is more optimal in your environment.

Solution

Using a graphical user interface

  1. Open ADSI Edit.

  2. Connect to the CNC if it is not already displayed in the left pane.

  3. In the left pane, browse the Configuration NC Sites.

  4. Click on the site you want to transfer the ISTG for.

  5. In the right pane, double-click CN=NTDS Site Settings.

  6. Modify the interSiteTopologyGenerator attribute to include the NTDS Settings object of the domain controller you want to transfer the ISTG role to.

  7. Click OK.

Using VBScript

' This code forces a new ISTG in a site.
' ------ SCRIPT CONFIGURATION ------
' Name of site to transfer ISTG in
strSiteName = "<SiteName>"        ' e.g. Raleigh
' Site the new ISTG server is in
strNewISTGSite = "<ISTGSiteName>" ' e.g. Raleigh
' Common name of server object for new ISTG
strNewISTGName = "<DomainControllerName>" ' e.g. dc01 ' ------ END CONFIGURATION --------- set objRootDSE = GetObject("LDAP://RootDSE") set objSiteSettings = GetObject("LDAP://cn=NTDS Site Settings,cn=" & _ strSiteName & ",cn=sites," & _ objRootDSE.Get("ConfigurationNamingContext")) strCurrentISTG = objSiteSettings.Get("interSiteTopologyGenerator") objSiteSettings.Put "interSiteTopologyGenerator", _ "cn=NTDS Settings,cn=" & strNewISTGName & _ ",cn=servers,cn=" & strNewISTGSite & ",cn=sites," ...

Get Active Directory Cookbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.