Active Directory Application Mode End User License Agreement
How to use these release notes
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 End User License AgreementThis 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 notesThis 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 feedbackWe appreciate your input on this release. To submit feedback or suggestions about this release, contact the Microsoft directory services newsgroup at | Back to Top |
Finding helpFor help in using Active Directory Application Mode, this release includes the following documentation:
| Back to Top |
Corrections to the Active Directory Application Mode Administrator's GuideThe 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 ModeThe 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:
Description of the ApplicationPartitionsToReplicate answer file parameterIn "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 instanceIn "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 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 instanceAdding 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
Note
| Back to Top |
Correction to the Active Directory Application Mode Step-by-Step Reviewer's GuideThe 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 accountThe 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 siteYou 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 releaseThis release of Active Directory Application Mode requires one the following platforms:
*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 versionsYou 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
| Back to Top |
Running Active Directory Application Mode on Windows XP ProfessionalThe following considerations apply when you run Active Directory Application Mode on Windows XP Professional. Active Directory Application Mode on Windows XP Professional in a workgroupWhen 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 Windows XP Professional and ADSIFor 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 ProfessionalWhen 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:
For more information about well-known SIDs, see "Well-known SIDs" at the Microsoft MSDN Web site. | Back to Top |
Active Directory Application Mode ToolsThe following information applies to the Active Directory Application Mode administration tools that are provided with this release. ADAM ADSI Edit limitationsADAM ADSI Edit has the following limitations:
New tools in Active Directory Application ModeDsdbutil 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
Dsmgmt
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 versionsThe following Active Directory Application Mode administration tools are not currently available in localized language versions:
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 ConsiderationsThe 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 installationIf 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 identificationActive 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 accountWhen 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
Note
ADAM dsHeuristics attributeThe 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
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
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 softwareIt is recommended that you exclude the following ADAM files from scans by antivirus software:
By default, these files are located in: where instancename equals the ADAM instance name that you specified during install. Using Active Directory Application Mode with Authorization ManagerTo 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:
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 ConsiderationsUsing SSL certificates with ADAMTo 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
Allowing the setting of passwords over a non-SSL connectionBy 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
Some failed binds to Active Directory Application Mode incorrectly reported as successfulIf 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 |
CopyrightInformation 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, The names of actual companies and products mentioned herein may be the trademarks of their respective owners. | Back to Top |