Installing ADAM

Applies To: Windows Server 2003 R2

You can install an ADAM instance either by using the Active Directory Application Mode Setup Wizard or by using the ADAM unattended installation process. In the first exercise, you use the Active Directory Application Mode Setup Wizard to install ADAM. In Managing Configuration Sets, you use an unattended installation to install an ADAM replica.

Note

To install ADAM, you must log on to your computer using an account that belongs to the local Administrators group.

In this exercise, you first install ADAM, and then you install an ADAM instance by using the Active Directory Application Mode Setup Wizard.

To install ADAM

  1. To install ADAM, log on as an administrator, click Start, point to Control Panel, and then click Add or Remove Programs.

  2. Click Add/Remove Windows Components.

  3. Select the check box next to Active Directory Services, and then click Details.

  4. Select the check box next to Active Directory Application Mode (ADAM), click OK, and then click Next.

  5. Review the message that appears. Based on the contents of message, do one of the following:

    • If the message "You have successfully completed the Windows Component Wizard" appears, click Finish.

    • If an error message appears, make a note of the error, click Finish, and then review the ADAM event messages in Event Viewer.

To install an ADAM instance by using the Active Directory Application Mode Setup Wizard

  1. To start the Active Directory Application Mode Setup Wizard, click Start, point to All Programs, point to ADAM, and then click Create an ADAM instance. The first page of the Active Directory Application Mode Setup Wizard looks like the following:

    ADAM Setup Wizard Welcome Page

  2. On the Welcome to the Active Directory Application Mode Setup Wizard page, click Next.

  3. On the Setup Options page, you can choose whether to install a unique ADAM instance or join an existing configuration set. Because you are installing the first ADAM instance, click A unique instance (as shown in the following), and then click Next. Later, you will create additional ADAM instances and join them in a configuration set.

    ADAM Setup Wizard Setup Options page

  4. On the Instance Name page, provide a name for the ADAM instance that you are installing. This name is used on the local computer to uniquely identify the ADAM instance. For this exercise, simply accept the default name of instance1, and then click Next.

    ADAM Setup Wizard Instance Name page

  5. On the Ports page, specify the communications ports that the ADAM instance uses to communicate. ADAM can communicate using both LDAP and Secure Sockets Layer (SSL); therefore, you must provide a value for each port. For this exercise, accept the default values of 389 and 636, and then click Next.

    ADAM Setup Wizard Ports page

    Note

    If you install ADAM on a computer where either of the default ports is in use, the Active Directory Application Mode Setup Wizard automatically locates the first available port, starting at 50000. For example, Active Directory uses ports 389 and 636, as well as ports 3268 and 3269 on global catalog servers. Therefore, if you install ADAM on a domain controller, the Active Directory Application Mode Setup Wizard provides a default value of 50000 for the LDAP port and 50001 for the SSL port.

  6. On the Application Directory Partition page, you can create an application directory partition (or naming context) by clicking Yes, create an application directory partition. Or, you can click No, do not create an application directory partition, in which case you must create an application directory partition manually after installation. For this exercise, click Yes, create an application directory partition. When you create an application directory partition, you must provide a distinguished name for the new partition. For this exercise, type o=Microsoft,c=US as the distinguished name (as shown below), and then click Next.

    ADAM Setup Wizard Application Directory Partition

    Note

    ADAM supports both X.500-style and Domain Name System (DNS)-style distinguished names for top-level directory partitions.

  7. On the File Locations page, you can view and change the installation directories for ADAM data and recovery (log) files. By default, ADAM data and recovery files are installed in %ProgramFiles%\Microsoft ADAM\instancename\data, where instancename represents the ADAM instance name that you specify on the Instance Name page. For this exercise, click Next to accept the default file locations.

    ADAM Setup Wizard File Locations page

    Important

    When installing ADAM on a computer running Windows XP, you must install these files on the same logical volume. When installing ADAM on Windows Server 2003 and Windows Server 2003 R2 in a production environment, it is recommended that you install the files on separate physical disks.

    Note

    ADAM setup installs program files and administration tools in %windir%\ADAM.

  8. On the Service Account Selection page, you select an account to be used as the service account for ADAM. The account that you select determines the security context in which the ADAM instance runs. Unless you are installing ADAM on a domain controller, the Active Directory Application Mode Setup Wizard defaults to the Network Service account. For this exercise, click Next to accept the Network service account default. Or, if you are installing ADAM on a domain controller, click This account, and then select a domain user account to use as the ADAM service account.

    ADAM Setup Wizard Service Account Selection page

    Note

    You can change the ADAM service account after ADAM is installed by using the Dsmgmt command-line tool. When you install ADAM on a domain controller, you must select a domain user account as the ADAM service account.

  9. On the ADAM Administrators page, you select a user or group to become the default administrator for the ADAM instance. The user or group that you select will have full administrative control of the ADAM instance. By default, the Active Directory Application Mode Setup Wizard specifies the currently logged on user. You can change this selection to any local or domain account or group on your network. For this exercise, click the default value of Currently logged on user, and then click Next.

    ADAM Setup Wizard ADAM Administrators page

  10. On the Importing LDIF Files page, you can import into the ADAM schema two .ldf files containing user class object definitions. Importing these user class object definitions is optional. However, these object definitions are required later in this guide so, you should import these definitions now:

    1. Click Import the selected LDIF files for this instance of ADAM.

    2. Click MS-InetOrgPerson.LDF, and then click Add.

    3. Click MS-User.LDF, and then click Add.

    4. Click MS-UserProxy.LDF, click Add, and then click Next.

    ADAM Setup Wizard Importing LDIF Files page

  11. The Ready to Install page gives you an opportunity to review your installation selections. After you click Next, the Active Directory Application Mode Setup Wizard begins copying files and setting up ADAM on your computer.

    ADAM Setup Wizard Ready to Install page

  12. When the Active Directory Application Mode Setup Wizard finishes installing ADAM, it displays this message: “You have successfully completed the Active Directory Application Mode Setup Wizard.” When the Completing the Active Directory Application Mode Setup Wizard page appears, click Finish to close the wizard.

Note

If the Active Directory Application Mode Setup Wizard does not complete successfully, an error message describing the reason for the failure appears on the Summary page.

If an error occurs in the Active Directory Application Mode Setup Wizard before the Summary page, you can review the error message that appears. In addition, you can click Start, click Run, and type either of the following:

%windir%\Debug\adamsetup.log

%windir%\Debug\adamsetup_loader.log

The Adamsetup.log and Adamsetup_loader.log files contain information that can help you troubleshoot the cause of an ADAM setup failure.