0% found this document useful (0 votes)
175 views

SmartPlant License Manager and Virtual Configurations

The document discusses using SmartPlant License Manager in virtual environments. It covers having the license machine virtualized and using the license client virtually. The license machine is supported on Windows Server 2012 R2 virtualized. Limitations include key invalidation from operations like cloning. The client can run virtually on VirtualBox or VMware with certain network adapter settings.

Uploaded by

francisblesson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
175 views

SmartPlant License Manager and Virtual Configurations

The document discusses using SmartPlant License Manager in virtual environments. It covers having the license machine virtualized and using the license client virtually. The license machine is supported on Windows Server 2012 R2 virtualized. Limitations include key invalidation from operations like cloning. The client can run virtually on VirtualBox or VMware with certain network adapter settings.

Uploaded by

francisblesson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SmartPlant License Manager and Virtual

Configurations
The following sections describe the different settings for using SmartPlant License Manager in virtual
environments.

SmartPlant License Manager License Machine in a Virtual


Environment
If you are using SmartPlant License Manager 12.00.82.00 or higher, the SmartPlant License Manager
license machine is supported in a virtual environment.
The only guest operating system currently supported for the SmartPlant License Manager license
machine in a virtual environment is Windows Server 2012 R2.

Hyper-V®
You must install one of the following operating systems on the host:
 Hyper-V® Server 2012 R2
 Windows Server 2012 R2 with the Hyper-V role

XenServer®
You must install the following operating system on the host:
 XenServer® version 6.2 or later
A compatible version of XenServer Tools must be installed on the guest operating system.

VMware®
You must install the following operating system on the host:
 vSphere®/ESXi™ version 6.0 or later
A compatible version of VMware Tools must be installed on the guest operating system.

Limitation for License Machine in all Virtual Machine Environments


Copy, checkpoint, move, clone, and similar operations may invalidate your license key.
Once a key is invalidated, you must remove the license key by running pdlice -c (using a
Command Prompt window run as Administrator), generate a new machine ID, and then request a new
key for the new machine ID.
SmartPlant License Manager Client in a Virtual
Environment
VirtualBox or VMware Player
To use the SmartPlant License Manager client with VirtualBox or VMware Player, create a virtual
machine, install the operating system, and install SmartPlant License Manager as the license client.
When creating the virtual machine, create a host-only or bridged adapter, and bind that adapter to your
local machine network adapter with network connectivity.

 In the virtual machine settings for VirtualBox, the Promiscuous Mode drop-down must be set
to Allow All.
 The NAT (Network Address Translation) adapter setting is not supported.
Host-Only Adapter
The SmartPlant License Manager license machine for this configuration must reside on the same physical
machine as the virtual machine.
To create a SmartPlant License Manager license machine for this client, refer to Appendix C: Installing
SmartPlant License Manager on a Stand-alone System in the SmartPlant License Manager Installation
and User’s Guide.
Bridged Adapter
The SmartPlant License Manager license machine for this configuration can reside on the same physical
machine as the virtual machine or on the network that the physical machine is connected to.

You might also like