We are working on updating our HP T610 Plus thin clients. We are updating the thin clients to the latest WES7P OS image and also updating to IE11 and Citrix Receiver 4.4.
We are using HPDM 4.6.4
We were able to successfully take several T610s and update the OS image and related software with no issues. We are then able to use HPDM 4.6.4 to successfully pull and image of these updated thin clients into the master repository.
We then create a task to deploy this new image to several thin clients. We setup the task to use cached imaging and then run the task. HPDM then successfully deploys the image to the thin clients.
The thin clients accept the cached image and once the image is fully downloaded they reboot to deploy the image. After the reboot the image deploys and unpacks correctly and then the thin client start the intial Windows setup.
But for 90% or more of these newly imaged thin clients they get hung up during the Windows setup (usually during the message that windows is writting to the regsitry). Once the thin clients get hung at this point they are unreachable and unrecoverable by HPDM and must be imaged via USB.
We think the issue is somehow related monitors being connected to the thin clients. If we completely disconnect the monitors from thin clients and then deploy an image the new image deploys OK. HPDM reports that the image was deployed successfully. If we then go back to the thin clients and reconnect the monitors the thin client is updated and the display appears to be in standard low resolution vga mode. A reboot of the thin client then recognises and sets the appropriate screen resolution and the thin client is good to go.
Does this sound normal that the monitors need to be disconnected to deploy a new image?
Thanks for any insight or thougts.