---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Set up ADAMSync

# Set up ADAMSync {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

ADAMSync is included with Windows
Server 2003 R2. Download and install ADAMSync if you are using a different OS.

## Extending the schema

The ADAM schema needs to be extended to support ADAMSync.

1. Run the following command from c:\\windows\\adam to import the ADAMSync schema extensions. You may have to change the server:port and add credentials if the current user doesn't have access. See the AdamSyncMetadata.ldf file for details.

       ldifde -i -f MS-AdamSyncMetadata.LDF -s localhost:50000 -j . -c "cn=Configuration,dc=X" #configurationNamingContext

2. Do the same with MS-AdamSchemaW2k3.ldf to support Windows 2003 attributes.

       ldifde -i -u -f MS-AdamSchemaW2K3.LDF -s localhost:50000 -j . -c "cn=Configuration,dc=X" #configurationNamingContext

{#c_SetUpADAMSync__ol_o2j_3jr_bq}

## Recommended schema changes

Here are some additional schema changes we recommend.

1. Open a new MMC console and add the ADAM Schema Snap-in.
2. Connect to the ADAM instance.
3. Expand the Classes folder and locate the userProxy class, open Properties.
4. Verify the following optional attributes on the Attributes tab, add any that do not already exist.
   * company
   * department
   * givenNane
   * mail
   * physicalDeliveryOfficeName
   * sAMAccountName
   * sn
   * telephoneNumber
   * title
   * userAccountControl
   * userPrincipalName
   {#c_SetUpADAMSync__ul_fhx_xjr_bq}
5. Restart the ADAM Service to enable the new settings.
{#c_SetUpADAMSync__ol_u2c_vjr_bq}