SAPIEN Software and Virtual Machines

Lately, we have been receiving more requests for offline activation. This increase is due to corporate environments transitioning to virtualized environments where all data is destroyed as the user logs off. This data destruction leads to the deletion of stored licensing data, among other items, and therefore our software will require activation the next time a VM is spooled up.

Adding an offline file to the VM’s image may address the licensing part, but it will miss vital other data. So a simple offline activation request will not solve your situation, and it is also not in accordance with our license agreement. If your machine—virtual or physical—is connected to the internet, you need to activate it online.

If you have a subscription license rather than a perpetual license, no offline activation mechanism is available.

The issue generally arises when our (or anyone else’s) installer trace or installer log is used to determine what items should persist between VM instances. That is not enough.

On first launch, most SAPIEN Software will perform additional steps—such as software activation—that are not traced by simply observing the installer.

The recommendation is to install the desired SAPIEN software and run it at least once before taking a snapshot. This includes activation. In the case of CIM Explorer, PowerShell Studio, PowerShell Module Manager, or PrimalScript, it is necessary to let the software perform a scan of your environment and/or cache required information before creating a snapshot.

Below is a list of top-level folders and registry entries that must be preserved between virtual machine sessions to ensure proper operation:

Folders:

C:\Program Files\Common Files\SAPIEN Common
C:\Program Files\SAPIEN Technologies, Inc
C:\Program Files (x86)\Common Files\SAPIEN Common

C:\ProgramData\SAPIEN
C:\ProgramData\VersionRecallService

C:\Users\<User Name>\AppData\Roaming\SAPIEN
C:\Users\<User Name>\AppData\Roaming\SAPIEN Technologies, Inc

User data has to be preserved for all users accessing a system.

Registry:
Per user:
HKEY_CURRENT_USER\SOFTWARE\SAPIEN Technologies, Inc.

Per machine:
HKEY_LOCAL_MACHINE\SOFTWARE\SAPIEN Technologies, Inc.

The installers may also add items to HKEY_CLASSES_ROOT to associate icons or file types with SAPIEN Software and to register COM objects. Therefore, it is advisable not to remove any item from HKEY_CLASSES_ROOT between VM sessions.

The list provided above may be incomplete and may also change over time. If you have any questions regarding these items, please use your Premium Support option, or post in the respective product support forum.

Please do not email the SAPIEN Sales Department; you will only be redirected to the product forum.