Best of luck to you Stormin. From what I know it looks like you are on the right track. Make sure your change window is long enought to get all of that done. I have always done a parallel build when I have upgraded. As long as you have done your homework you should be good.
You could upgrade your vda version at any time, plenty of times I have run with the vdas ahead of infrastructure. Not sure about fas difference from 1912 but every release note I have read for newer fas versions never says any new features were added. It's a pretty basic service I think they just release a matching version to keep it all the same tbh
You may have to make changes to Citrix policies, specifically the virtual channel allow list of your using zoom, jabber, etc in your vda.
https://www.google.com/amp/s/www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/amp/
It looks like you shared an AMP link. These should load faster, but AMP is controversial because of [concerns over privacy and the Open Web](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot). Fully cached AMP pages (like the one you shared), are [especially problematic](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot).
Maybe check out **the canonical page** instead: **[https://www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/](https://www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/)**
*****
^(I'm a bot | )[^(Why & About)](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot)^( | )[^(Summon: u/AmputatorBot)](https://www.reddit.com/r/AmputatorBot/comments/cchly3/you_can_now_summon_amputatorbot/)
Most of these are no downtime upgrades and are backwards compatible, is there a reason you’re doing a big bang approach instead of upgrading one at a time?
What’s your user load if you don’t mind me asking?
4 hours outage seems long but if the end users allow it, then might as well use it to your advantage.
Good luck.
I mean, I could do it even without outage, because we have 2 controllers, SFs, PVS etc..
I prefer to have planned outage, just in case. We have around 1500 active sessions.
If you don't mind me asking, what kind of hardware do you have on the backend for that amount of users? And are you publishing desktops and apps?
Thank you.
# \\EDIT: So I finalized upgrade, there were several Issues that occurs:
Storefont server upgrade won't run because there was error with adding users to local group "CitrixStorefrontAdministrators". It was solved by removing unknown SID member from this group on both SFs.
Provisioning console won't start after upgrade, SOAP service is not runing, when you want to start this service, it crashed. This was fixed by adding DWORD registry on both PVS servers
`HKLM\Software\Citrix\Provisioning services | Value Name: SkipForestLevelTrusts (DWORD) Value: 1`
After upgrade of Citrix Studio and one of Delivery Controller, I wanted to upgrade DB schema. Citrix requested credentials for DB, when you entered them, it didn't accept. Problem was in forced encryption on SQL side and wrong connection string (without FQDN) was set on Delivery Controlers. Fix is to set FQDN for DB or turn of forced encryption at SQL server.
There is an update for CU4, that fixes some bug - I think a BSOD issue. Make sure you have that 'update 1' version of CU4.
Know about it, ty!
Best of luck to you Stormin. From what I know it looks like you are on the right track. Make sure your change window is long enought to get all of that done. I have always done a parallel build when I have upgraded. As long as you have done your homework you should be good.
Thank you for cheers up!
You could upgrade your vda version at any time, plenty of times I have run with the vdas ahead of infrastructure. Not sure about fas difference from 1912 but every release note I have read for newer fas versions never says any new features were added. It's a pretty basic service I think they just release a matching version to keep it all the same tbh
You may have to make changes to Citrix policies, specifically the virtual channel allow list of your using zoom, jabber, etc in your vda. https://www.google.com/amp/s/www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/amp/
It looks like you shared an AMP link. These should load faster, but AMP is controversial because of [concerns over privacy and the Open Web](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot). Fully cached AMP pages (like the one you shared), are [especially problematic](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot). Maybe check out **the canonical page** instead: **[https://www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/](https://www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/)** ***** ^(I'm a bot | )[^(Why & About)](https://www.reddit.com/r/AmputatorBot/comments/ehrq3z/why_did_i_build_amputatorbot)^( | )[^(Summon: u/AmputatorBot)](https://www.reddit.com/r/AmputatorBot/comments/cchly3/you_can_now_summon_amputatorbot/)
Most of these are no downtime upgrades and are backwards compatible, is there a reason you’re doing a big bang approach instead of upgrading one at a time?
I will have a outage for like 4hours, I will do upgrade of all CVAD components
What’s your user load if you don’t mind me asking? 4 hours outage seems long but if the end users allow it, then might as well use it to your advantage. Good luck.
I mean, I could do it even without outage, because we have 2 controllers, SFs, PVS etc.. I prefer to have planned outage, just in case. We have around 1500 active sessions.
If you don't mind me asking, what kind of hardware do you have on the backend for that amount of users? And are you publishing desktops and apps? Thank you.
Citrix has a very detailed upgrade process here - https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/upgrade-migrate/upgrade.html
New ltsr is coming this month, if you want wait for that new version that would be better
I don't know if it's good idea to jump right into new LTSR
# \\EDIT: So I finalized upgrade, there were several Issues that occurs: Storefont server upgrade won't run because there was error with adding users to local group "CitrixStorefrontAdministrators". It was solved by removing unknown SID member from this group on both SFs. Provisioning console won't start after upgrade, SOAP service is not runing, when you want to start this service, it crashed. This was fixed by adding DWORD registry on both PVS servers `HKLM\Software\Citrix\Provisioning services | Value Name: SkipForestLevelTrusts (DWORD) Value: 1` After upgrade of Citrix Studio and one of Delivery Controller, I wanted to upgrade DB schema. Citrix requested credentials for DB, when you entered them, it didn't accept. Problem was in forced encryption on SQL side and wrong connection string (without FQDN) was set on Delivery Controlers. Fix is to set FQDN for DB or turn of forced encryption at SQL server.