Administration Guide

Active Directory Synchronization

On this page

Active Directory synchronization imports persons from a directory into Alloy Navigator and keeps them in step with it. It is made of three parts:

  • A directory connection, a Domain Credentials record: the server and the credentials of one directory service.
  • A synchronization job, which the Automation Server runs on its schedule. For the Automation Server and schedules, see Jobs and Schedules.
  • Two workflow service actions on the Person class: one creates persons, the other updates them. Apart from the link to a person's manager, what a run writes to a person record is decided by these actions, which are ordinary workflow configuration. For service actions, see Workflow Overview.

The directory can be Active Directory or another LDAP directory. The same directory connections are also used when technicians sign in with DOMAIN\UserName; see Authentication Methods. Importing persons from Microsoft Entra ID does not use these directory connections or synchronization jobs; see Microsoft Entra ID Import. For the other integrations, see Integrations Overview.

You set up synchronization in the Settings App and in the Admin Center. For how the two applications relate, see Admin Center and Settings App.

Prepare Windows

Two settings outside Alloy Navigator can be needed on the Windows computers that connect to the directory: the logon right of a Connect as account and, for a secure connection, a registry value of the Windows LDAP client.

Logon right of a Connect as account

When a job names a Windows account in Connect as, the job and Test Account Settings... log that account on with the network logon type on the Automation Server computer. A job run from the command line does the same on the computer that runs ImportContacts.exe; see From the command line.

In Windows, the right to log on with the network logon type is the user right Access this computer from the network, and the user right Deny access to this computer from the network takes precedence over it. For the logon types and the rights they require, see Microsoft's Account Rights Constants. Alloy Navigator does not grant these rights.

To check the rights on the computer that runs the job:

  1. Sign in to the computer as an administrator.
  2. Open Local Security Policy and go to Local Policies > User Rights Assignment.
  3. Right-click Access this computer from the network and choose Properties. If neither the account nor a group it belongs to is listed, click Add User or Group..., add the account, and click OK.
  4. Right-click Deny access to this computer from the network and choose Properties. Make sure that neither the account nor a group it belongs to is listed.

When a setting is grayed out in Local Security Policy, a Group Policy Object controls it, and a local change would be overwritten at the next Group Policy update. A change to a user right applies the next time the account logs on; the computer does not need a restart.

Secure connection to an LDAP server

When a secure connection to an LDAP server fails because the server's certificate does not cover the name used to reach the server, for example an alias name, consider the Windows LDAP client setting that Microsoft describes in LDAPS connection fails with event ID 36884. Set it on each computer that opens the secure connection: the Automation Server computer and the web server computer.

  1. Start Registry Editor.
  2. Locate the subkey HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LDAP.
  3. Create a new REG_DWORD value named UseHostnameAsAlias, and set it to a value other than zero, for example 1.
  4. Exit Registry Editor, and then restart the computer.

In the Settings App

Go to Services > Active Directory Integration. It has three pages: Synchronization, the list of jobs; Domain Credentials; and Logs. The page is available with the Active Directory Integration permission; see Permissions Reference. The top-level Logs also lists the runs, as AD Synchronization.

Add a directory connection

  1. On the Domain Credentials page, click New. The Domain Credentials window opens.
  2. In Domain:, enter the short domain name that exactly matches the domain part of DOMAIN\USER user names.
  3. Under Directory Server (domain controller), in Directory Service:, choose Active Directory or LDAP Server.
  4. Enter the Server Name: and the Port:. Selecting Secure Connection sets the port to 636, and clearing it sets 389; you can still change the port. A new record starts at port 389 with Active Directory.
  5. For LDAP Server, enter the Users DN:.
  6. Enter the Username: and the Password:.
  7. To check the settings, click Test Connection. The test first checks that the server answers on the port, then connects to the directory.
  8. Click OK. The list reloads with the new record selected.

Domain:, Server Name:, Port:, and Username: are mandatory; the password is not.

A directory connection can also be created from Users & Security > SSO Providers: choose Domain in the New drop-down. The SSO Providers list shows directory domains beside the single sign-on providers.

On the Domain Credentials page, the list shows the domain name, server name, port, and secure connection of each record; the password is not shown. Edit, or opening a row, opens the record in the same window, titled Domain Credentials [<domain>]. Delete refuses to delete a record that a synchronization job uses, either with a message that names the job or with a database error.

