Captured data
The scan creates assets of these two types:
How the detail pages of the types are structured is described in
Directory and Network Services.
Setting up the job
The wizard follows the standard path Basics › Targets › Schedule › Summary—see Creating a Scan Job. The Targets step is what sets this module apart. Each row carries the columns Server Name and Credentials. Server Name takes one namespace server per row, as an address or hostname; the column does not accept an address range. Search DFS Servers fills in the servers from Active Directory instead: the dialog asks for the Domain and credentials and adds the DFS servers it finds as rows.Search DFS Servers finds domain-based DFS servers only if the Namespace
Server role is installed on them. Enter standalone namespace servers as rows
by hand.
Prerequisites
The scan connects to the DFS servers over WMI and to a domain controller over LDAP.Ports and protocols
Permissions
- The account is a domain user, entered as
DOMAIN\useroruser@domain.local. - It is a member of the local Administrators group on the namespace servers.
- It is a member of the local Administrators group on the servers that provide resources for the DFS.
Network requirements
- The firewall allows the ports above.
- PowerShell can run on the DFS servers.
- User Account Control (UAC) is set up for the account’s remote access.
Discovery-DFS.exe scan script—see
Scanning by Script. For DFS this is the recommended
way.