This message was deleted.
# citrix-vads
Slackbot
06/05/2023, 1:44 PMThis message was deleted.
n
Nick Panaccio
06/05/2023, 2:09 PMI had BSOD issues with Webex and 2203 CU2, but so far 2203 CU3 is working nicely. Webex client 42.12.0.24647 on the VDI VM, 42.12.0.24485 VDI plugin on my endpoint.
Nick Panaccio
06/05/2023, 2:09 PMAlso have Webex Meetings Virtual Desktop Plug-in 42.10.8.14 on my endpoint
Nick Panaccio
06/05/2023, 2:09 PMSince you need both
m
Matt Sliva
06/05/2023, 2:10 PMI'll try re-installing Webex after 2203 CU3. With 2305 everything works as expected.
Matt Sliva
06/05/2023, 6:49 PMStill not working. I am running 43.4.0.25959 on the VDA, same for the plugin on the Windows client. I have the Webex app deployed in Dark mode. Normally the Webex meeting window turns white and it appends - VDI to the name. That's not happening despite having the VDI version installed and the health checker showing green.
n
Nick Panaccio
06/05/2023, 6:51 PMDumb question, but in the VDA's registry, in HKLM\SOFTWARE\Cisco Spark Native, do you have EnableVDI set to 1 or 2? Either should work, though I had used 1 at my last place. New place uses 2 to let it automatically detect the VDI environment.
m
Matt Sliva
06/05/2023, 6:53 PM2
n
Nick Panaccio
06/05/2023, 6:53 PMNot sure what to tell you there then. You may have to open a case with Cisco... sorry in advance, they're not fun to deal with.
m
Matt Sliva
06/05/2023, 6:55 PMAppreciate the sympathy. I know it.
Matt Sliva
06/05/2023, 7:31 PMSo with 2203 I get new meeting freezing and with 2305, I get this. As if it is trying to pass devices through and not use optimization. While inside the meeting, health checker says the "virtural" channel is disconnected. I think something is broke and will hopefully be fixed in the release later this month.
n
Nick Panaccio
06/05/2023, 7:32 PMWhen you say 2305, are you talking CWA or the VDA?
m
Matt Sliva
06/05/2023, 7:32 PMVDA
n
Nick Panaccio
06/05/2023, 7:32 PMokay
m
Matt Sliva
06/05/2023, 7:36 PMWhat a Webex meeting looks like on my 1912 CU7 server. Same version. Installed the same way.
n
Nick Panaccio
06/05/2023, 7:47 PMI have only been testing 2203 CU3 for a few days now, but in CU2 I was getting BSOD's daily. I have probably a dozen Webex calls per week, so if something is going to bomb, I think I'd probably have seen it by now.
👍 1
Nick Panaccio
06/05/2023, 7:47 PMAnd if I just jinxed myself, I'm going to blame you...
m
Matt Sliva
06/05/2023, 8:00 PMHa! I'm looking at the release notes for 42.12.0.24485 and it says it added support for CVAD 7 1912 CU6. LTSR 2203 CU2 is not supported until 43.2.0.25157, along with CR2212. LTSR 2203 CU1 was added with 42.8.0.23214. I'm going to let this rest for a few more days while I wait for the next release. My problems may be related to a lack of support for 2203 CU3, but doesn't explain why CU2 isn't working.
Matt Sliva
06/06/2023, 7:08 PMI have this figured out, but I'm wondering what I can do different. The System event log and RPM errors are what helped crack the case.
I have the Virtual channel allow list enabled and populated with the following settings:
CSCOTM,C:\Program Files\Cisco Spark\dependencies\teamshvdagent.exe
CSCOMT,C:\Program Files\Webex\Webex\Meetings\meetingshvdagent.exe
I was seeing loads of RPM errors and they indicated Webex Meetings was running meetingshvadagent.exe out of my profile despite having Webex VDI w/ MC installed on the base image.
I added a 3rd entry to the Virtual channel allow list:
CSCOMT,C:\Users\*\AppData\Local\WebEx\WebEx64\Meetings\meetingshvdagent.exe
It is now working as expected. What a pain.
n
Nick Panaccio
06/06/2023, 7:25 PMAh, honestly forgot to ask about the VC since we just disable that policy and allow all. So dumb, though.