8.11. Binding to the Default Container for Computers

Tip

This recipe requires the Windows Server 2003 domain functional level.

Problem

You want to bind to the default container that new computers objects are created in.

Solution

Using a graphical user interface

  1. Open LDP.

  2. From the menu, select Connection Connect.

  3. For Server, enter the name of a domain controller (or leave blank to do a serverless bind).

  4. For Port, enter 389.

  5. Click OK.

  6. From the menu, select Connection Bind.

  7. Enter credentials of a domain user.

  8. Click OK.

  9. From the menu, select View Tree.

  10. For the DN, enter:

    <WKGUID=aa312825768811d1aded00c04fd8d5cd,<DomainDN>>

    where <DomainDN> is the distinguished name of a domain.

  11. Click OK.

  12. In the left menu, you can now browse the default computers container for the domain.

Using a command-line interface

With tools like netdom, if there is an option to only specify the name of the computer, and not its DN or parent container, the default computers container is typically used.

Using VBScript

' This code illustrates how to bind to the default computers container.
' ------ SCRIPT CONFIGURATION ------
strDomain = "<DomainDNSName>" ' e.g. apac.rallencorp.com ' ------ END CONFIGURATION --------- ' Computer GUID as defined in ntdsapi.h Const ADS_GUID_COMPUTRS_CONTAINER = "aa312825768811d1aded00c04fd8d5cd" set objRootDSE = GetObject("LDAP://" & strDomain & "/RootDSE") set objCompContainer = GetObject("LDAP://<WKGUID=" & _ ADS_GUID_COMPUTRS_CONTAINER & "," & _ objRootDSE.Get("defaultNamingContext") & ">" ) WScript.Echo ...

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.