- 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 Docusnap365 user with the role Administrator.
1. Install the gateway
We download the setup under Scan › Gateways › Download Gateway and run it on the Windows server. The setup installs the service and the configuration application. In the configuration application we sign in with our Docusnap365 user and register the gateway for our tenant. After registration the gateway appears under Scan › Gateways with the state Online.A gateway belongs to exactly one tenant. A second tenant needs a second gateway.
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.
An entry with an Expiry Date appears under Action Required on the dashboard
before it expires. We set the expiry date to the date the account’s password
expires.
3. Scan Active Directory
We create the first job: Scan › Scan Job, module Active Directory.
The job appears under Scan › Active. After the run, Last Result shows
Successful. Assets now lists the domain, users, groups and computer accounts.
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 start the job with Run now.
Windows (AD) requires a completed Active Directory scan. Without it, the domain
cannot be selected in the step Targets & Authentication.
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 entries. For systems a scan module can capture — switches via SNMPv1/v2, printers via IP Hosts — we create another job instead.A typed system is an asset. It disappears from Unknown Systems and appears under
Assets.
Result
- One gateway Online
- Two credential entries in the vault
- Two jobs: AD Headquarters (once) and Windows Servers (daily)
- The inventory under Assets, unknown systems typed
What’s next
- Capture further sources: Scan Modules – Overview
- Give assets owners and a lifecycle: Recording ITAM Data
- Monitor jobs and follow up on failures: Managing Jobs