This message was deleted.
# citrix-vad
s
This message was deleted.
a
I'm not at my desk at the moment but I was able to get this working with PDQ recently. Might be able to translate it to SCCM. I'm message you in a little bit
g
Ah, nice. Hadn't even thought of PDQ. Thanks.
a
I typically can take SCCM sequences and use the logic in PDQ so should work. I'll get in touch after lunch here with what we did
g
OK awesome, thank you.
👍 1
r
This is not upgrade its install but can help. I recommend first upgrading the pre-reqs ahead of time. It makes the upgrade go much easier.
n
Long story short, using a task sequence that does the following has resolved the issue for us: 1. Run VDACleanupUtility 2. Reboot 3. Run VDACleanupUtility 4. Reboot 5. Run VDACleanupUtility 6. Reboot 7. Run VDACleanupUtility 8. Reboot 9. Install VC++ 2015-2022 10. Reboot 11. Install VDA 12. Reboot
Lots of steps, but we've seen up to 4 reboots required for the VDA cleanup utility, hence why we run it that much.
a
Yup that's pretty much our sequence... We do the vda/vc++ part slightly differently but I like this approach. We had to add code 3 to PDQ as a success reference too or it would stall... Not sure if that is anything you'd need to worry about with SCCM ( I think that might actually be called out in the link @Rob Zylowski linked)
n
I think our guys also use code 3 in SCCM, too.
👍 1
g
This is all great feedback, thanks you guys. I have been over and over the Citrix docs for command line and SCCM installs, but just couldn't get my Task Sequences to work right. I'll try Nick's steps and report back to you all. Thanks again!
a
where has yours stalled? always good to do the vda cleanup utility like Nick called out first to clean things up and could always try whatever vda command line options locally on a vm first to make sure thats not part of the issue as well. we had to tweak ours from what we used in 1912 to 2203
✅ 1
n
For the record, ours appeared to be stalling with the VC++ install that is included in the VDA installer. Once we separated that out to its own SCCM package, things started to work.
g
I'm not sure, on my end: I would watch the target Test machine in an RDP window, and it would just suddenly shut down. Not an SCCM pro but I'm sure there's a Log somewhere on the SCCM Server that can tell me what's happening at each stage of the Task Sequence?
a
yup that was sticking for us too.....we currently are using 2 passes of the vda install, the first one w/ the full arguments starting with /quiet /noreboot /noresume (which takes care of the vc++) and then a reboot and then another pass w/ no arguments which i guess is smart enough to use the 1st attempts and works. but i like your approach better just separating it all
another reason to ditch sccm for pdq 🙂
n
If you use /noresume, you should be able to use the local path of the XenDesktopVda.exe (may be the wrong exe name) to continue. That exe is written to the RunOnce registry value as part of the VDA install.
👍 1
SCCM has tons of logs, but if you're doing a command line install, you need to definitely use the /logpath switch (which points to a folder, not a file) for your VDA install.
✅ 1
g
@Nick Panaccio, I forgot to ask you, when we were talking about this: What method do you use for getting the VDACleanupUtility and the VDA software ONTO the end-point device, so that you can then use Task Sequences to run the Tasks we were talking about? We have an SCCM job that might do it, but I thought I'd ask you about your method also... Thanks.
n
I've got no insight into our SCCM environment here, but since I see nothing like 1E Nomad on my VDA, I assume we're using all of the native SCCM mechanisms for delivering content to devices.
👍 1