Release Notes for Active Directory® Application Mode


Active Directory Application Mode End User License Agreement

How to use these release notes

Providing feedback

Finding help

Corrections to the Active Directory Application Mode Administrator's Guide

Correction to the Active Directory Application Mode Step-by-Step Reviewer's Guide

Active Directory Application Mode on the Microsoft Web site

Requirements and limitations of this release

Running Active Directory Application Mode on Windows XP Professional

Active Directory Application Mode Tools

Operational Considerations

Security Considerations

© 2003 Microsoft Corporation. All rights reserved.

Active Directory Application Mode End User License Agreement

This software is subject to the End User License Agreement ("EULA") of Active Directory Application Mode (ADAM). The EULA can be found in the file systemroot\ADAM\adamEula.txt on the computer on which ADAM is installed. If you do not agree to the terms of that EULA, you may not use this software.

Back to Top

How to use these release notes

This document contains new and updated information about this release of Active Directory® Application Mode (ADAM) that is not available in the documentation accompanying the release. Read this document before installing and using this release of Active Directory Application Mode.

Back to Top

Providing feedback

We appreciate your input on this release. To submit feedback or suggestions about this release, contact the Microsoft directory services newsgroup at microsoft.public.windows.server.active_directory.

Back to Top

Finding help

For help in using Active Directory Application Mode, this release includes the following documentation:

  • Active Directory Application Mode Step-by-Step Reviewer's Guide

    Provides a step-by-step guide for ADAM installation and basic administrative procedures. This guide is available in the ADAM release download in a Microsoft Word file called Revguide_adam.doc. If you do not have Microsoft Word available, you can download Microsoft Office file viewers at the Microsoft Web site. (http://www.microsoft.com/)

  • Active Directory Application Mode Administrator's Guide

    Contains conceptual information and administrative procedures. This guide is available in the ADAM program group on the Start menu after you install Active Directory Application Mode.

  • Active Directory Application Mode documentation in the Platform SDK

    Contains Active Directory Service Interfaces (ADSI) programming information for Active Directory Application Mode. This documentation is available in the ADAM release download as a compiled Help file called Adamsdk.chm.
  • Microsoft Support Web site

    Visit the Microsoft Support Web site(http://www.microsoft.com/) for new Knowledge Base articles about Active Directory Application Mode.

Back to Top

Corrections to the Active Directory Application Mode Administrator's Guide

The following corrections apply to the Active Directory Application Mode Administrator's Guide that is included with this release of Active Directory Application Mode.

Answer file for unattended uninstall of Active Directory Application Mode

The example answer file that is provided in "Performing an unattended removal of an ADAM instance" in the Active Directory Application Mode Administrator's Guide is incomplete. The following example is complete, and it includes the heading that is required at the beginning of the file:

[ADAMUninstall]
Administrator=cohovineyard\administrator
AdministratorPassword=adminpassword

Description of the ApplicationPartitionsToReplicate answer file parameter

In "Installing an ADAM replica from media" in the Active Directory Application Mode Administrator's Guide, the description of the ApplicationPartitionsToReplicate answer file parameter is incorrect. The description should read as follows:

The application directory partitions (from the restored files) that you want to install. Setting ApplicationPartitionsToReplicate equal to * installs all application directory partitions that exist in the configuration set. When setting this parameter to specific application directory partitions, those partitions are restored from the restore files, or from another ADAM instance, if the partition exists in the configuration set but not in the restored files.

Procedure for listing directory partitions located on an ADAM instance

In "To list the directory partitions, or naming contexts, of an ADAM instance" in the Active Directory Application Mode Administrator's Guide, the dsmgmt: command shown as domain management should be partition management.

Additional parameter for use with "adaminstall"

In addition to the parameters described in "Performing an unattended install of an ADAM instance" in the Active Directory Application Mode Administrator's Guide, you can use the /strict parameter with adaminstall to cause ADAM Setup to treat warnings as errors.

Procedure for adding an application partition to an ADAM instance

Adding application directory partitions by using ldp.exe is described in "To add an application directory partition" in the Active Directory Application Mode Administrator's Guide. In addition to using ldp.exe, you can use dsmgmt to add an application directory partition to an ADAM instance.

To add an application directory partition using dsmgmt

  1. Open an ADAM tools command prompt.
  2. At the command prompt, type: dsmgmt.

  3. At the dsmgmt: prompt, type: partition management.

  4. At the partition management: prompt, type: connections.

  5. At the server connections: prompt, type: connect to server computername:portnumber

    where computername is the computer on which the ADAM instance is running and portnumber is the Lightweight Directory Access Protocol (LDAP) or Secure Sockets Layer (SSL) communications port used by the ADAM instance.

  6. At the server connections: prompt, type: quit.

  7. At the partition management: prompt, type: create nc app_dn objectclass computername:portnumber

    where app_dn is the distinguished name of the application directory partition that you want to create, objectclass is the object class (for example, organization or container) that you want to use for the application directory partition, and computername:portnumber represents the ADAM instance on which you want to create the application directory partition.

    For example, to create the application directory partition "o=Microsoft,c=US" on an ADAM instance running on the local computer at port 389, type:

      partition management: create nc o=Microsoft,c=US organization localhost:389

Note

  • The attribute value assertion (for example, "o=", or "cn=") you specify at the beginning of the distinguished name for the new application directory partition must match the object class you specify in objectclass.
Back to Top

Correction to the Active Directory Application Mode Step-by-Step Reviewer's Guide

The following correction applies to the Active Directory Application Mode Step-by-Step Reviewer's Guide that is included with this release of Active Directory Application Mode.

Modifying the ADAM service account

The ADAM Step-by-Step Reviewer's Guide incorrectly states that the ADAM service account cannot be modified after ADAM is installed. The ADAM service account can be modified after ADAM installation by using dsdbutil, as described in "To modify the service account used by an ADAM instance" in the Active Directory Application Mode Administrator's Guide.

Back to Top

Active Directory Application Mode on the Microsoft Web site

You can find the latest product information and white papers about Active Directory Application Mode on the Active Directory Application Mode section of the Microsoft Web site. (http://www.microsoft.com/windowsserver2003/adam/)

Back to Top

Requirements and limitations of this release

This release of Active Directory Application Mode requires one the following platforms:

  • Windows Server 2003, Standard Edition
  • Windows Server 2003, Enterprise Edition
  • Windows Server 2003, Datacenter Edition
  • Windows XP Professional with Service Pack 1 (SP1)*

*For use on computers running Windows XP Professional, Active Directory Application Mode has been designed primarily as a personal data store. It is recommended that you run Active Directory Application Mode on the Windows Server 2003 family if you need scalability to support a growing number of simultaneously connected clients and if you have ADAM instances that you intend to use as centralized directory servers.

Remove previous ADAM versions

You must remove any previous versions of Active Directory Application Mode on your computer before you install this release of Active Directory Application Mode.

To remove a previous version of ADAM from your computer

  1. In Control Panel, click Add or Remove Programs.
  2. Click Change or Remove Programs, click the ADAM instance that you want to uninstall, and then click Remove.
Back to Top

Running Active Directory Application Mode on Windows XP Professional

The following considerations apply when you run Active Directory Application Mode on Windows XP Professional.

Active Directory Application Mode on Windows XP Professional in a workgroup

When you install Active Directory Application Mode on a computer running Windows XP Professional that is joined to a workgroup, you must set the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\forceguest to 0. (The default is 1.) Otherwise, users connecting to ADAM over the network are forced to a security context of Guest, and binds to ADAM fail. For more information, see "To enable ADAM binding to ADAM instances running on Windows XP Professional computers joined to a workgroup" in the Active Directory Application Mode Administrator's Guide.

Windows XP Professional and ADSI

For complete Active Directory Service Interfaces (ADSI) functionality with Windows XP Professional, download and install the hotfix described in article Q817583, "Active Directory Services Does Not Request Secure Authorization Over an SSL Connection," in the Microsoft Knowledge Base.

User tokens when running Active Directory Application Mode on Windows XP Professional

When an ADAM instance is running on Windows XP Professional, the user tokens do not include the following well-known SIDs, which are included in user tokens when Active Directory Application Mode is running on Windows Server 2003:

  • Local (S-1-2-0)

    Users who log on to terminals that are locally (physically) connected to the system.
  • SECURITY_NETWORK_RID (S-1–5-2)

    Users who can log on across a network. This is a group identifier.
  • SECURITY_INTERACTIVE_RID (S-1–5–4)

    Users who can log on for interactive operation. This is a group identifier.

For more information about well-known SIDs, see "Well-known SIDs" at the Microsoft MSDN Web site.

Back to Top

Active Directory Application Mode Tools

The following information applies to the Active Directory Application Mode administration tools that are provided with this release.

ADAM ADSI Edit limitations

ADAM ADSI Edit has the following limitations:

  • No support for LDAP simple bind

    ADAM users can only bind to ADAM using LDAP simple binds. Therefore, you cannot bind to ADAM as an ADAM user using ADAM ADSI Edit.
  • No support for SSL connections

    If you want to perform administrative tasks on an ADAM instance over a Secure Sockets Layer (SSL) connection, you must use Ldp.exe.
  • No support for editing attributes of numeric string type

    You cannot use ADAM ADSI Edit to edit attributes whose type is numeric string.

New tools in Active Directory Application Mode

Dsdbutil and dsmgmt are Active Directory Application Mode tools that, together, provide functionality that is equivalent to ntdsutil for Active Directory. The following are brief descriptions of the functions that these tools provide:

Dsdbutil

  • Authoritative restore
  • DSRM password management
  • List ADAM instances
  • Set LDAP and SSL ports
  • Change service account

Dsmgmt

  • Metadata cleanup
  • Naming context (partition) management
  • FSMO roles
  • Enable/disable SSL

Dsdiag is an Active Directory Application Mode tool that provides functionality that is equivalent to dcdiag in Active Directory.

Some Active Directory Application Mode administration tools not available in localized language versions

The following Active Directory Application Mode administration tools are not currently available in localized language versions:

  • Dsacls.exe
  • Dsdiag.exe
  • Ldp.exe

However, localized Help is available for these tools in the Active Directory Application Mode Administrator's Guide, and the tools can be used with localized versions of Active Directory Application Mode.

Back to Top

Operational Considerations

The following operational considerations apply to this release of Active Directory Application Mode.

The Active Directory Application Mode Setup Wizard leaves behind an empty ADAM program group after a failed installation

If the Active Directory Application Mode Setup Wizard fails during the first attempt to install Active Directory Application Mode on a computer, it leaves behind an empty ADAM program group on the Start/Programs menu. You must delete this empty program group before attempting to install Active Directory Application Mode a second time. To delete the empty ADAM program group, right-click the group, and then click Delete.

ADAM RootDSE attribute for user identification

Active Directory Application Mode includes an attribute on the RootDSE object that contains an attribute called msDS-principalName. This attribute returns the name of the currently logged on user (equivalent to the first SID of the RootDSE tokenGroups attribute, resolved to a name). For Windows security principals, the attribute returns this information in the format domain\username. For ADAM security principals, as well as ADAM bind redirection proxy objects, the attribute returns the distinguished name of the ADAM object. For an anonymous user, the attribute returns "NT AUTHORITY\ANONYMOUS LOGON".

IFM installs and the ADAM service account

When you specify an ADAM service account for an install from media (IFM) that differs from the ADAM service account used on the ADAM instance from which the backup was taken, the new ADAM instance may fail to start, reporting Jet Error - 1032. This issue can be resolved by manually assigning the necessary permissions on the folders containing the ADAM database (Adamntds.dit) and log (*.log) files to the ADAM service account.

To assign the necessary database and log file permissions to a newly assigned ADAM service account

  1. On the computer where the ADAM instance is installed, open Windows Explorer.
  2. For each of the folders containing the ADAM database (Adamntds.dit) and ADAM log (*.log) files, do the following:
    1. Right-click the folder, and then click Properties.
    2. On the Security tab, in Group or User names, select (or add to the list, if necessary) the account being used as the ADAM service account.
    3. In Permissions, select the following permissions:
      • Read & Execute
      • Read
      • Write
      • List Folder Contents
  3. On the Security tab, click Advanced, and then click the following:
    • Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.
    • Replace permission entries on all child objects with entries shown here that apply to child objects.
  4. To exit, click OK twice.
  5. Open Services, and start the ADAM instance.

Note

  • By default, the Adamntds.dit and *.log files are located in:

    \%ProgramFiles%\Microsoft ADAM\instancename\data

    where instancename equals the ADAM instance name that you specified during install.

ADAM dsHeuristics attribute

The dsHeuristics attribute on the Directory Service object in the configuration directory partition (CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,CN={GUID}) controls certain aspects of Active Directory Application Mode operations.

The following dsHeuristics settings apply specifically to ADAM:

1st character:

Unlike Active Directory, Active Directory Application Mode does not disable write caching by default. You can force the disabling of write caching by setting the first character (from the left) in dsheuristics to 2. The default value is 0, which leaves the write cache enabled for ADAM. (In Active Directory, a value of 0 disables the write cache.)

7th character:

ADAM does not accept anonymous bind requests by default. To enable anonymous Lightweight Directory Access Protocol (LDAP) operations in ADAM, you must set the seventh character (from the left) in dsHeuristics to 2.

Note

  • In addition, assign permissions so that anonymous users have access to the appropriate objects in the directory. To grant the Read permission on all objects in a given directory partition to anonymous users, you can simply add the built-in security principal Anonymous (from the local computer) to the Readers group on that directory partition.

9th character:

The 9th character controls how the userPassword attribute is used, and it has 3 possible values:

0 - (Default value.) Causes the userPassword attribute to be used as a write-only password attribute that cannot be read and to be used as a write-alias for unicodePwd. Any object class containing the userPassword attribute must also have the unicodePwd attribute as a mayContain attribute.

Note

  • In Active Directory, the default setting of the 9th character in dsHeuristics is also 0. However, in Active Directory, a setting of 0 causes the userPassword attribute to be used as a regular attribute.

1 - Causes the userPassword attribute to be used as a password attribute. (This is equivalent to using the default setting of 0.)

2 - Causes the userPassword attribute to be used as a regular attribute that can be read and written, with no relationship existing between the userPassword attribute and the unicodePwd attribute.

Using ADAM with antivirus software

It is recommended that you exclude the following ADAM files from scans by antivirus software:

  • Adamntds.dit
  • ADAM *.log files
  • Temp.edb
  • Edb.chk

By default, these files are located in:

\%ProgramFiles%\Microsoft ADAM\instancename\data

where instancename equals the ADAM instance name that you specified during install.

Using Active Directory Application Mode with Authorization Manager

To use Active Directory Application Mode as a data store for Microsoft Authorization Manager, you must import into the ADAM schema the optional Ms-azman.ldf file that is provided with Active Directory Application Mode. For more information about the optional .ldf files that are provided with Active Directory Application Mode, see "Importing LDIF files during setup" in the Active Directory Application Mode Administrator's Guide. For more information about Authorization Manager, see "Role-Based Access Control for Multi-tier Applications Using Authorization Manager" on the Microsoft TechNet Web site. (http://www.microsoft.com/)

To import Ms-azman.ldf manually using Ldifde.exe, type the following at a command prompt:

c:\windows\adam\ldifde -i -f MS-AZMan.ldf -s
computername:portnumber -b username domain password -k -j . -c
"CN=Schema,CN=Configuration,DC=X" #schemaNamingContext

where computername:portnumber represents the computer and port number on which the ADAM instance is running.

This syntax is also available in the first line of the Ms-azman.ldf file.

Back to Top

Security Considerations

Using SSL certificates with ADAM

To enable Secure Sockets Layer (SSL) connections to Active Directory Application Mode, you must have certificates installed on the computer running Active Directory Application Mode and also on the clients connecting to Active Directory Application Mode. You can obtain certificates from a trusted certification authority (CA). Or, for internal use, you can issue certificates from your own internal CA by installing and using certificate services on Windows 2000 Server or Windows Server 2003.

For information about setting up and using certificate services, see Certificate Services on the Microsoft TechNet Web site (http://www.microsoft.com/) For more information about enabling LDAP over SSL, see article Q321051, "How to Enable LDAP over SSL with a Third-Party Certification Authority", on the Microsoft Support Web site. (http://www.microsoft.com/)

Note

  • When using certificates with Active Directory Application Mode, you must assign the ADAM service account full access to the certificates that are installed on the computer where the ADAM instance is running. The certificate store is located in the directory Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys.

Allowing the setting of passwords over a non-SSL connection

By default, and to help ensure the highest level of password security, passwords for Active Directory Application Mode users can only be set over an SSL connection. You can remove this requirement on an ADAM instance using the dsmgmt administration tool, as described in the following procedure. Note that disabling the SSL requirement greatly reduces the security of ADAM user passwords.

To allow or deny password operations over a non-SSL connection

Note

  • You must be logged on as the ADAM administrator to complete this procedure.
  1. Open an ADAM tools command prompt.
  2. At the command prompt, type: dsmgmt
  3. At the dsmgmt: prompt, type: ds behavior
  4. At the ds behavior: prompt, type: connections
  5. At the server connections: prompt, type:

    connect to server computername:portnumber

    where computername:portnumber represents the ADAM instance that you want to configure.
  6. At the server connections: prompt, type: quit
  7. At the ds behavior: prompt, do one of the following:
    • To allow password settings over a non-SSL connection, type:

        allow passwd op on unsecured connection
    • To deny password settings over a non-SSL connection, type:

        Deny passwd op on unsecured connection
  8. Type quit at the ds behavior: prompt and at the dsmgmt: prompt.

Some failed binds to Active Directory Application Mode incorrectly reported as successful

If the Guest account on a computer on which Active Directory Application Mode is running is enabled, unsuccessful bind attempts to ADAM may be reported as successful, even though the bind attempt actually failed. To prevent these unsuccessful binds from being reported as successful, you can disable the Guest account on computers running Active Directory Application Mode. For information about disabling the Guest account, search for "guest account" in Help and Support Center for Windows Server 2003.

Back to Top

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2003 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Back to Top