Microsoft® Windows® 2000 Scripting Guide
« Previous | Next »
Knowing which computers in your organization are global catalog servers is very helpful for administering Active Directory efficiently.
Because global catalog servers are required for user authentication, it is important to have an adequate number of global catalog servers at a site to handle the volume of authentication requests and a quick connection to handle each request efficiently. If a remote office does not have its own global catalog server and is connected over a slow network link, authentication of the site s users will be slow.
However, having too many global catalog servers can slow down your network by creating unnecessary replication traffic. Global catalog servers contain information about every item in the forest and can generate a considerable amount of replication data. A remote office that has its own global catalog servers and is connected over a slow network link can provide efficient authentication to its local users, but it might have trouble communicating with other sites because of the quantity of replication data moving across the network link.
You can identify global catalog servers by using ADSI.
Listing 9.17 contains a script that identifies global catalog servers by using ADSI. To carry out this task, the script must perform the following steps:
The rootDSE is a well-known and reliable location on every domain controller. You can use rootDSE to get distinguished names for the domain container, schema container, and configuration container, as well as other information about the server and the contents of its directory information tree.
This attribute represents the distinguished name of the NTDS Settings object for the directory server.
The NTDS settings represent the data in Active Directory that define a computer as a domain controller.
Listing 9.17 Identifying Global Catalog Servers
|
|
Send us your feedback | « Previous | Next » |