Create a synchronization job

  1. On the Synchronization page, click New. The Active Directory Synchronization dialog opens, with the tabs Settings, Processing, and Sessions. The Sessions tab is available once the job is saved.
  2. Enter the Name:. A new job is named "Active Directory Import", or the first free "Active Directory Import (1)", "Active Directory Import (2)", and so on. Enabled is selected for a new job.
  3. In Domain:, choose the directory connection. On a computer that is a domain member, the list also offers Currently logged-in domain.
  4. Check the LDAP Path:. It is filled in from the domain when you choose one. For an Active Directory connection, the ellipsis button opens the Windows container browser. Check Path checks the path.
  5. Under Schedule, click Change... and set the schedule.
  6. If Connect as is shown, choose The Automation Server startup account, or choose This account: (with Find...) and enter the account and its Password:. Test Account Settings... checks the account. Connect as is shown only while the selected directory connection has no user name.
  7. On the Processing tab, set the options:
    • Under Ignore user records where:, select the users to skip: User account is disabled, 'E-mail' field is empty, 'Office' field is empty, and Logon name is in UPPERCASE (system accounts).
    • Under Processing Options:, select the values the job hands to the service actions: Create Self Service Portal accounts, Create Organizations, and Create Locations.
    • In the Workflow group, choose the service action in For new users: Create Persons: and in For existing users: Update Persons:. Both are empty on a new job. For the actions of the Default Workflow, see The Default Workflow.
  8. Save the job.

The name, the LDAP path, and the schedule are required. On a new job, the three Processing Options: are selected, and so are the Ignore boxes for an empty e-mail, an empty office, and an uppercase logon name; disabled accounts are not ignored.

A banner in the dialog warns when the Automation Server is not running.

NOTE: In Alloy Navigator Cloud, the Settings App's scheduler has a minimum interval of 240 minutes, or 4 hours. See Administering Alloy Navigator Cloud.

Connect as messages. The job, and Test Account Settings..., log the named account on with a network logon. When Windows refuses that logon type, Test Account Settings... reports "The Automation Server cannot run the ... using the specified Windows account. Make sure that this Windows account has the "Log on as a batch job" user right." The job log itself records "This Windows account does not have the right to log on using the network logon type." The account therefore needs the right that the job log names, to log on using the network logon type. Alloy Navigator does not grant logon rights to the account itself; for the Windows user rights, see Logon right of a Connect as account. A wrong password is reported as "The Automation Server cannot run the ... under the specified Windows account." When a privilege is missing, the message asks that the startup account be a member of the local Administrators group.

LDAP path and port. The LDAP path holds the server and the port. Selecting Secure Connection on the connection moves its port to 636, but a path chosen at port 389 keeps the old port until you choose the domain again or edit the LDAP Path:. The run goes on with the path; the mismatch is added to the error message only when reading the directory then fails because the server is not operational or the path is invalid, and on Check Path only when the path check fails. The text names the server name, the port number, or both, and ends "Ensure these values match (for example, reselect the Domain in the job settings)."

Older jobs. Opening a job written in an older format offers to upgrade it to an LDAP path. If you decline, the LDAP path stays empty and a banner names the old server and start OU. A job whose LDAP path is empty reads the directory through the server of its directory connection, and the run fails with an invalid command line error when no server name is available.

Run and manage jobs

The Synchronization list offers New, Open, Run, Terminate, Enable, Disable, Delete, and Copy Job ID (GUID) to Clipboard.

  • Run starts one selected job now, whatever its schedule and its Enabled box. It is available while the Automation Server runs. When the request cannot be delivered, the job is queued to run as soon as possible, and a message reads "Since your Settings App and the Automation Server are installed on separate computers, it may take some time to test your settings. Please wait until the job has completed, and then check the session log to make sure that it runs as expected." When the Automation Server answers the request with an error, the error reads "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started." with the reason.
  • Terminate stops one selected job that is running, after a confirmation.
  • Enable, Disable, and Delete act on several selected jobs; Delete asks for a confirmation. Disabling a job clears its next run date; enabling it again computes a new one.

While the list is on screen, it reloads changed jobs every ten seconds by default. Refresh, or F5, reloads it at once.

Check the results

Every run is one row in the AD Synchronization Log:

  • The job's Sessions tab shows the runs of that job, with the log's open, delete, and refresh commands.
  • The Logs page of Active Directory Integration lists the runs of every job.

A row shows the run date, comments, duration, total users, created persons, updated persons, up-to-date persons, errors, and the job name.

In the Admin Center

