Anyone utilizing Citrix VDA Upgrade Service? If so, any gotchas? We've been piloting it in our lower environment, and one thing that we noticed is that enterprise deployments (mostly via SCCM, but Windows patching via another process, too) keep throwing it off, as it gets deployed and kicks off during the VDA upgrade process causing it to fail. I know the obvious answer is to have different maintenance windows, but I'm not sure that's possible here.

We tried, but since we manage persona/config with LWL ProU we ran into a block. LWL services have to be stopped when the VDA is installed due to ProU locking WMI writers.

How does it handle the 14 reboots it takes to update the VDA? i ended up making my own scripts to handle the entire process.

I haven't been the one testing this, just hearing about the issues from a colleague. The reboots thing is funny because our SCCM TS accounts for up to 7 reboots so that it doesn't fail, lol.

@Nick Panaccio can you explain a bit more on what you're seeing? Do you mean that during the maintenance window of VUS to update the VDA, some other update process will run as well?

Very nice

VuS itself is able to update the VDA in a very short time. In a previous project, office updates were running at the same time and slowing down the upgrade process. Used it for +50k devices so open for any questions 😁

@Rody Kossen, yes, exactly - somebody is pushing SCCM packages to our VDAs while they are in the middle of the VDA upgrade process, and it's hosing the installs. I think we're going to have to work with the other teams and force dedicated maintenance windows for persistent VDAs where nobody is allowed to push anything on a specific night. We have like 3 different utilities that are used to push software and patches, so it's a bit of a mess.