|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() |
Step-by-Step Guide to Managing Active Directory Introduction This guide introduces you to administration of the Windows® 2000 Active DirectoryTM service and the Active Directory Users and Computers snap-in. This snap-in allows you to add, move, delete, and alter the properties for objects such as users, contacts, groups, servers, printers, and shared folders. PrerequisitesThis Software Installation and Maintenance document is based on Step-by-Step Guide to a Common Infrastructure for Windows 2000 Server Deployment Parts 1 and 2. Before beginning this guide, please build the common infrastructure, which specifies a particular hardware and software configuration. If you are not using the common infrastructure, you need to make the appropriate changes to this instruction set. You can run the Administrative Tools from the server, or you can run the tools from a computer running Windows 2000 Professional. The Administrative Tools are installed by default on all Windows 2000 domain controllers. You must be logged on as a user with administrative privileges to run through the procedures in this document. If you are working on a domain controller, the Active Directory Schema snap-in might not be installed. To install it:
On Windows 2000-based stand-alone servers or workstations, Active Directory Administrative Tools are optional. You can install them from Add/Remove Programs in Control Panel, using the Windows Components wizard, or from the ADMINPAK on the Windows 2000 Server or Professional CD. In this Step-by-Step Guide:
Using Active Directory Domains and Trusts Snap-in The Active Directory Domains and Trusts snap-in provides a graphical view of all domain trees in the forest. Using this tool, an administrator can manage each of the domains in the forest, manage trust relationships between domains, configure the mode of operation for each domain (native or mixed mode), and configure the alternative User Principal Name (UPN) suffixes for the forest. Starting the Active Directory Domains and Trusts Snap-in
Changing the Domain ModeWindows 2000 domains operate in one of two modes:
When a domain is first installed, it is in mixed mode. The mode of operation can be changed from mixed mode to native, but this is not reversible. In native mode, Windows NT 4.0 Domain Controllers cannot participate in the domain. You can change to native mode after making sure all domain controllers in your domain are running Windows 2000 Server. To switch to native mode
Using the Active Directory Users and Computers Snap-in
Figure 2 below displays the key components of the Active Directory Users and Computers snap-in. ![]() Figure 2. The Active Directory Users and Computers Snap-In Recognizing Active Directory ObjectsThe objects described in the following table are created during the installation of Active Directory.
You can use Active Directory to create the following objects.
Adding an Organizational UnitThis procedure creates an organizational unit (OU) in the Reskit domain. Note that you can create nested organizational units and there is no limit to the nesting levels. These steps follow the Active Directory structure begun in the Common Infrastructure Part One Step-by-Step Guide. If you did not create that structure, add the OUs and users directly under Reskit.com; that is, where Accounts is referred to below, substitute Reskit.com.
For the rest of the exercises in this guide, repeat steps 1 and 2 above to create additional organizational units, as follows:
When you are finished, you should have the following hierarchy as in Figure 3 below: ![]() Figure 3: New OUs Creating a User AccountThe following procedure creates the user account James Smith in the Construction OU. To create a new user account
You have now created an account for James Smith in the Construction OU. To add additional information about this user:
![]() Figure 5: Additional User Information Moving a User AccountUsers can be moved from one organizational unit to another in the same domain or a different domain. For example, in this procedure, James Smith moves from the Construction division to the Engineering division.
If you upgrade from an earlier version of Windows NT Server, you might want to move existing users from the Users folder to some of the OUs that you create. Creating a Group
Adding a User to a Group
![]() Figure 7: Add James Smith to the Tools Group Note: You can select multiple users or groups in this dialog by pressing the CTRL key as you click them. You can also type the name directly. If the name is ambiguous, a further list is displayed to confirm your selection. Alternatively, you can select the users from the results pane, right click then click Add members to a Group. Or you can click Add the selected objects to a group you specify on the snap-in toolbar. This may be more efficient for adding large numbers of members to a group. Publishing a Shared FolderAny shared network folder, including a Distributed File System (Dfs) folder, can be published in Active Directory. Creating a Shared folder object in the directory does not automatically share the folder. This is a two-step process: you must first share the folder, and then publish it in Active Directory.
To publish the shared folder in the directory
The Engineering organizational unit appears as shown in Figure 8 below: ![]() Figure 8: Engineering OU contents Users can now see this volume while browsing in the directory. To browse the directory
Publishing a PrinterThis section describes the processes for publishing printers in a Windows 2000 Active Directory-based network. Windows 2000 Printers You can publish a printer shared by a computer running Windows 2000 by using the Sharing tab of the printer Properties dialog box. By default, Listed in the directory is enabled. The directory is the Active Directory data store. (This means that Windows 2000 Server publishes the shared printer by default.) The print subsystem will automatically propagate changes made to the printer attributes (location, description, loaded paper, and so forth) to the directory. Note: For this section of this guide, you must have a printer available and know its IP address. If you do not have an IP printer, you can still run through these procedures, substituting the correct port for Standard TCP/IP Port. To add a new printer
After you create the printer, the printer is automatically published in Active Directory and the Listed in the Directory check box is selected. You might also need to find the server from which a printer is shared out before adding it to the machine you're working on. To locate a printer
Note: If you don't know the name, location, or model of the printer, you can simply click the Find Now button, and all the printers in the domain you selected will be listed in the list box. Adding Non-Windows 2000 Printers You can publish printers shared by operating systems other than Windows 2000 in the directory. The simplest way to do this is to use the pubprn script. This script will publish all the shared printers on a given server. It is located in the \winnt\system32 directory. To publish a printer shared from a non-Windows 2000 server using the pubprn.vbs script
This script copies only the following subset of the printer attributes:
You can add other attributes by using the Active Directory Users and Computers snap-in. Note that you can rerun pubprn and it will update rather than overwrite existing printers. Alternatively, you can use the Active Directory Users and Computers snap-in to publish printers on non-Windows 2000 servers. To use the Active Directory Users and Computers snap-in to publish printers
End users can realize the benefit of printers being published in the directory because they can browse for printers, submit jobs to those printers, and install the printer drivers directly from the server. To browse and use printers in the directory
Creating a Computer ObjectA computer object is can be created automatically when a computer joins a domain. You can also create the computer object before the computer joins a domain.
Optionally, you can select which users are permitted to join a computer to the domain. This allows the administrator to create the computer account and someone with lesser permissions to install the computer and join it to the domain. Renaming, Moving, and Deleting Objects
Creating Nested GroupsYou can use nested groups providing that you are running the Active Directory in Native Mode. Nested groups are easier to manage, and thus reduce administrative overhead.
To check the nested groups
Finding Specific Objects Rather than browsing the list of objects in the results pane, it is often more efficient to find specific objects that meet a certain criteria. In this example you will find all users who have a surname of "Smith" and are in the Marketing organizational unit.
Filtering a List of Objects Filtering the list of returned objects from the directory can allow you to manage the directory more efficiently. The filtering option allows you to restrict the types of objects returned to the snap-in–for example, you can choose to view only users and groups, or you may want to create a more complex filter. If an OU has more than a specified number of objects, the filter function allows you to restrict the number of objects displayed in the results pane. You can use the Filter function to configure this option. In this example, you create a filter designed to retrieve users only.
After you click OK, whenever you view a container, it retrieves user and group objects only. For example, if you now view the Engineering OU, the shared folder Engineering Specs will no longer be displayed. The description bar above the contents of the right pane will show that the list is filtered. Important NotesThe example company, organization, products, people, and events depicted in this step-by-step guide is fictitious. No association with any real company, organization, product, person, or event is intended or should be inferred. This common infrastructure is designed for use on a private network. The fictitious company name and DNS name used in the common infrastructure are not registered for use on the Internet. Please do not use this name on a public network or Internet. The Active Directory structure for this common infrastructure is designed to show how Windows 2000 features work and function with the Active Directory. It was not designed as a model for configuring an Active Directory for any organization—for such information see the Active Directory documentation. This feature information was obtained from the Microsoft Windows 2000 website at http://www.microsoft.com/windows2000 and are linked from ActiveWin.com for your convenience and is subject to Microsoft's copyright. For the most accurate information please visit the official site.
| ![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||