Go to Services and Integrations > Active Directory Integration. It opens on the Synchronization tab and has the tabs Synchronization, Domain Credentials, and Logs. The sidebar also lists the runs as AD Synchronization. A directory connection can also be created with Domain in the New menu of the SSO providers screen.

The page is available with the Active Directory Integration permission. The Admin Center's list of directory connections, their creation, update, and deletion, and the connection test are available to an administrator who holds either of these permissions: Active Directory Integration or Security Management. See Permissions Reference.

Add a directory connection

  1. On the Domain Credentials tab, click New. The New Domain Credentials panel opens.
  2. In Domain, enter the short domain name that exactly matches the domain part of DOMAIN\USER user names.
  3. Under Directory Server (domain controller), in Directory Service:, choose Active Directory or LDAP Server.
  4. Enter the Server Name and the Port. To connect with SSL, select Secure Connection.
  5. For LDAP Server, enter the Users DN.
  6. Enter the Username and the Password.
  7. To check the settings, click Test Connection.
  8. Save the record.

Domain, Server Name, Port, and Username are marked as required.

The Domain Credentials tab lists the directory connections with the columns Domain Name, Server Name, Port, and Use SSL. Use SSL shows a check mark for a connection that uses SSL and nothing for one that does not. Click a domain name to open the record for editing. The tab offers New, Edit, and Delete. Edit is available when exactly one row is selected, and Delete when one or more rows are selected. The list has no Copy command.

  • The connection test connects to the directory with Negotiate authentication for Active Directory and Basic authentication for an LDAP server.
  • A record that a synchronization job uses is not deleted: the delete is refused with a message that names the job, or it ends with a database error.

The Domain form of the SSO providers screen follows these rules:

  • The secure connection setting is a single check box, with no STARTTLS choice. Selecting it sets Port to 636, and clearing it sets 389, replacing any port you typed.
  • Base DN is required only when Directory Service is LDAP. For Active Directory, the box is disabled.
  • Test Connection first validates Domain, Username, and Server Name, and Base DN for LDAP; when a value fails validation, the server is not contacted. The result opens in an information or error dialog that shows the server's own message text.

Create a synchronization job

  1. On the Synchronization tab, click New. The New Synchronization panel opens, with the tabs Settings and Processing. The Sessions tab appears once the job is saved.
  2. On the Settings tab, enter the Name. A new job is named "Active Directory Import", or "Active Directory Import (1)", "Active Directory Import (2)", and so on when the name is already used. Enabled is selected for a new job.
  3. Under Active Directory, in Domain, choose the directory connection. When the web server runs on Windows, the list can also offer Web server domain (<host>), the web server's own domain, with port 389 and no credentials.
  4. Enter the LDAP Path. The ellipsis button opens the domain tree. Check Path checks the path.
  5. Under Schedule, the field shows the job's schedule. To change it, click the button beside the field; the Schedule panel opens. A note beside the field gives the server's offset from UTC, for example "Server time (UTC-07:00)".
  6. If Connect as is shown, choose The Automation Server startup account, or choose Specified: and enter the Account and its Password. Test Account Settings... checks the account. Connect as is shown only when Web server domain (<host>) is selected in Domain.
  7. On the Processing tab, set the options:
    • In the Workflow group, choose the service action in For new users: Create Persons and in For existing users: Update Persons. For the actions of the Default Workflow, see The Default Workflow.
    • In the Options group, under Ignore user records where:, select the users to skip: User account is disabled, 'E-mail' field is empty, 'Office' field is empty, and Logon name is in UPPERCASE (system accounts).
    • Under Processing Options:, select the values the job hands to the service actions: Create Self Service Portal accounts, Create Organizations, and Create Locations.
  8. Click Ok.

The name and the LDAP path are required, and so are the account and the password when Specified: is chosen. A missing value is reported as, for example, 'The "LDAP Path" field is mandatory, it can't be left blank'.

On a new job, the three Processing Options: are selected, and so are the Ignore boxes for an empty e-mail, an empty office, and an uppercase logon name; disabled accounts are not ignored. The schedule of a new job is set to every day, once at 12:00 AM, starting on the day you create it.

When neither Create Persons nor Update Persons is chosen, saving the job asks "You didn't choose any action to be performed by the job. The job will make no changes in the database. Are you sure you want to proceed?" Yes saves the job; No returns you to the Processing tab.

When the Automation Server is not running, the form shows "Warning. For this job to be executed, the Automation Server must be set up and running."

Manage synchronization jobs

