This message was deleted.

For persistent VDA upgrades? Yeah, it's a bit of a pain if you want to ensure that it completes successfully. In a perfect world, simply running the new VDA installer will handle it all, but that's not always the case. You can give it a try on a small subset of VDAs to see if it'll work for you. At my place, with our images not exactly being clean, we have to jump through the hoops. Run VDACleanupUtility (4x, reboots in between), run the MS VC++ installer, reboot, run the VDA installer, reboot, validate that the RunOnce entry is gone (if not, run the XendesktopVdaSetup.exe to complete the VDA install), reboot, done. It's... a lot.

Just ran a simple quiet install of 2203 here now, and it does not seem to complete all the way. I see that some services are installed, but the VDA version info is not updated... pain..

Sounds like you'll be boarding SS DoItTheHardWay with the rest of us...

Well... I'll have a chat with the apps-team... they have an uncanning way of finding some neat solutions sometimes... not that I think they are that better than anyone else that have tried and failed, but it's worth a try.

Yeah, just have to schedule those ones for after hours. We use SCCM, so it gives us more leeway on how we upgrade.

Yeah, we can use SCCM as well. The trouble is that these users use the VDIs for simulations and stuff, and they can run for days. They don't react kindly to sysadmins that needs to patch something within a reasonable time frame.

At my last place, we used to let people defer 3 times before it forcibly installed. They can whine all they want, but this was happening.

If they had their way, they would never log off. In fact, in the old days we had users that stayed logged in for months... on Windows 7. I'll never complain about uptime and stability in Windows again. 😛

Oh yeah, we had people who used to go nuts over our timeout values. Thankfully I just referred them to InfoSec and went about my day.

Yeah, of course Nick, if they have to suffer a reboot they will. But they will also complain and bicker and cry... 😛

I had a look at automating this in another environment a while back and i ended up just manually upgrading all the servers as trying to make it work using command line just wasn't worth the hassle. So yeah, same experience here

@Geir Sandstad make sure to install latest VC++ before installing vda automatically. Microsoft enforces a reboot if you upgrade VC++.

^This. We added that as a step in our SCCM task sequence thanks to the Citrix installer failing to install that prereq consistently.

If it's a recent VDA the cleanup utility should not be needed. But you might need to reboot during the upgrade though

I'm talking 2203 CU2 here...

Would be interesting to get the logs of the failed upgrades to see what's going wrong

I'll give it another go if we move forward with a different CU, but we have BSOD issues in CU2 so we're sticking with 1912 CU6 for the foreseeable future.

@Nick Panaccio We had BSOD issues after a VDA upgrade as well a while ago, turned out to be a conflick of some sorts with the ControlUp agent. Seems like they've sorted that out in the mean time, the issues is gone now.

We force a reboot post-VC++, which I've always found to be necessary.

If you would upgrade VC++ a reboot is definitely required, not so sure about when it's a fresh install. But I would install VC++ x86 & x64 and then reboot.