https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
n
Are you certain that both the Webex app version installed in the VDA and the VDI plugin on the endpoint is the same, or only one build off? https://www.webex.com/downloads/teams-vdi.html I ask because I have found that the new unified Webex app is much less tolerant of version differences between the two.
I saw similar issues in my W10 20H2/1912 CU3 environment when the VDI plugin was only one build behind the app.
(Endpoint was 42.6.0.22645, VDA app was 42.8.0.23214)
r
o
thx @Nick Panaccio! I had sync'd the versions 2 weeks back, but, i'll check again
@Ryan Gallier! We did have to open USB / audio / mic redirection via Citrix policy, but the virt channel allow list is only for 2109 or later, AFIAK
r
Ah, sorry, I glossed over 1912 CU4.
n
Yeah, disabled by default in 1912.
o
@Nick Panaccio: Anything you had to do windows firewall / appliance firewall wise to make it work? Does your virtual channel show as open / green ? on this sub-page of the WebEx client? This is my first time doing WebEx on VDI, as it's Citrix, i'm used to things not working as excepted on the 1st attempt 😜, i'm thinking I missed something simple ?
n
I didn't request any firewall changes, though I can't speak for our UC team who owns the app. Perhaps they did, but I'm unaware of it. Before you go into a meeting, this is what I see for Health Checker:
And yes, there are a few other gotchas around the install. 1. What was your install string for the app install on the VDA? Mine is:
Copy code
msiexec.exe -i Webex.msi ACCEPT_EULA=TRUE ALLUSERS=1 AUTOSTART_WITH_WINDOWS=FALSE AUTOUPGRADEENABLED=0 ENABLEVDI=2 FORCELOCKDOWN=1 ROAMINGENABLED=1 /qn
Note the ENABLEVDI switch.
There are also three registry keys that I apply via WEM (disable auto run, disable HW accel, enable VDI):
Copy code
Path: HKCU\Software\Webex\ProdTools
Name: AppAutoRun
Value: 0
Type: REG_DWORD

Path: HKCU\Software\Webex\JoinMeetingOption
Name: EnableVideoHWAcceleration
Value: 0
Type: REG_DWORD

Path: HKCU\Software\Webex\NativeVDI
Name: VDIFeatureEnabled
Value: 1
Type: REG_DWORD
o
ok! great, thank you, i'll try out those HKCU keys today, and re-do the install with switches
👍 1
Thanks again, Nick. Tried just now, and had the same result with the updated GPP keys provided , sync'd Web clients on desktop/VDI. I will more than likely ask the client to open a ticket to Cisco as the next step
👍 1
n
Hopefully, it's something dumb, like a missing firewall port that needs to be opened. Everything I posted is all I do for Webex to work in our environment.
s
@Owen Reynolds did this registry key worked for u
o
Hello! In the end , the issue was fixed by a re install of Ms webview2 runtimes
s
Which version u are using and Webview2 is prerequisite?
n
Interesting, I had no idea that WebView2 was a requirement. Looks like it's new as of v42.6.
o
Neither ! I had case opened to Cisco, but I ended up knowing more about the binary requirements in/out of the VDI platform than the support guy. I asked them to please update their support article which calls windows 10 / OSX devices as "thin clients", and the remote VDI platform "HVD" 😛
@Salim Hurjuk: I just went as high as I could go 2 weeks back
s
Ok
I think @Owen Reynolds you should blog it 😎
🙂 1
o
@Salim Hurjuk! Challenge accepted, I'm going to write the cisco webex VDI implementation article that I wish I had read last month 😆
😄 1
s
Ohh Nice
👍
4 Views
Open in Slack
PreviousNext
Powered by