How can we help you today?

VMs are not available in the PowerChute priority list.

Issue:

VMware VMs are not shown in the PowerChute priority list.

Product:

PowerChute Network shutdown

Environment:

VMware vCenter Server

Cause:

The VMs have been added to a VMware resource pool.

In the example below, VM AlmaLinux9A and Azure23HCI have been added to resource pool 1

vCenter Server list of VMs

When viewing VMs in the PowerChute priority list, the AlmaLinux9A and Azure23HCI are not displayed.

PowerChute UI not showing the resource pool VMs

NOTE: VMs added to a resource pool will be powered off along with unprioritized VMs.

Solution:

To prioritize VMs that have been added to a resource pool, create a vApp or vApps within the resource pool and add the VMs to the vApp(s)

In the example below, we have created a Test vApp within the resource pool and added the two VMs to that vApp. The vApp has been added to a high-priority group in PowerChute so the VMs will be shutdown last and started first.

PowerChute showing the vApp that was added to the resource pool

Schneider Electric Canada

Explore more
Range:
Users group

Discuss this topic with experts

Visit our community and get advice from experts and peers on this topic and more
Explore more
Range:
  • Help and Contact Center
  • Contact Sales
  • Find our Offices
  • Where to Buy
  • Careers
  • Company Profile
  • Investors
  • Newsroom
  • Report a Misconduct
  • Product Documentation
  • Product Selectors
  • Software and Firmware
  • Product Substitution and Replacement
  • Blog
  • Events
  • Schneider Electric Community
  • Sustainability
  • Legal Information
  • Privacy Policy
  • Cookie Notice
  • Terms of use
  • Change your cookie settings