This message was deleted.

what's the OS ? If the site was 7.6, I'm afraid the client OS is out of support. Probably best to rebuild new machines imo.

win10 OS. Cant give em new machines as there are too many devs

I have some scripts here to update the VDA. However, the one for LTSR are a bit out of date since well why the heck would anyone install LTSR anyway ? 😁 Adjust the install parameters to your needs. Make sure to have folder at the same location as the script. For example: 2305\VDAWorkstation_2305.exe Also download the VDA cleanup utility and copy the exe at the same location as the install script. https://github.com/JonathanPitre/Apps/tree/master/Citrix/Virtual%20Delivery%20Agent

we are installing LTSR now. CVAD 2203 LTSR. Our client doesnt upgrade very often. So, I've suggested this ltsr version.

Most client don't so when they pay me to do it I make sure I install the latest and greatest, especially if they are using Teams.

hmm

There's a misconception by customers that if you run LTSR, you can avoid updates. you still have to apply CU.

True.

correct, but if you are always lagging behind on updates, the window is larger with ltsr yes?

correct, but CR is still supported for 1.5 year so that's good enough for most

for support we get covered for 10 years as it is LTSR

with the latest CU yes 😛

Aside from version, are you trying to upgrade from 7.6 directly to 2203?

Yes Martin. This is a parallel version. We still have our 7.6 env running but we've also created 2203 env

your windows 10 and hypervisor support will end before you reach that 10 years too so, you'll have to rebuild your VMs anyway

The update path is then to run vdacleanup and then install yes? The reason I am asking is that I did not think there was a direct update path install wise from 7.6 to 2203 without cleaning the box 1st.

There are other reasons for LTSR. Some software manufacturers require it (healthcare) is one. Another is that the feature updates with CR can cause other issues as well and customers don't want to deal with that. Just depends on the customer needs which is most appropriate

I agree but in my experience CR has been pretty stable, your mileage may vary but the better integrations with Teams and the enhancement in protocol, especially for GPU is critical for some business.

I agree on both. I am in healthcare and LTSR is our deployment currently. If we could get away with installing CR, I'd be for it, but we cannot right now.

To be honest, implementing the servers, configuring, moving VDIs take more than 6-8 months in our environment. Approvals take too long. By the time we configure CR completely, it will be time for an upgrade already 🙂

Make sure if you're doing 2305, to include the UPM hotfix (powershell uninstall UPM components, reboot, install hotfix'd UPM) as part of your upgrade script.

I would wait a few days and go to 2308 instead, plus if you use FSLogix it doesn't really matter

@Jonathan Pitre I created a script for uninstall which works as expected. I also created a autologin and post reboot install script kicks in. But looks like this new VDA version requires multiple reboots. Post installation, and reboot, VDA is not completely installed. I need to manually login again. Is your script compatible with CVAD 2203 LTSR ? Also in your script, how does enable autologin and disable auto login functions work? I dont see any code for those functions in install-workstationmcs-cr file.

@Chai yes I'm also seeing issues with 2308, its looks like an extra reboot is required maybe since the install completes but is broken, a bunch of services are missing. I'm not sure exactly how to fix it yet. I didn't update my VDA LTSR script a while so probably not. Yes the script Install-WorkstationMCS-CR.ps1 reboot automatically and automaticallly logs you back in. The posh module BetterCredentials will save the currrent account password into Windows Credentials Manager and the posh module Autologon will relaunch the script at the next reboot on the console session.

I've observed that too @Jonathan Pitre Services are missing on the VDI. I had to manually start the installation to fix it.

if anyone has an idea how to fix it, please let me know

I m dealing with a VDI right now. Starting manual install. Manual install done. What I've observed is, installation is half way done and failed. It continued when I started manually. Looks like reboot should be delayed. Needs lot of testing though.