Items in brackets are optional, and the | symbol means "or":
| General | Repair | Reboot |
|---|---|---|
| /AgentBehavior=AgentBehaviorID | /Repair Group=GroupID | Vulnerability=VulnerabilityID | Vulnerability=All | /Reboot |
| /ShowUI | /Fix | /RebootIfNeeded |
| /AllowUserCancelScan | /RemovePatch=Unique patch name | /RebootAction= [always | never] |
| /AutoCloseTimeout=Seconds | /RepairPrompt=Message | /RebootMessage=Message |
| /Scan=X, where X is the type | /AllowUserCancelRepair | /AllowUserCancelReboot |
| /Group=GroupID | /AutoRepairTimeout=Seconds to wait | -1 (-1 mean to use "Default") | /AutoRebootTimeout=Seconds to wait | -1 |
| /Autofix=True or False | /DefaultRepairTimeoutAction=start | close | /DefaultRebootTimeoutAction=reboot | close | snooze |
| /StageOnly | /SnoozeCount=Number of snoozes | |
| /Local | /SnoozeCount=Number of snoozes | |
| /PeerDownload | /SnoozeInterval=Seconds to snooze | |
| /NoPeer | ||
| /SadBandwidth=(% of bandwidth to use) | ||
| /IgnorePendingFileRename |
| MSI | VB Testing | Disable |
|---|---|---|
| /OriginalMSILocation=Path | /scriptrepair=filename | /NoElevate |
| /Username=Username | /scriptdetect=filename | /NoSleep |
| /Password=Password | /customVarfile=filename | /NoSync |
| /NoUpdate | ||
| /NoXML | ||
| /NoRepair |
| Data Files | Antivirus | Endpoint Security |
|---|---|---|
| /Dump | /removeoldav | /installhips |
| /Data | /removeav | /removehips |
| /O=Filename (including full path) | /installav | /changesettings (download new settings made) |
| /Log=Filename (including full path) | /z=filename | |
| /Coreserver=server name | /fixnow | |
| /Reset - Deletes client side settings and files | /changesettings | |
| /Clear or /ClearScanStatus - Clears scan results for client at core | av |
Running "vulscan e", "vulscan l", "vulscan c", or "vulscan av" does the following:
| Vulscan log files | Vulscan log directory | LDClient Directory | Antivirus |
|---|---|---|---|
| e - Opens the folder containing vulscan log files | l - Opens the current vulscan log | - opens the LDClient Directory | AV - opens the LANDeskAV folder |
Vulnerability definition types for use with the /scan= switch:
| Number | Type |
|---|---|
| 0 | Vulnerabilities |
| 1 | Spyware |
| 2 | Security Threats |
| 3 | LANDesk Updates |
| 4 | Custom Definitions |
| 5 | Blocked Apps |
| 7 | Drivers |
| 8 | Antivirus |
Vulscan switches used for content replication
/replicate– triggers vulscan to do a content replication.
/changesettings with a /replicationbehavior=default tells vulscan which behavior to use. Default means compute the behavior guid based on the computer idn. For example, if my computer idn is 1234, then I will try to download a behavior called “ReplicationBehavior_Replicator_1234.xml”. Vulscan will now consider itself a “replicator” and will try to update its copy of a replicationBehavior any time it runs, creating any local scheduler jobs as necessary.
/changesettings /replicationbehavior=-2 will disable vulscan as a replicator, removing any local scheduler tasks regarding replication and causing vulscan to no longer attempt to get the latest replication behavior file.
/settingsIndex=NNN– you’ll see this commandline used by the local scheduler when it launches vulscan. This tells vulscan which group of settings to use to control its behavior as specified in the console’s UI. For each scheduled replication event that you specify, there will be a new “settingsIndex”.
/duration=NNN– The maximum duration that vulscan should do replication, in minutes. This will appear in the replication behavior file and not typically on the command line, but in the file you’ll see something like “Duration_0”, or “Duration_1”, etc. The value after the underscore is the settings index number. When vulscan applies settings found in the behavior file and it sees that its settingsIndex value has been set, then it looks for any variables in the behavior file that end with an underscore and that number (such as “Duration_0”). It strips off the underscore and number and sets the value internally. Therefore, anything you see in the behavior file that ends in the underscore can be passed on the commandline (and therefore take precedence over the behavior file settings).
Many of the _NNN settings that are in the behavior file are regarding the local scheduler task that should be created. So vulscan only interprets those values when creating the local scheduled task that will later launch itself to do replication.