3. Installing a PxM Virtual Appliance within Hyper-V

This chapter provides instructions on how to install a new PxM Virtual Appliance within a Hyper-V virtual desktop infrastructure.

3.1. Software download

The software is supplied as a virtual hard disk (VHD), ready for deployment in your Hyper-V infrastructure.

To download the latest PxM software:

  1. Go to the PxM Virtual Appliance section of the Osirium Software Releases page.

  2. Under Deploying new appliances, download PxM Platform Hyper-V VHD.


    A SHA256 checksum is available to verify the download integrity.

3.2. Deploying the virtual appliance

  1. Within your existing Hyper-V infrastructure, create a new virtual machine with a custom configuration.

  2. Complete the wizard based on your preferences, but ensure that you allocate the recommended memory to the virtual appliance in the Assign Memory page. See Preparing to install the PxM Platform.

    Assign Memory Screen

  3. Verify the details shown on the Completing the New Virtual Machine Wizard page and click Finish.

    Completing Wizard Screen

  4. In the Virtual Machines list, right-click the new virtual appliance and click Settings….

    Hyper-V Virtual Machines list

  5. In Processor, assign 2 virtual processors to the virtual appliance.

    Add 2 processors

  6. Wait while the virtual appliance is created.

3.3. PxM Virtual Appliance Setup and Configuration

  1. Start and connect to the PxM Virtual Appliance. Wait while the system configures.

    Initial configuration

  2. Press ENTER to begin the setup process.

    Press ENTER

  3. Read and accept the EULA to continue.


  4. Within the Osirium: Configure Networking screen, configure the following virtual appliance settings. Press TAB to navigate between the fields.

    • IP Address: Enter the IP Address which will be used to connect to the virtual appliance.
    • Netmask: Enter the network mask.
    • Gateway: Enter the network default gateway IP address.
    • Primary DNS: Enter the network primary DNS IP address.
    • (Secondary DNS): Enter the secondary DNS IP address if necessary, else leave blank.

    Configure networking

  5. Wait while the system is configured. When prompted, hit ENTER to Continue without restoring a backup.


  6. Within the Enter a hostname window, enter a name to identify the new PxM Virtual Appliance.

    Enter a hostname

  7. TAB down to the OK button and hit ENTER.

  8. Set a password for the new primary superadmin account. The username (superadmin) and the password will be used later to login to the PxM Client.

  9. TAB down to the OK button and hit ENTER.

  10. Confirm the new primary superadmin account password.

  11. TAB down to the OK button and hit ENTER.

  12. Your Master Encryption Key will be shown.

    Master Encryption Key

    Type Description
    Master encryption key

    This key is VERY IMPORTANT make a note of it and securely store it externally for future reference as it is not stored within the PxM Platform.

    It will be required during a backup/restore procedure to recreate the hash file and decrypt the PxM Platform database stored within the backup file.

    See PxM Virtual Appliance backup and restore guide.


    During the installation process the master encryption key is combined with the Salt to generate a hash which is stored in a file.

    The Salt is stored on the PxM Virtual Appliance and will be included in the backup file.


    Is generated during the installation process and stored on the PxM Virtual Appliance. The hash file will not be included in the backup file.

    During a backup/restore procedure the master encryption key will be used with the salt to recreate the hash and decrypt the backup database file to reinstate the PxM Virtual Appliance.

  13. Enter the Master Encryption Key including the dashes to verify.

  14. TAB down to the OK button and hit ENTER.

  15. Once the setup is complete the following message will be displayed in the Osirium Console window. Make a note of the https virtual appliance address.

    Setup complete

  16. Close the virtual machine connection.