The Admin Center edits the same synchronization jobs as the Settings App. The Synchronization tab lists them and offers New, Edit, Delete, Enable, Disable, Run, Terminate, and a refresh button. It has no Copy command, and no Open or Copy Job ID (GUID) to Clipboard command as in the Settings App.

  • To open a job, select one job and click Edit. The job form opens on its Settings tab, which holds the schedule, continues with Processing, and ends with Sessions, which appears once the job exists and shows the job's runs.
  • Delete asks "Are you sure you want to delete the selected item?", or, when several jobs are selected, names their number. Yes deletes; No keeps the jobs.
  • Run and Terminate need a running Automation Server. For running, terminating, enabling, and disabling jobs in the Admin Center, see Jobs and Schedules.

In Alloy Navigator Cloud, the job form holds the schedule to a minimum interval of 240 minutes, or 4 hours. In addition, when you add or update a job, the Admin Center saves any repeating interval of its schedule as 240 minutes, or 4 hours. For example, a job set to run every 8 hours is saved to run every 4 hours. See Administering Alloy Navigator Cloud.

Check the results

The Logs tab lists the runs of every job, newest first by default, with the columns Run Date, Job Name, Comments, Duration (in hours, minutes, and seconds), Total Users, Created Persons, Updated Persons, and Errors. Click the run date to open the run in a details pane. The tab also has a settings page for the number of days the log is stored.

From the command line

The Automation Server runs each job with ImportContacts.exe. You can run a job the same way:

ImportContacts.exe /AccessKey="Key_Name" /RunID="Job_GUID" [/Log="File_Name"]
  • /AccessKey names the Database Access Key of the database, registered on the computer, as the Connection Manager lists it under Key Name:. Without a key the run ends with "Database connection failed. Please check with your Alloy Navigator administrator that your Database Access Key is valid."
  • /RunID is the job's GUID, which the Settings App's Copy Job ID (GUID) to Clipboard copies.
  • /Log is an optional name for the temporary log file, created under %ALLUSERSPROFILE%\Alloy Software\<product>\Logs\Services. Without it, the name is random.

The Administrative Tools package installs ImportContacts.exe in the Bin folder of its installation folder (Alloy Software\Alloy Navigator under Program Files). Every computer that runs it needs the registered Database Access Key.

A command-line run ignores the job's Enabled box, and the job's Connect as setting applies. At the end, the log is added to the job's AD Synchronization Log and the file is deleted, whether or not there were errors. The file stays on disk when the access key could not be read or the upload fails. An empty log is deleted without being added. Without /RunID, the program prints its usage, and when it is given more than one argument it also fails as an invalid command line.

Run the command on a schedule

To run a job from the command line on a schedule, create a task in Windows Task Scheduler. Create it on a computer that has access to the SQL Server that hosts the Alloy Navigator database and to the directory server, and that has ImportContacts.exe and the registered Database Access Key.

If the job is to run only from Task Scheduler, clear its Enabled box, so that the Automation Server does not also run it on the job's schedule. A command-line run ignores the box.

  1. Open Task Scheduler, for example by typing Task Scheduler in the Windows search box. If you are prompted for an administrator password or confirmation, provide it.
  2. To keep the task in a folder of its own, right-click Task Scheduler Library, choose New Folder, and create the folder. This step is optional.
  3. In the Actions pane, click Create Basic Task.
  4. Enter a name for the task and an optional description, and click Next.
  5. Click Daily, Weekly, Monthly, or One time, click Next, set the schedule, and click Next.
  6. Click Start a program, and click Next.
  7. Click Browse, select ImportContacts.exe, enter the command-line parameters described above as the arguments, and click Next.
  8. Click Finish.

The account that runs the task must have sufficient rights to read the directory when the job's directory connection has no user name and Connect as is The Automation Server startup account. To run the task under a dedicated account, open the task's properties and, on the General tab, click Change User or Group... under Security options. When the job names an account in Connect as, that account needs the logon right described in Logon right of a Connect as account.

How synchronization works

The directory connection

A directory connection is either Active Directory or LDAP Server. The choice changes how Alloy Navigator connects:

Active Directory LDAP Server
Connects as The user name as entered, with secure authentication uid=<Username>,<Users DN>, with a simple bind
Login attribute sAMAccountName uid
Users DN: in the Settings App Not used; cleared when you save Mandatory
Objects read as users Only objects of the directory's user class Every object that exposes user properties

Secure Connection adds SSL to either kind. No particular LDAP product is required, but a server that refuses a simple bind of this shape cannot be used. For a Windows registry setting that a secure connection can need, see Secure connection to an LDAP server.

