Managing Multiple Machine Properties

The Machine Properties dialog enables you to define several common properties for two or more machines.


Machines to update

Contains a list of the machines that will be affected by the properties you define.

Patch drive path

Enables you to specify the drive and the path to use on the target machines when patches are downloaded during a patch deployment. Do this only if you do not want to use the default location (C:\Windows\ProPatches). For example, if the C: drive on your target machines is low on space, you might specify that the patches are instead written to the D: drive. The "ProPatches" name is automatically appended to whatever path you specify. For example, if you specify "D:\ABC," the final destination for the patches will be "D:\ABC\ProPatches."


Enables you to specify a custom criticality level for the listed machines. This value is something you assign and use for your own purposes. For example, if you have a set of machines that are of particular importance to your company, you can assign a criticality level to the machines and then use the filtering and sorting capabilities in Machine View to quickly locate the machines and determine their status.

If you assign a custom criticality level, the flag displayed in the Machine Criticality column of Machine View will change to the appropriate color.

(Red) Critical

(Orange) High

(Yellow) Medium

(Gray) Low

(White) Ignore

Custom 1, Custom 2, and Custom 3

These three fields enable you to write custom notes about properties that are unique to the listed machines. For example, you might use Custom 1 to specify the machine type (laptop, desktop, server, etc.), Custom 2 to specify the machine location (St. Paul, Dallas, Seattle, etc.), and Custom 3 to specify the department that owns the machine (HR, Accounting, IT, etc.). You can use the fields to filter or sort machines within Machine View or Scan View.


Specifies the credential used when authenticating Shavlik Protect to the machines. The credential you supply here will override credentials specified in other areas of the program. If you select None you effectively remove the credential currently assigned to the machines.

There may be several reasons for providing different credentials to machines after a scan has been performed. If you have multiple administrators in your organization and each is responsible for a different domain, they will need to set their own credentials before performing an action. Or, your organization's policy may be to separate scan (assessment) duties from deployment duties, in which case different credentials are probably required.

RDP Port

Defines the Remote Desktop Protocol (RDP) port to use when making a remote desktop connection with the machines.

ITScripts Port

Defines the port used to allow the WinRM protocol for Windows PowerShell commands.