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

Upgrade catalogs fails without details


Question

Upgrading machine Catalag (MCS) seems to finish successful. Servers are rebooted at night with a reboot script what always runs successful. Studio shows correct image already (which should be used) after upgrading the catalog. Test catalog went fine with immediate reboot. Production failed, servers were not rebooted and all servers were unregistered in studio. Manual reboot of the servers did not solve the issue, we had to re-upgrade the catalog with immediate reboot to solve the issue.

 

We can see in logs that the catalog update should be successful but somehow it does not come through. Reboot fails without specific reason, something we experienced on other times also when updating a catalog.

 

Anyone experienced this also? Eventviewers does not show information enough to come to the root cause. 

 

CVAD 7 1912 LTSR CU2

ESX 6.7.0.40000

VDA 1912 - FL 1811

Windows server 2016

Link to comment

1 answer to this question

Recommended Posts

  • 0

What happens if you use Studio to schedule a reboot?   The actual machine update only occurs when Citrix itself initiates the reboot, so if you are (for example) running shutdown.exe to do it from a batch file, then the update won't happen.   I suspect the scheduled reboot script isn't actually working as well as expected, despite reporting success, and that's why your machines aren't updating.

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...