Requirement to update Virtual Hosting Pool ID after moving machines to new host connection
Article ID: CTX482569
Updated On:
Description
After moving virtual machines from an old host connection to a new host connection, you may experience issues with power managing machines from the PVS console or if VMs have been created with BDM Boot Partition, you may not be able to update the BDM Boot partition when you add an additional PVS machine.
This is due to the virtualhostingpoolid for each device in pvs still reflecting the information from the previous host connection.
Requirement is to update the virtualhostingpoolid machine after the machines have been moved to a new host connection.
Resolution
We currently do not support updating the virtual hosting pool information for an existing target as it is not a simple update as it potentially may also require an update to the hypervisor ID of every target being changed (which is also something else we do not allow to be changed currently).
Currently since the hosting pool ID is different since the machines were moved to a new hosting connection, you cannot power manage these from the PVS console but you can from studio or from the hypervisor console..
As long as the VMs still have the same MAC addresses and are connected to the same network, PVS streaming will work apart from manual power management from the PVS console.
The only support method to have these machines use the updated virtual hosting pool ID option is to re-create these machines on the new host connection.
You would need to follow the below steps:
1. Convert one of the old targets to a template
2. Use it to spin up new PVS targets
3. Delete all the old PVS targets from the hypervisor, PVS console etc
If there is a requirement to keep the VM names of the machines, then you may delete the VMs from the PVS console after step 1 above.
Any changes being made to hosting pool ID via Powershell, SQL changes, etc. are not supported.
The recommendation Citrix is to re-create these machines so the hosting pool ID reflects that of the new hosting connection.
Currently since the hosting pool ID is different since the machines were moved to a new hosting connection, you cannot power manage these from the PVS console but you can from studio or from the hypervisor console..
As long as the VMs still have the same MAC addresses and are connected to the same network, PVS streaming will work apart from manual power management from the PVS console.
The only support method to have these machines use the updated virtual hosting pool ID option is to re-create these machines on the new host connection.
You would need to follow the below steps:
1. Convert one of the old targets to a template
2. Use it to spin up new PVS targets
3. Delete all the old PVS targets from the hypervisor, PVS console etc
If there is a requirement to keep the VM names of the machines, then you may delete the VMs from the PVS console after step 1 above.
Any changes being made to hosting pool ID via Powershell, SQL changes, etc. are not supported.
The recommendation Citrix is to re-create these machines so the hosting pool ID reflects that of the new hosting connection.
Problem Cause
Expected behavior.Issue/Introduction
After moving virtual machines from an old host connection to a new host connection, you may experience issues with power managing machines from the PVS console or if VMs have been created with BDM Boot Partition, you may not be able to update the BDM Boot partition when you add an additional PVS machine.
This is due to the virtualhostingpoolid for each device in pvs still reflecting the information from the previous host connection.
Requirement is to update the virtualhostingpoolid machine after the machines have been moved to a new host connection
Was this article helpful?
Yes
No
Powered by
