For those of you who use an SCCM Task Sequence for VDA upgrades, are you using the /noresume switch? We're not, but we're also telling SCCM to manually kick off XenDesktopVdaSetup.exe post-reboot. Wondering if we should actually use this switch, even though I'm 99% sure that all it does is prevent the VDA installer from adding that .exe to the RunOnce entry in the registry. Troubleshooting some VDA upgrades that are failing around this particular step.

I don't use SCCM, and I didn't use the /noresume switch in my scripting for a long time and suddenly started having issues with the script with 2203 and had to add it. Started getting strange failures to install on some components without the switch.

Damnit

Good luck.

To be fair, we did have an issue with the VC++ component, and had to add a separate task to run that before installing the VDA.

Yes Nick I think you should use the noresume then have sccm resume

My only worry is that we've completed our test deployment, and all that's left is Prod. Kinda hard to change the install string now, especially when I really don't know if this is the issue. SCCM is already forcibly running the XenDesktopVdaSetup.exe locally post-reboot.

The problem is its going to try twice I htink becasue its gonna start from the runonce and from sccm

Good point about running twice. The issue would be a user logging in and that kicking off, when we need the admin account to handle it.

If you do all the prereqs separately then you shouldn't need the run once continuation maybe that why your good

It only runs when a user logs on, but with the SCCM TS, it's kicking off the exe when the device comes back online and checks in.

yea that does sound like the issue

I really wish the VDA upgrade process was smoother..............

yea i dont write code unfortunately Have given that feedback several times. Alot of the issue are thre prereqs and we dont really control those

Our CM guy has yet to get a repeatable/reliable CM task sequence...

It's hard to judge this deployment because the environment we pushed to is a fucking mess.

Thanks, highly likely we did the same as well. I'll our TS and poke our CM guy if I see the old folder!