Virtualization

The following table lists the virtualization support for installation and operation of Power Operation with Advanced Reporting and Dashboards:

  Microsoft Hyper-V VMWare vSphere
Power Operation Server (including web server host) Yes Yes
Power Operation Client Access (this refers to Windows Desktop clients) Yes Yes
Mobile Notifications (Event Notification Module) Yes Yes
Advanced Reporting and Dashboards (Power Monitoring Expert) Yes Yes

NOTE: Power Monitoring Expert is validated with additional virtualization systems, see the Power Monitoring Expert 2022 – System Guide for additional details.

Virtualization planning notes:

  • Set all resource allocation (CPU, memory, and disk) to fixed; dynamic is not supported.
    • Do not share resources between virtual machines via over-allocation.The total of all individual VM resources should not exceed that which is available from the host.

      • notice

      UNINTENDED DATA LOSS OR LOSS OF SOFTWARE FUNCTION

      Do not exceed device limits.

      Failure to follow these instructions can result in irreversible damage to software and databases.

  • If you are using shared drive storage, use Fiber SAN storage. If you are not using Fiber SAN storage, use a direct attached, dedicated hard drive used by Power Operation only.
  • You must have a fixed-size disk virtual machine.
  • Set host (for example: ESX host) power management to “High Performance”.
  • Adjust Quality of Service (QoS) to allow precedence to Power Operation over less time-critical applications.
  • Create your Power Operation virtual machine on a host without other time-critical applications.

Additional virtual machine configuration guidelines vary by hypervisor.

When running virtual machines, licenses remain trusted during the following scenarios:

  • Changes to the NIC card MAC address of the physical host or virtual machine.
  • Changes to the physical host or virtual machine RAM
  • Changes to physical host hard disk or virtual machine disk
  • Changes to the OS clock (within +/- 2 hours)
  • The physical host or virtual machine is rebooted.
  • The virtual machine is paused or resumed.
  • The virtual machine is restored from a snapshot.
  • The virtual machine is live migrated/moved (eg. VMotion) for common migration scenarios.

Virtual machine live migration/move scenarios that may cause licenses to go untrusted include:

  • VMWare moving from one vCenter to another (cross-vCenter migration).

  • Microsoft Hyper-V moving from one System Center Virtual Machine Manager to another.