This message was deleted.
# citrix-vad
s
This message was deleted.
d
If you have till the end of the year, why not update all the components then?
a
That's most likely the way forward. Just get the VDI done, then worry about upgrading the infrastructure.
d
I would say. Upgrade, then improve the experience. There's huge amount of features with 2203, coming from a 1912 deployment. So improving first and upgrade after, seems a bit off.
a
Ok. That makes sense. I have to see what road blocks there are to going 2203 first. We have multiple environments and 2 data centers. I have to check, but I believe we could do an in place upgrade of 2016 server to 2203 LTSR.
r
Its OK to upgrade the DDCs and VDA only for what you are trying to achieve. Some features will require upgrading the catalog version.
j
What Rob says is important. PVS becomes your stumbling block. You can't update the PVS Device Target agent to a newer version than the back end PVS Servers, without experiencing issues. I haven't tried to see if the 1912 PVS Target Agent will play nicely with 2203 VDA, but I wouldn't take that path for production and support reasons. Always upgrade the back-end components first, then you are supported.
r
I have done many 1912 to 2203 upgrades. From 1912 flat or CU1/CU3 to 2203 CU2. The only thing that stuck out on these environments were virtual channel security policies. Some choose to doable it, some put in the virtual channels.
a
Thanks for the info about PVS. We rely on that. I'm not directly involved with that Citrix environment any longer, so I was asking to see what options that team has.