This message was deleted.

only doing the controller side upgrades this weekend.......keeping the desktop agent at 1912 cu1 to start and tackling that next

As to your other question, you can jump to 2203 from any 1912 build, so you're good there.

ok cool thanks guys! i'll read over that link as well.....correct me if i'm wrong but i THOUGHT that loginui issue was only w/ the upgraded desktop agent wasnt it?

We started with our persistent MCS, and so far I think things have been fine. My own VM has been solid.

@Andrew Gresbach I honestly don't recall anymore. But read through this and see if anything applies.

cool thanks guys! main thing was confirming if we could do the direct jump which i was pretty sure we could but being paranoid 🙂. from what i've heard the backend upgrade has been pretty solid and issues mainly stemmed from the new desktop agent so gonna ease into that after we knock this one out. i wonder if there are any big changes from SF 1912 to 2203 but we'll see 🙂

Make sure your 2203 CU1 ISO is from August 24 or later. Citrix reissued CU1 quietly; the initial release had a problem with its RPM.DLL.

Virtual channel allow list is enabled by default

yup for sure i made sure it was CU1 because of that.

Are you swapping controllers or upgrading Citrix in-place?

so what would the virtual channel allow list affect? not sure if we use that right now

Depends on your environment. Webex, Jabber, Bluejeans, etc.

upgrading in place.....we had our original controllers on server 2012 so a month or so ago we added 2 additional server 2022 controllers to the cluster , then removed the 2012 so as far as i understand we should be able to direct upgrade

Windows Media Player, Dragon, Epic, Zoom... anything that uses a custom virtual channel would be affected.

cool ya i was gonna roll with what we have and see how it goes if we need to adjust after

Here is an example of the Virtual channel list. Windows Media Player: CTXMM,C:\Program Files (x86)\Windows Media Player\wmplayer.exe Nuance Dragon Medical One (your SoD.exe may be in a different location, as I used the copy file install method and not the MSI): PSPSBEX,C:\Program Files\Nuance\DMO\SoD.exe PMICIIB,C:\Program Files\Nuance\DMO\SoD.exe PSPMIX,C:\Program Files\Nuance\DMO\SoD.exe NUCAAUX,C:\Program Files\Nuance\DMO\SoD.exe NUACOM,C:\Program Files\Nuance\DMO\SoD.exe NUAPLAY,C:\Program Files\Nuance\DMO\SoD.exe NUAREC,C:\Program Files\Nuance\DMO\SoD.exe Cisco WebEx Meetings: CSCOMT,C:\Program Files (x86)\Webex\Webex\Meetings\meetingshvdagent.exe Newer WebEx-Teams CSCOTM,C:\Program Files\Cisco Spark\dependencies\teamshvdagent.exe BlueJeans: BJNBLUE,C:\Program Files\BlueJeans\current\BlueJeans.exe BJNLOGS,C:\Program Files\BlueJeans\current\BlueJeans.exe Zoom https://support.zoom.us/hc/en-us/articles/4412351225101-Configuring-the-Citrix-virtual-channel-allow-list-policy-for-Zoom ZOOMHDA,C:\Program Files (x86)\ZoomVDI\bin\Zoom.exe ZOOMHDC,C:\Program Files (x86)\ZoomVDI\bin\Zoom.exe ZOOMHDS,C:\Program Files (x86)\ZoomVDI\bin\Zoom.exe ZOOMHDV,C:\Program Files (x86)\ZoomVDI\bin\Zoom.exe ZOOMHDX,C:\Program Files (x86)\ZoomVDI\bin\Zoom.exe Sources https://www.citrix.com/blogs/2021/10/14/virtual-channel-allow-list-now-enabled-by-default/

Ray saved my list, lol

That was collected from Slack and from Nick and Myself

And the Webex unified client isn't entirely accurate.

Got anything on Cerner?

But they're completely useless

Ahh I just got an updated Webex this morning.

Cerner support is pretty good, though, so I bet they could tell you.

Here is what Webex gave me

CSOMT may be the missing one. It's not in my list.

Yea, if you contact Cerner, they will have it.

wait, hold on, we have Webex here and I know the logging is enabled. let me check

Most vendors have updated this list bynow

awesome thanks guys for the help! for those of you that did the 1912 to 2203 upgrade, about how long did the upgrade take for you?

I don't see CSOMT in my logs. Weird.

They gave me this 57 page pdf.

i setup a 2hr downtime window so i figured that was more than plenty

Nice

I guess it depends on your footprint @Andrew Gresbach.

2 hours to do what?

2 delivery controllers so probably looking at those 2 controllers, 2 storefront servers possibly (just upgraded those from 7.15 to 1912 last week) and probably the 1 license server (thats quick i know)

IMO, 2 hours should be fine, but you might want to bake in some extra just in case shit happens.

that should be enough time. 15-20 minutes a DDC, SF is like 5-10 minutes

FWIW, Citrix TAM just told us today that we should go from 1912CU1 to CU5 prior to the 2203 upgrade to avoid rare database issues

cool yup thats what i was thinking

lol, jesus Citrix

@Bill Pennie The Docs are misleading then lol.

I hated having to do those double jumps.

ya i'm not a fan either

it seemed more of a CYA type of thing for a single issue that has cropped up

Click on Site Test, get to test 265 of 266 and sit there for 10 minutes

cool ya i get it

I wonder why they say this. I heard of folks doing both to be honest.

I have done both before.

right, their documentation says you dont have to but like he said after the fact they probably had 1 ticket and a weird rare issue so now they are covering their butt

@Andrew Gresbach just backup the DB, and do the "oh shit" snapshots just in case

yeah, I've seen the chart, and they said it should be fine, but we're healthcare with the single largest in-house Epic installation so CYA lol

What Ray said

oh yea, def need a CYA just in case.

yup for sure.....we have sql backups every night at 9pm and gonna do controller/server snapshots

Single largest Epic? UPMC?

We opted out of hosted Epic to host it ourselves lol

I don't know anyone who has Epic host their stuff yet. My last company was at least talking to them about it, but I would bet against them doing it.

~40k concurrent users, split among 4 farms, with active-active failover (semi-automated) between 2 datacenters

@Bill Pennie not a problem! thanks!

Whats the pre-req say?

havent found any useful info in the log just yet