When you save a directory connection in the Settings App's Domain Credentials window, the password you entered is stored encrypted.

The Settings App and the Admin Center test a connection in different ways, so a successful test in one application does not show that the other can connect.

The synchronization job

A job reads one LDAP path, the subtree it imports users from. To import from a second container, create a second job.

The job runs under the Automation Server service account. When you name a Windows account in the job, the job runs as that account for the whole run instead. The named account is used only when the job's directory connection has no user name; otherwise the connection's credentials are used.

The create and update service actions decide what the job does:

  • In the Settings App and in the Admin Center, a job saved with neither action is accepted after a warning, and then does nothing. The run logs a warning for each missing action and stops only when both are missing.
  • With only a create action, the job never updates persons. With only an update action, it never creates them.

What one run does

A run reads the LDAP path recursively, going into every organizational unit and container, and treats only user objects as candidates. A path with no users produces a "users not found" line in the log, not an error.

Each directory user then passes five filters, in this order. The first filter that fails is written to the log as a Conclusion line, and the user is skipped. The job options below carry their Settings App labels.

Order The user is skipped when Controlled by
1 The directory account is disabled User account is disabled
2 The login is empty Always
3 The e-mail attribute is empty 'E-mail' field is empty
4 The login is all upper case and not all lower case Logon name is in UPPERCASE (system accounts)
5 The office attribute is empty 'Office' field is empty

For a user who passes, the run looks for the person record (see How a re-import finds the person), then runs the update action for a person it found or the create action for a new one.

  • A user already created or updated earlier in the same run is skipped.
  • A user whose directory identity (see How a re-import finds the person) is held by an inactive person record is not imported. The run logs an error, "matches an inactive Person record ... Operation aborted", and adds it to the error count, unless the directory account is itself disabled; then it logs an informational line instead.
  • A person counts as updated only when the record actually changed. Otherwise the log says the person was up to date, with no changes, and counts the person separately.
  • When a user has a manager in the directory, the run finds the manager's person record. If the manager does not exist yet and the service action maps the manager field, the run imports the manager first. The link to the manager is written directly, not through workflow, so no workflow trigger, history entry, or notification fires for it.
  • The job itself creates no organizations and no locations. Creating them is left to the service action, which the job options for organizations and locations steer (see What the job hands to workflow).
  • The job itself does not delete or deactivate a person who is no longer in the directory. It processes only the users the directory returns, so deleting such a person or changing their status is arranged outside the job.

Disabled directory accounts reach Alloy Navigator as a Disabled value, which the default mapping passes to the update action only. A disabled user who has no person record is never created, whatever the disabled-account option says. When the account state cannot be read, the run logs a warning and handles the account as enabled. For a directory other than Active Directory, accounts are always handled as enabled.

How a re-import finds the person

Every imported person keeps the identity of its directory object in a hidden field: the object's GUID, in the form {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, or its distinguished name when the directory returns no GUID. The job writes this identity through the create and update actions: it adds a mapping for the identity field to both actions unless the action already maps that field. You therefore cannot switch the identity off in the mapping, but mapping the identity field to something else redirects it.

The run matches each directory user in two stages:

  1. Identity. The user's GUID and distinguished name are both compared, ignoring case, with the identities of the imported persons. A person imported by distinguished name therefore still matches once the directory returns a GUID.
  2. Person matching. Only when no identity matches, the run uses the person matcher, described in Person Matching Reference. For this job:
    • Inactive persons are excluded.
    • A match by full name considers only persons that do not yet carry a directory identity, so two directory users with the same display name cannot end up on one record by name. A match by login or by e-mail can still find an already imported person.
    • When the job has a create action, a login, e-mail, or name match is tried only if the create action maps that field.
    • The name match is skipped when the full name equals the e-mail address.
    • A match by name alone is enough.

When you create a technician account from a directory user in the Settings App's account wizard and the directory returns a GUID, the new person record already carries the directory identity, so the first synchronization run matches it by identity.

Field mapping

The field mapping belongs to the service action. It is edited on the service action's Field Mapping tab. For the directory actions, the list of directory attributes there has four extra entries: Manager (Link to Person), Full Login, memberOf (raw), and Disabled, which is offered only for the update action. The attribute list shows only attributes whose type fits the target field, sorted by caption.

The job reads six attributes itself: the login, the e-mail address, and the full, first, middle, and last names. It takes them from the create action's mapping, or from the update action's when there is no create action, and uses the product's default for a field the action does not map. Every other field is written only through the action's own mapping.

