Special considerations when adding keys of various types

When adding keys, you should take the following into consideration:

• If you are using a licensing scheme based on the number of protected virtual machines, the type of key that you use to activate the application must match the guest operating system type of the virtual machines:
  • Add a server key to an SVM in order to protect virtual machines with server operating systems.
  • Add a desktop key to an SVM in order to protect virtual machines with desktop operating systems.
  • Add two keys, a server key and a desktop key, to an SVM in order to protect virtual machines with both server and desktop operating systems.

  If you are using a licensing scheme based on the number of processor cores or based on the number of processors, you need one key (with a limitation on the number of processor cores or with a limitation on the number of processors), irrespective of the type of operating system installed on the virtual machines.

  To protect virtual machines with Linux guest operating systems, you may use only server keys, keys with a limitation on the number of processor cores, and keys with a limitation on the number of processors.

• Simultaneous use of keys corresponding to different licensing schemes on SVMs is not supported. After activation of the application, if you add a key that corresponds to a different licensing scheme, the previously added key is removed from the SVM. For example, if you add a key with a limitation on the number of processor cores, and a desktop and/or server key was previously added to the SVM, the active and (if available) additional desktop and/or server keys are removed when the task is executed. They are replaced by the key with a limitation on the number of processor cores as the active key.

  On an SVM, only keys corresponding to the same licensing scheme can be simultaneously used, for example, a desktop and a server key (a licensing scheme based on the number of protected virtual machines).

  A key that was removed from one SVM can be added to another SVM if the term of the license bound to the key has not expired.

• Simultaneous use of commercial keys and subscription keys on an SVM is not supported.

  For example, if you add a commercial key on an SVM with a previously added subscription key, the subscription key is removed from the SVM. The commercial key is added in its place.

• Simultaneous use of keys matching different types of licenses (standard license or enterprise license) on an SVM is not supported.

  For example, if you are adding a key that corresponds to an enterprise license but the application was previously used with a standard license, all active and (if available) additional keys that correspond to the standard license are removed from the SVM. A key that corresponds to an enterprise license is added instead of them.