Our Test Policy contains our test devices (a server, two workstations, and a laptop) that are not part of our production set. Policies B and C are groups of workstations and laptops. In the adjacent visual example, all of our devices are grouped into a few different policies: Production (A, B, C) and Test.
Therefore, at any time, you can have all of your production policies as well as one (or more) testpolicies: By creating a new policy (or policies) to affect only test devices, you have quickly isolated these machines as your test group.īy creating a test policy, changes applied to this policy affect only those devices - keeping your test activity apart from your day-to-day work (production) machines. We recommend you leverage this policy-based approach to segment production devices from test devices. You can create policies for any group of devices that you like, and the devices belonging to that policy are all affected by that policy's settings.įor more information, see Learn about policies. Generally, customers have separate policies for servers, workstations or laptops, and even for sub-groups, like "Accounting laptops" or "Admin support machines". Reminder: A policy is simply a collection of settings that are applied to a group - one or more devices. Using a test policy to contain your test devices also enables you to easily test-deploy brand new VIPRE agent releases to this group. Use policies to separate your production devices from your test devices to try out potentially disruptive changes in a non-production environment. Split test and production devices by policy
0 kommentar(er)