The product's default mapping is:

Person field Directory attribute
Full name cn
First name givenName
Middle name initials
Last name sn
Job title title
Business phone telephoneNumber
Home phone homePhone
Mobile phone mobile
Fax facsimileTelephoneNumber
Notes info, only when the notes are empty
Picture thumbnailPhoto
Primary e-mail mail
Primary login Full Login
Manager Manager (Link to Person)

Some rows are not person fields but named values that the service action uses:

Named value Directory attribute
Location Name physicalDeliveryOfficeName
OU Name and OU Parent department and company
City, State, PostalCode, Country, Street I (an uppercase i), st, postalCode, co, and streetAddress
Disabled Disabled, for the update action only

On a service action's Field Mapping tab, Default replaces the rows with this default mapping after you confirm the replacement. The service actions of the Default Workflow map City differently; see The Default Workflow.

The job fills four values itself, just before the action runs: the full login, the manager, the disabled flag, and the directory identity. The full login is <NetBIOS domain>\<login> while the login is mapped to Full Login. When the login is mapped to another attribute, the job takes that attribute's value and keeps only the part from the first backslash onward.

Some attributes get special handling:

  • Photographs. A field mapped to thumbnailPhoto or jpegPhoto receives the user's photograph, read as BMP, PNG, or JPEG, scaled to fit 300×300, and stored as JPEG. Data that cannot be decoded gives no value and no log line.
  • Groups. A field mapped to memberOf receives the name (cn) of each group, one per line. memberOf (raw) receives the same attribute unresolved. Whether these values become group membership is up to the service action.
  • Empty values. An attribute that is empty after trimming is passed as no value, not as empty text.

What the job hands to workflow

Three job options reach the service actions as job values on every action run:

Job option (Settings App label) Value in conditions
Create Self Service Portal accounts %[SYS Job Settings.Create SSP Accounts]%
Create Organizations %[SYS Job Settings.Create Organizations]%
Create Locations %[SYS Job Settings.Create Locations]%

The job itself does not act on these options; the service actions can read them in their conditions. For macros, see Macros Reference.

The run itself works as the Active Directory Integration service person.

The Default Workflow

This section describes what a new Alloy Navigator 2026.1 database created with the Default Workflow contains; see Default Workflow Configuration. A database upgraded from an earlier version need not have this content, and an administrator may have changed it.

The supplied configuration includes the service actions New Person (Active Directory Sync), the create action, and Update Person (Active Directory Sync), the update action, both on the Person class. They are ordinary configuration: you can edit them or replace them with your own. In the Settings App, you choose the actions in the job's Create Persons: and Update Persons: fields, which are empty on a new job. In the Admin Center, you choose them in the job's Create Persons and Update Persons fields.

On the Field Mapping tab of both supplied actions, the City value is mapped to the directory attribute l (a lowercase L).

Six workflow parameters, in the parameter category Integrations\Active Directory Integration, steer this content. In the supplied configuration they are set as follows:

Parameter Set to, in the supplied configuration Choices
Organizational Structure Department Name Company Name\Department Name, Company Name, Department Name
Active Directory SSP Authentication Windows Authentication Single Sign-On, Standard Authentication, Windows Authentication
Active Directory SSP Default Password Empty Free text; empty means that the password is generated automatically
Active Directory Disabling Behavior Permanently mark Person record Inactive That, or Temporarily mark Person record Disabled
Automatically Set SSP Manager Access for Managers On On or off
Debug Logging Status Debug Logging Off On or off

In the supplied configuration, Update Person (Active Directory Sync) branches on the Disabled value, on the Active Directory Disabling Behavior and Debug Logging Status parameters, on the person's status, and on %[SYS Job Settings.Create SSP Accounts]%. New Person (Active Directory Sync) branches on %[SYS Job Settings.Create SSP Accounts]% and on the Debug Logging Status parameter. A separate function of the supplied configuration, Create Self Service Portal Account (Active Directory), branches on the three values of Active Directory SSP Authentication and on Active Directory SSP Default Password.

Logging

Each run writes a log with one block per directory user: the data considered, the matching result with the hits per field, and a Result line. The log ends with statistics: users seen, created, updated, and unchanged. The detailed breakdown of a failed match is added only in detailed (debug) mode.

When a run fails with an unexpected error, the error is also recorded in the system log, under the category Failure to synchronize with Active Directory, with the job's ID.

The logs do not count the accounts, locations, or organizations that the service actions create. For the logs in general, see Logs.