Force client reboot when required: When encryption is added to a policy, it does not become
active until the endpoint is rebooted. This setting forces the required reboot by displaying a
countdown timer, warning the user that the machine will reboot in the specified number of
seconds. The user has that amount of time to save work before the machine reboots.
Reboots are required when encryption is first activated in a policy, and again when either "Safe
Harbor" or removable storage encryption is activated (if activated separately from encryption
activation). For example, when an encryption policy is applied for the first time, two reboots
are required: one reboot to initialize the drivers and another reboot to put any safe harbors into
encryption. If additional safe harbors are subsequently selected after the policy has been
applied, only one reboot is required to put the safe harbor into policy.
ZSC Update
Patches to repair any minor defects in the Endpoint Security Client are made available with regular
ZENworks Endpoint Security Management updates. Rather than providing a new installer, which
needs to be distributed through MSI to all endpoints, ZENworks Security Client Update allows the
administrator to dedicate a zone on the network that distributes update patches to end users when
they associate to that network environment.
To access this control, click the Global Policy Settings tab, then click ZSC Update in the policy tree
on the left.
Figure 6-14
To facilitate simple and secure distribution of these patches to all Endpoint Security Client users:
1 Check Enable to activate the screen and the rule.
94
ZENworks Endpoint Security Management Administration Guide
ZSC Update
Need help?
Do you have a question about the ZENWORKS ENDPOINT SECURITY MANAGEMENT 3.5 - ADMINISTRATION and is the answer not in the manual?