Solved! Go to Solution.
Hello and thank you for posting here!
For initial deployments of DLP, a reboot is not required for the Windows Client Configuration policy to take effect. There are some settings within the Windows Client Configuration policy that do require a DLP Agent restart (which a reboot is the easiest way to accomplish that). Those settings are indicated in the policy with an asterisk (*).
If you're upgrading the DLP Agent from an older version, a reboot is often necessary since drivers are being updated. However, that is not directly related to settings that are in the Windows Client Configuration policy.
Hello and thank you for posting here!
For initial deployments of DLP, a reboot is not required for the Windows Client Configuration policy to take effect. There are some settings within the Windows Client Configuration policy that do require a DLP Agent restart (which a reboot is the easiest way to accomplish that). Those settings are indicated in the policy with an asterisk (*).
If you're upgrading the DLP Agent from an older version, a reboot is often necessary since drivers are being updated. However, that is not directly related to settings that are in the Windows Client Configuration policy.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: