Skip to main content
We put a new subscription into operation: one gateway, one Active Directory, the Windows servers of the domain. At the end the inventory is in Inventory, and the systems no module could assign are typed. Prerequisites
  • A Windows server or Windows VM in the network with outbound HTTPS. No inbound ports are required.
  • A domain account that can read Active Directory.
  • An account with local administrator rights on the Windows servers.
  • A user with write access in the Scan area.

​
1. Install the gateway

We download the installer under Scan › Gateways › Download Gateway and run it on the Windows server. It installs the service and the window of the Docusnap Enterprise Gateway. In the gateway we sign in with our Docusnap365 user and register it for our subscription. If the subscription has exactly one organization, the gateway registers itself after sign-in. Otherwise we select the Subscription on the Registration tab and click Register. After registration the gateway appears under Scan › Gateways with the state Online. The registration fields are described in Installing and Registering the Gateway.
A gateway belongs to exactly one subscription. A second subscription needs a second gateway on a machine of its own. The subscription of a registered gateway cannot be changed; a change requires deregistering and registering again.

​
2. Create credentials

Under Scan › Credentials we create two entries: Storage mode: Reusable. The entries are stored encrypted in the Vault and are available to every job.
If the gateway service runs under a domain account with sufficient rights, Integrated Login is enough for both jobs.
Credentials that must not leave our own network we create on the gateway instead. They then apply to this gateway only; see Storing Credentials Locally.
An entry with an Expiration Date appears under Action Required on Scan › Dashboard from five days before it expires and after that. We set the expiry date to the date the account’s password expires.

​
3. Scan Active Directory

We create the first job: with the Scan Job button on Scan › Dashboard we open New Scan Job and select Active Directory. While it runs, the job is listed under Scan › Active. Afterward we find it under Scan › Completed with Last Result Succeeded. Inventory now lists the domain, users, groups and computer accounts.
Succeeded (No Data) means the job ran but captured nothing. The cause is usually the target or the account’s permissions. We open the job and read Last Scan Details.

​
4. Scan Windows servers

The second job captures the servers the Active Directory scan found: module Windows (AD). The module reads the computer accounts of the domain and scans the systems behind them. For the first run we select the job under Scan › Active, click Run Now and confirm the prompt.
After the Active Directory scan the domain is available for selection; without it, the domain can be entered by hand.
After the run, Inventory lists the servers with hardware, operating system, software and services.
The results of scheduled runs appear in Inventory with the next data refresh. Its interval depends on the edition. A run started with Run Now appears immediately.

​
5. Type unknown systems

The dashboard shows under Unknown Systems the number of systems a scan found but could not assign to a type—printers, switches, devices without Windows. We open Scan › Unknown Systems, select the systems of one type and assign the type via Edit Systems. For systems a scan module can capture—switches via SNMP v1 and v2, printers via SNMP—we create another job instead. IP-Hosts recognizes printers as such, but only the SNMP scan delivers detailed data.
A typed system is an asset. It disappears from Unknown Systems and appears under Inventory.

​
Result

  • One gateway Online
  • Two credential entries in the vault
  • Two jobs: AD Headquarters (once) and Windows Servers (daily)
  • The inventory under Inventory, unknown systems typed