This message was deleted.
# citrix-vad
s
This message was deleted.
d
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.
n
Damnit
I guess the next step is to add it.
d
Good luck.
n
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.
r
Yes Nick I think you should use the noresume then have sccm resume
n
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.
r
The problem is its going to try twice I htink becasue its gonna start from the runonce and from sccm
But I guess if you had no issue you had no issues
n
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.
r
If you do all the prereqs separately then you shouldn't need the run once continuation maybe that why your good
n
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.
r
yea that does sound like the issue
you woudl see without noresume
n
I really wish the VDA upgrade process was smoother..............
hint hint
r
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
j
Our CM guy has yet to get a repeatable/reliable CM task sequence...
n
It's hard to judge this deployment because the environment we pushed to is a fucking mess.
Found our issue. We were using C:\ProgramData\Citrix\*XenDesktop*\XenDesktopVdaSetup.exe as the executable instead of C:\ProgramData\Citrix\*XenDesktopSetup*\XenDesktopVdaSetup.exe, as we copied our old 2203 CU2 TS to create this one. So I partially blame Citrix for changing that folder name. So, so dumb.
👍 1
j
Thanks, highly likely we did the same as well. I'll our TS and poke our CM guy if I see the old folder!