Jump to content
Welcome to our new Citrix community!
  • 0

Updating Desktop OS Machines Pending Update

Kim Atwater


Can anyone tell us how to force a base image update on individual machines? We have a small Xen Desktop 7, Windows 7 OS environment. We updated the Machine Catalog yesterday, all but two machines updated and those two are showing "Yes" in the Pending Update field. We have rebooted them repeatedly, logged off, etc. but to no avail. They do not seem to realize there is an update pending.

Any suggestions would be appreciated!


Link to comment

4 answers to this question

Recommended Posts

  • 2

Issue mentioned in this thread might be old, but I have faced this issue mentioned in the above thread with XD 7.17. After updating the Machine catalog, rebooted the VDAs multiple times, but still the VDAs didn't get the updated mage and studio "Pending Update" showing "Yes".



--Followed the CTX KB https://support.citrix.com/article/CTX225293


-When  ran the get-brokerhypervisorconnection 


--One of the Host connection state was showing Unavailable, after following the steps (or re-entering the Hyp connection credentials) resolved the issue. Once all the VDA actual power state were reflecting instead of UNKNOWN power state, issue resolved


  • Like 2
Link to comment
  • 0

Yes, we did resolve this...when we attempted to update the Machine Catalog again (to force the 2 machines to update) it was failing with an Image Preparation error so we uninstalled & reinstalled the VDA on the Master Image, created a new Snapshot and then updated the Machine Catalog and machines sucessfully.

Just a side note...prior to uninstalling and reinstalling the VDA it was taking almost 8 hours to update the machines, after reinstalling the VDA the entire process takes less than an hour now.

Link to comment
  • 0

Ok, thanks.. yea, seems like different issues then. I could see a bad VDA install certainly causing issues one off.. I am just seeing this more on Server updating now, whereas desktop MCS updating it would be every now due to issues you describe, but in my case, I have a brand new image with new VDA install and been through it 4 or 5 times to eliminate that.. Multiple installs seeing it.. so I think it might be different. Thanks for your response though!

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...