A Hyper-V failover cluster consists of multiple nodes. Each node can be protected by installing a PowerChute instance locally. PowerChute instances on each node are independent and are unaware of each other's configuration.
It is possible for Virtual Machines (VMs) to migrate between the cluster nodes following the initial PowerChute configuration. It cannot be predicted which PowerChute instance will handle operations for a given VM at the time of a UPS On Battery event. For this reason, it is recommended that each PowerChute instance in a failover cluster has the same configuration, so that the behavior during VM operations (migration/shutdown/startup) is consistent across the nodes.
This is particularly relevant when VM Prioritization is enabled, where VM operations are performed according to a set of priority groups where each priority group having a list of VMs and a maximum duration. In this case, using a different configuration for each PowerChute instance could cause inconsistent results.
For example, if a particular VM was assigned to the HIGH priority group on one PowerChute instance and to the MEDIUM priority group on another, then the sequence of operations for that VM would vary depending on which PowerChute instance handles the UPS On Battery event.