1.0

Table Of Contents
CHAPTER 7 Deploying and Maintaining Packages
147
Enter the entire command on a single line.
In the commands above, -n is an optional flag that instructs the host to verify the
validity of the new descriptor but not save it.
Return Values
The exit value of the command is 0 if the descriptor is valid, or 1 if it is invalid.
Sample Usage
If you want to check whether descriptor 0x7B4C2902 is valid, use the optional -n flag,
as shown in the following command:
/usr/sbin/vmware-guestd --cmd "nq-set -n 0x7B4C2902"
An exit value of 0 means that the descriptor is valid
To set the descriptor to the value 0xFA542D3F, use the following command:
/usr/sbin/vmware-guestd --cmd "nq-set 0xFA542D3F"
An exit value of 0 means that the descriptor is valid and has been saved.
Custom network quarantine applications can save arbitrary strings by using the
nq-set command. For example, assume that you want to save the following string:
"os=winxp-sp2,ie=6.0,virusdefs=4.0,office=2003-sp1"
You may do so using the following command:
/usr/sbin/vmware-guestd --cmd "nq-set os=winxp-
sp2,ie=6.0,virusdefs=4.0,office=2003-sp1"
Enter the entire command on a single line.
An exit value of 0 means that the descriptor is valid and has been saved.
Using nq-set with Version-Based Network Quarantine
Each version update defined in the Network Quarantine Wizard has a network
quarantine descriptor associated with it. The Network Quarantine Wizard also displays
the command you need to run in the guest operating system to update the
descriptor. To view that command, go to the Manage Versions panel in the Network
Quarantine Wizard, choose the version you want to check, then click Properties. The
command is shown in the field at the bottom of the screen.
You must update the network quarantine descriptor after you apply an update to the
guest. Updates must be applied in the order that they were defined.
Note: Your patching mechanism should check whether the nq-set command will
succeed before it applies any updates to prevent the user from applying patches out
of order and causing the guest patch level to be out of sync with the network