Policies

On this page, you can assign policies for pre-existing user groups that you can set up in Parallels My Account. Each user group is a sublicense of your main Parallels Desktop Enterprise Edition license with a unique key. Read this chapter to learn more.

Attention: If you want, you may assign a new policy to the users activated with the primary license key. However, for security reasons, we strongly advise against using your primary key directly. Any compromised secondary (sublicense) keys can be deleted and replaced with new ones.

To create user groups and populate them with users, please refer to this page. If you plan on using Single Sign-On for license activation, refer additionally to this page.

To create a new policy, click on the Add button in the top left corner of the page.

Presently, policies only define what users from your organization can do with their Parallels Desktop setups and not their virtual machines. The four available settings are:

Note: As Parallels Desktop Enterprise Edition develops, we will be adding more policies to this menu.

• Limit users to corporate virtual machines only. This policy prevents users from setting up new virtual machines from sources other than your organization’s Golden Images, as well as importing or cloning pre-existing ones. You may want to enact this policy to prevent members of your organization from setting up virtual machines for their own extracurricular activities;

• Limit the number of corporate virtual machines per user to one. This setting prevents users from installing any more virtual machines from the approved sources (i.e., your organization’s Golden Images). ;

• Do not allow removing corporate virtual machines;

• Do not allow upgrading to the next major Parallels Desktop version. This setting will still allow users to update their Parallels Desktop installations to a minor version (e.g., 20.0 to 20.1) but will prevent them from upgrading to a major version (e.g., from 20.x to 21.x) when it becomes available. Enabling this setting will allow you to first ensure that a major new version suits your needs before proceeding with a fleet-wide upgrade.

When adding a new policy, provide the following information:

1. Name. Use a unique descriptive name in case the number of policies increases in the future;

2. Description;

3. Policy applies to. This setting allows you to add and remove the groups (as defined by secondary license keys) that the policy applies to. If you don't divide your Parallels users into groups, or have users assigned to the primary license key, you may assign a policy to the primary license key. To add a group, use the drop-down menu as indicated in the image above. To remove one already added, click on the (X) symbol next to the one already listed. primary license key. SSO user groups;

4. Set the restrictions as described above;

5. Click Save.

The default view of the main Policies screen shows you the list of all the policies under your management, citing their names as provided during the setup process, their descriptions, and the list of groups they apply to. Right-clicking on a policy from the list allows you to edit or delete it.

If a policy is marked as "not applied", it either means that no groups were selected during the creation, or the group(s) it initially applied to was (were) deleted.

Warning: Deleting a policy is non-reversible. Please make sure you are deleting the right one.