Patch for Windows® Servers, powered by Shavlik

> Asset Inventory > Asset Scan Requirements

Asset Management Scan Requirements

Before attempting an asset scan, please confirm that you meet the following requirements:

The Windows Management Instrumentation (WMI) service must be enabled and accessible on the target machines.

TCP port 135 must be configured on your organization's firewall to allow the WMI protocol.

Credentials must be provided for the target machines. You cannot perform scans using your current logon credentials. See Supplying Credentials for details.

For target machines using Windows operating systems that employ the use of User Account Control (this includes Windows Vista or later and Windows Server 2008 or later), you must either:

Join the machines to a domain and then perform the scan using domain administrator credentials, or

If you are not using the built-in Administrator account on the target machines (and using that account is NOT recommended), you must disable User Account Control (UAC) remote restrictions on the machines. To do this:

1.Click Start, click Run, type regedit, and then press Enter.

2.Locate and then click the following registry subkey:


3.If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.

b. Type LocalAccountTokenFilterPolicy and then press Enter.

4.Right-click LocalAccountTokenFilterPolicy and then click OK.

5.In the Value data box, type 1, and then click OK.

6.Exit Registry Editor.

For more details on disabling UAC remote restrictions, see

Windows Firewall Requirements for Hardware Asset Scans

Ivanti Patch for Windows® Servers scans for hardware assets using WMI in semisynchronous mode. This means the firewall policy only requires DCOM connections from the console machine to the target machines. Asynchronous mode, which would require reverse connections back to the console, are not used.

To scan hardware assets of a machine with Windows Firewall running, you must set that machine’s firewall to allow remote administration. You can configure the firewall via group policy or local command. The local command is:

netsh firewall set service RemoteAdmin enable

If you are unfamiliar with Windows Firewall administration, the following links may help:

Was this article useful?    

The topic was:



Not what I expected