--- title: "Directory Jobs" slug: "directory-jobs" status: "update" updated: 2026-11-13T08:07:57Z published: 2026-11-13T08:07:57Z canonical: "help.symphonysummitai.com/directory-jobs" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Directory Jobs Directory discovery performs agentless discovery of Microsoft Active Directory through LDAP or LDAPS. It identifies directory objects and structures, including forests, domains, domain controllers, sites, organizational units, computers, users, groups, and trusts. Use this job type to discover the directory environment and its computer objects. Follow-up discovery through WMI, SSH, or SNMP is required to enrich computer records with device-level inventory information. **Example:** An administrator discovers computer objects in Active Directory, then uses Network discovery to collect hardware, operating system, and software information from the corresponding devices. To create a new job for Directory devices, perform the following steps: 1. Click **Workspace > ITAM > Asset > Discovery > Discovery Jobs**. The Discovery Jobs list page is displayed. 2. Click **New Job**. 3. On New Job, select the job type that matches your discovery source. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/discovery_jobs-image-1d9biwvy.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=Zzi9B2OuDlU4FkWuNhJ5PIdKwjwwLF8izCSX6G8pqS8%3D) Figure: New Job | **Job type** | **Purpose shown on the selection screen** | | --- | --- | | Network | Discover Windows through WMI, Linux through SSH, and network devices through SNMP. | | Cloud | Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud. | | Container | Discover Docker containers and Kubernetes resources. | | Hypervisor | Discover guest VMs through virtualization platforms. | | Database | Connect to database engines to discover instances and inventory. | | Directory | Discover Active Directory information without an agent. | | Storage / SAN | Discover storage systems through supported platform interfaces. | 4. Select Directory on the new job. 5. On **Identity**, select the tenant and enter a descriptive job name. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-VXI0SWA4.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=hS9zSZJWV%2BPZVs1InAAMTJHQB%2FvBFGOA%2FWqb%2B%2BUnN8g%3D) Figure: Identity | **Field name** | **Description** | | --- | --- | | Tenant * | Tenant context associated with the job. The demonstration displays Information Technology. | | Job Name * | Name used to identify the job in the jobs list and run details. Example: LDAP-Directory. | | Status | Activation state selected for the job. The demonstration shows Active. | | Description (optional) | Purpose, scope notes, ownership, or other context for the team. | | Next | Continues to the next wizard stage. | | Cancel | Leaves the wizard. Confirm any save or discard behavior presented by the application. | 6. Click **Next** to open Type and Credentials. 7. The **Type & Credentials** step lets you select Docker or Kubernetes container services and associate credentials with the respective container services you want to discover. 1. For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available. 2. Use the up and down controls to arrange the displayed execution order. 3. Review the methods and selected credentials, then click **Next**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-QVU6VZKO.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=eRSWINc9m%2B8NUBvLh4tN%2F8T298gGMsJZLprXYR9Aq8I%3D) Figure: Directory Credentials | Parameter or control | Description | | --- | --- | | **LDAP** | Enables directory discovery through LDAP / Active Directory. The discovery scope comes from the server and Base DN configured in the selected credential; separate IP targets are not required. | | **Selected LDAP credential** | Displays the credential assigned to directory discovery. Click **×** beside it to remove the assignment. | | **PRIMARY** | Identifies the LDAP credential used first. | | **Add LDAP credential** | Select an existing LDAP credential to add to the job. | | **Quick-create LDAP credential** | Creates an LDAP credential and adds it to the current job. | | **Manage credentials** | Opens credential management to review or maintain stored credentials. | | **Host Protocols & Credentials (Required)** | Configures the methods and credentials used to enrich discovered computers after directory discovery completes. Select at least one protocol and attach its credentials. | | **WMI** | Select to collect additional inventory information from Windows computers using WMI credentials. | | **SSH** | Select to collect additional inventory information from hosts that support SSH using SSH credentials. | | **SNMP** | Select to collect additional inventory information from hosts that support SNMP using SNMP credentials. | 8. Create LDAP Credential 1. Enter the credential name, Bind DN, Bind password, and Base DN. 2. Click **Create & Add**. The **Quick create LDAP credential** dialog lets you add credentials for LDAP / Active Directory discovery. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-PUTTLTZX.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=IYdZ4NELHKCJ6xR3%2BOsDzfUbGxk2pG7dZ6sLLUC8zJk%3D) Figure: Create LDAP credential | Parameter | Description | | --- | --- | | **Credential Name*** | Enter a descriptive name to identify the LDAP credential. | | **Bind DN*** | Enter the account identity used to authenticate to the directory. Supported formats shown include `DOMAIN\user`, `user@domain`, or a distinguished name such as `CN=DiscoveryUser,OU=ServiceAccounts,DC=corp,DC=local`. | | **Bind Password*** | Enter the password for the account specified in **Bind DN**. | | **Base DN*** | Enter the distinguished name that defines the starting point for directory discovery. For example, `DC=corp,DC=local` specifies the domain, while `OU=Servers,DC=corp,DC=local` specifies an organizational unit. | | **Create & Add** | Saves the credential and adds it to the current discovery job. | | **Cancel** | Closes the dialog without creating the credential. | 9. Credential Selection Guidance 1. Use an LDAP account with read access to the directory objects you want to discover. Verify the **Bind DN**, **Bind Password**, and **Base DN** for the intended scope. Add WMI, SSH, or SNMP credentials to collect additional inventory from discovered computers. 10. The **Settings** screen controls the collection depth and execution limits for enriching computers discovered through LDAP / Active Directory. Collection depth determines how much information WMI collects from each host. Click **Next** to configure the discovery schedule. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-M5UM5HIP.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=lsoOprW2O%2BWBr3I7ohVPl4vSAJZ6ky7cjI08PfpQ8PY%3D) Figure: Settings | Collection Depth | Field Name | Description | | --- | --- | | **Fast** | Collects basic identity, hardware, and operating system information, including hostname, CPU, RAM, disks, and network interfaces. Excludes software inventory. | | **Normal** | Collects hardware and software information, including hotfixes, services, users, and Hyper-V guests. | | **Deep** | Collects everything in Normal mode plus running processes, scheduled tasks, and system restore configuration. Includes CVE correlation when enabled for the job. Suitable for smaller scopes or detailed audits; takes longer per host. | | **Timeout per host (s)** | Sets the time allowed for collection from each host. The displayed value is **180 seconds**. Enter **0** for no per-host limit during deep WMI collection. | | **Job timeout (hours)** | Sets the overall execution limit for the discovery workflow. The screen specifies a minimum of **24 hours**. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-OP6EOV35.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=CXbdZGd8Cur8O4D5ciye5LtSZ6hgd%2B8TjA8DjqU8wgo%3D) Figure: Performance and Knocking configuration | Parameter | Description | | --- | --- | | **Timeout per host (s)** | Sets the time allowed to collect information from each host. The displayed value is **180 seconds**. Enter **0** for no per-host limit during deep WMI collection. | | **Job timeout (hours)** | Sets the overall execution limit for the discovery workflow. The screen specifies a minimum of **24 hours**. | | **Pre-flight Ping** | Checks host reachability before attempting WMI, SSH, or SNMP collection. Hosts that do not respond to the selected check are skipped. | | **Ping Only** | Checks host reachability without collecting inventory through WMI, SSH, or SNMP. | | **Ping Protocol** | Selects the reachability check used before discovery. **ICMP** is shown as the default; the helper text also identifies TCP connect and UDP probe methods. | | **Knock concurrency** | Sets the number of parallel reachability checks. Enter **0** for **Auto (500)**. The maximum is **2,000**. | | **Rate limit (req/s)** | Limits SNMP/WMI requests per second to manage load on target devices. Enter **0** for unlimited requests. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-MBZDTL9N.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=2HJp25w3ik1bLYv65jq21Tz7doMQ%2BUN2sKLc1IzZQ3E%3D) Figure: Options configuration | Field Name | Description | | --- | --- | | **Rate limit (req/s)** | Limits SNMP/WMI requests per second to manage load on target devices. Enter **0** for unlimited requests. | | **Pre-scan Port Detection** | Checks TCP port **135** for WMI, TCP port **22** for SSH, and UDP port **161** for SNMP before attempting collection. Skips a protocol when its port is detected as closed to avoid timeout waits. | | **Coverage Score** | Calculates a per-device score showing which parameters were collected and why others were not. Enable to assess discovery completeness. | | **CVE Correlation** | Matches discovered software against the National Vulnerability Database (NVD) to identify associated Common Vulnerabilities and Exposures (CVEs). Requires an **NVD API key**. | | **Host Enrichment** | Indicates that computers are enriched using **WMI** configured in the **Type** step after Active Directory discovery completes. The target scope and batch size apply to this enrichment. | Host enrichment runs after Active Directory discovery completes, using the WMI configuration from the **Type** step. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-GM0KMJF3.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=AL9bxea1GE368IEr0WwRMJQvPYbUjj37la5k2m19dnQ%3D) Figure: Target Scope | Field Name | Description | | --- | --- | | **Target Scope** | Selects which computers discovered through Active Directory receive additional inventory collection using WMI. The displayed selection is **All AD Computers**. | | **Batch size** | Sets the number of computers included in each host enrichment batch. The displayed value is **500**. | | **Capture Engine Logs** | Stores detailed discovery engine logs for each run to support troubleshooting. Enabling this option increases storage use. | | **Capture Per-Host Results** | Stores detailed results for each host, allowing individual results to be investigated by IP address. Disable to reduce storage use. | 11. Click **Next**. 12. Execution and Scheduling: The **Schedule** step lets you define when the discovery job starts, how often it repeats, and when the recurring schedule ends. 1. Select the effective task queue and if you want to schedule it, enable the **Enable Schedule Runs** toggle button. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-Z6C79QP7.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=t%2FrihWDlLhzL1OpYiFNWqMt3%2Byhd3eojpKoFczhRTvA%3D) Figure: Scheduling and Execution | Parameter / Control | Description | | --- | --- | | **Effective task queue** | Displays the selected worker’s task queue used to execute scheduled runs and **Run Now** requests. | | **Enable scheduled runs** | Enable to run the discovery job automatically according to the configured schedule. | | **Repeat Job** | Select to repeat the discovery job at the specified interval. | | **Recurrence Type** | Select how frequently the job repeats. The selection shown is **Daily**. | | **Recurs Every** | Enter the interval between recurring runs. For example, **1** with **Daily** runs the job every day. | | **End Condition** | Select when the recurring schedule ends. Select **No end** to continue recurring runs without an end date. | | **Start Date*** | Specify the date and time when the schedule begins. The value is displayed in your time zone and stored in Coordinated Universal Time (UTC). | | **Previous** | Return to the **Settings** step. | | **Cancel** | Cancel the discovery job configuration. | | **Create Job** | Create the discovery job using the configured scope, credentials, settings, and schedule. | 13. Once you click **Scan and Run Now**, you will get a message mentioning Job started. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-9E4IFJ8X.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A49%3A54Z&se=2026-11-20T22%3A49%3A54Z&sr=b&sp=r&sig=3iTPHyni2Le8EJhjzzFSpHtD4k%2FBJddgG1esyzsH02Y%3D) Figure: Job saved successfully