This message was deleted.

Today I performed an upgrade from 7.15CU5 to 1912, had no issues sofar with Director, StoreFront, Controller and PVS

Upgraded from 1909 in my lab and had no issues but what I learned in the past years doing upgrades for all our customers, including some of our largest ones, >10k machines is that upgrading from one LTSR to another is basically less prone to issues IF the initial version of the environment is upgraded to the last CU of that LTSR and the same goes for CB. If you're upgrading from 1909 to 1912, you have less chances of having issues but if you upgrade from 7.18 to 1912, the risk grows and you can eliminate that by going to intermediary versions. Still you're losing time which is more valuable. Best is to keep up with versions and when time comes and you'll realize you will not be able to do that anymore, just switch from CB to LTSR to at least maintain a good level of stability for that environment.

We're on 7.15 LTSR CU2, and have been debating just jumping straight to 1912, or upgrading to CU5 first.

@Nick Panaccio we're in the same situation (CU2) and wondering if its smartest to go to CU5 before jumping to 1912. i'm currently testing the 1912 agent in our MCS / App layering environment and seeing weird logon behavior every so often where the desktop will load but then "lock" for several minutes before coming back to life. not sure if its an app layering/user layer supportability issue yet or not

You've got User Layers enabled in your testing? We're an App Layering shop, as well, but aren't using User/Elastic layers. 1911 doesn't mention support for 1912 LTSR, so I've been waiting for the next release.

yup we've always used UL and elastic in our environment and i noticed the same thing (not listed in the 1911 release so figured it just isnt quite there yet as i know it takes a bit of time to catch up)

Have you tested it without UL/Elastic enabled?

I haven't yet but on my testing list of to do's (usual process w/ app layering) and yup thats my post 🙂

Yeah, Rob is usually lightning fast in his replies. May not be the case with the holidays. We're PVS, too, so I may not see the same thing you do.

yup he usually is! but yup its weird.....most of the time the login is fine but then say the 3rd try I will see the start menu/desktop but it doesnt finish loading all my taskbar items and everything looks frozen unless i leave it for a while

I've been waiting for 1912 so long that I any derailment will just depress me, lol.

same here

From what i understand u need to be on cu5 for a smooth upgrade

@Ray Davis thanks! thats what i was leaning towards anyways. my own fault for not staying up on the CU's anywaysy

I am in the same boat man.

i dont have access to our SQL setup so i need to get help for the db upgrade whenever i do it so not quite as simple

What help do you need? Are you allowed to use the service account and login then do the upgrade. The account of course would need citrix admin access and local admin access to the delivery controllers. But its temporary.

well i should say access to sql to do a backup before i run the upgrade just in case. and in past cases the auto upgrade tended to fail so we had to do a manual but maybe that wouldnt happen now

I upgraded from cu4 straightaway to 1912 no issue at all.... the only issue at the moment target device wont be registered...no idea why yet (but i dont think is a generall problem, must be on my side)

I had that issue in my lab. I had to remove the vda completely. Then install again.

Will give them a shot, thank @Ray Davis 👍

Yea man. No prob. What i donis remove from control panel. Reboot. Then run the vda clean up utility Works well

yes, def make sure you are on CU5 first

We're likely going to upgrade the DC to CU5 so the DB gets updated, and then go to 1912. Then go from CU2 to 1912 on PVS, the VDAs, etc.

I been successful in doing things like this. License server. Storefront Vdas One Dc Second Dc.

3rd DDC, 4th DDC, 2nd site, 3rd site, 4th site 👀

upgraded from 1909 to 1912: DDC, Director, Studio, StoreFronts, Lic server, VDAs, FAS, WEM - all good so far - worklaoads and backend on Nutanix AHV. Only one Server 2016 VDA upgrade running on an additional Citrix Hypervisor 8.1 hosting ressource failed, but was easy to recover after a VDA cleanup.

Hi @Ray Davis that works, great.👍 need to change

TrustRequestsSentToTheXmlServicePort results

from

False

to

True

, but after that has worked.

Just tried to upgrade from 7.15.4000 to 1912.. fail... 😕

What issue(s) did you run into?

Fyi I've have been running into vda upgrades since 1903 and up. Darn vda just will not upgrade. So i remove, reinstall now.

If it’s only the VDA install, that won’t matter to me since I use App Layering.

@Nick Panaccio It just didn't install. One of the components would not install because one of the services wouldn't stop. I guess i can blame that on Windows? PvSAgent.exe couldn't stop causing it to fail.

Dang, that's insane.

Tested the 1912 LTSR VDA in my 7.15 environment. At the very least, my whacky upside down Skype webcam issue is resolved with it (and CWA 1912).