Active Directory, Exchange, Microsoft Clustering, Scripting, MOM, SQL. : AD Replication

Tips - 4

Nirmal Sharma — Tue, 03 Nov 2009 14:15:00 GMT

A Quick Tip To Disable "Initial Configuration Tasks List" This article explains how you can disable the Initial Configuration Task List at logon. What All Ports Are Required By Domain Controllers And Client Computers? This article explains the...(read more)

Tips - 3

Nirmal Sharma — Tue, 03 Nov 2009 14:03:00 GMT

Group Policy Offers New Functionality in Windows Server 2008 This article explains the improvements to the Group Policy in Windows Server 2008. Domain Controller Options Not Supported By RODC This article explains the DC Options which are not supported...(read more)

Tips - 2

Nirmal Sharma — Tue, 03 Nov 2009 13:44:00 GMT

A Quick Tip To Prevent Users From Accessing The Computer Tab This article explains a quick tip which you can use to prevent users from accessing the Computer Tab on My Computer property. A Quick Tip To Create A User Mode Process Dump File This article...(read more)

Tips - 1

Nirmal Sharma — Tue, 03 Nov 2009 13:18:00 GMT

Please check all the tips at WindowsNetworking.com: A Quick Tip To Strict FRS Replication To A Specific Port This article explains a registry heck which can be used to strict FRS Replication to a specific port. A Quick Tip To Strict AD Replication To...(read more)

Inter-Site Topology Generator Invalid

Nirmal Sharma — Tue, 31 Oct 2006 18:30:00 GMT

Scenario:

ISTG has invalid on all Domain Controller on the network after you demote a DC and trasfer roles and then rebuild it.

If demoted Domain Controller is the first DC in site - If yes then this DC holds the role - ISTG Server.

Initially the first server in the site becomes the ISTG owner and this this role is communicated by normal AD replication.

Moreover, this role is not changed automatically. Server holding ISTG role notifies other domain controllers about its presence by writing the *InterSiteTopologyGenerator* attribute in Configuration Naming Context at a specified interval.

Another fact is that another DC as an ISTG server doesn't take over unless it knows that DC hold ISTG server has failed.

To correct this issue:

You can edit the following registry value to modify this behaviour:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

Value Name: KCC site generator renewal interval (minutes)
Value Data: Number of minutes between updates to Active Directory

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
Value Name: KCC site generator fail-over (minutes)
Value Data: Time that must elapse before a new ISTG is selected, in minutes.