Andrew Gresbach1709152664
-
Posts
197 -
Joined
-
Last visited
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Andrew Gresbach1709152664
-
-
4 minutes ago, Jeff Riechers1709152667 said:
I have been routinely updating the Teams client and Workspace, and have not seen any issues.
Are you having issues?
What I'm referring to is the new MSIX teams clients, not the traditional one that's been out for years. As far as I've been able to find, I don't see any documentation of VDI optimization with the new client between the workspace app locally and a VDA nor any indication in the team's client that any voice or video calls are being optimized like they do with the current client. So that's what I'm curious about. My testing has been hit or miss so it feels like pre-optimization state. The other issue. I've run into that isn't related to optimization since it happens locally on a laptop as well is we don't see a screenshare option in the new client
-
does anyone have any info on Microsoft and Citrix roadmap and plans for using the new Teams client in a Citrix environment? It took quite a while for the optimization to work consistently w/ the current client and worried we're starting from square 1 again here
-
we recently started updating from 1912.1000 to 2203.1000 and at least one person is blue screening several times a day . I stumbled upon this page and known issue however in our case the blue screen is showing afd.sys as the failed file (analyzing further points to our Nutanix NIC driver). However we've had that driver on this system and all others for a while w/out issue and only since updating the VDA agent this started. think this private fix might apply to our situation as well or no?
-
curious if anyone else found anything more on this issue. we are in the exact situation where we have that policy set to 7 days but renew time shows 10hrs. Our DC's are still on 2012 so not sure if the temporary group membership feature will apply to our situation. I am going to open a ticket on it but thought i'd check in here as well
-
That makes sense......so if we have a standard 10zig Windows 10 thin client that we are going to be deploying to everyone where we're seeing the scaled back resolution with Teams and found that by ONLY adding the OverridePerformance key (to say a value of 3) that it dramatically improves the video resolution in Teams, would that be safe to add to the image for those devices for now? thought process here would be that its a client that seems to handle that resolution fine . I'd be concerned that having that there for a user at home w/ a bad internet connection might have performance issues since we're forcing it to 720p rather than letting auto determine what it should be (but it sounds like VP9 should be lower on bandwidth so maybe ok?
-
one other update on the topic of quality on the video i found this helped quite a bit setting the override key on the client. is there a reason it might dumb it down when it seems to be clearly capable of handling the higher resolutions (like when we set the override?) . either way great to have that control
-
3 hours ago, Daniel Szomboti said:
We are very interested in these issues as we can't repro them ourselves. What's the case ID and I'll reach out tohave a live debug session.
(long shot that I noticed at some customers. Disable de default audio devices on endpoint, especially if they run on a default Microsoft driver)
Regards,
Daniel
thanks! i'll shoot you a PM on here now w/ the case ID and contact #. I have it acting up right now if you get any time just let me know!
-
On 5/15/2020 at 11:00 AM, Daniel Szomboti said:
Tehnically you need that version of DDC so you get the Studio policy as I mentioned, else the UI doesn't have it.
You can still enable the feature though by registry:Enable optimization of Microsoft Teams
To enable optimization for Microsoft Teams, use the Studio policy described in Microsoft Teams redirection policy (it is ON by default). In addition to this policy being enabled, HDX checks to verify that the version of Citrix Workspace app is equal to or greater than the minimum required version. If you enabled the policy and the Citrix Workspace app version is supported, the HKEY_CURRENT_USER\Software\Citrix\HDXMediaStream\MSTeamsRedirSupport registry key is set to 1 automatically on the VDA. The Microsoft Teams application reads the key to load in VDI mode.
https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html
DanielHey Daniel, alright so we have our DDCs upgraded to 1912 cu1 and still having horribly inconsistent results in getting Teams to run in optimized mode. I reopened the case # i sent you a PM on and had client/vda & DDC logs. They sent me a citrix link w/ the teams optimization troubleshooting which was very helpful. However I was told that they are unable to send the logs to the dev team unless it happens again. I sometimes can fix it by rebooting my desktop but not always and right now i cant get it working at all (one time ran in non-vdi mode and the rest not connected mode and cannot get it to trigger the hdxteams.exe process on the client. I took more logs and asked to please send both sets of logs off asap if possible but not sure where it will lead. would you be able to help? we're on a pretty tight time frame here before we have execs looking to test this on Friday/ Monday so hoping you can . If so let me know what you need and i'm happy to help. thank you!
-
yup w/out having the DDCs upgraded yet we already have had that HKCU key in place w/ the 1912 VDA so that makes sense. so what do we do when we have that key in place and Teams still doesn't show "optimized" or show the USB. webcam/headset even though it shows as redirected and optimized in the Citrix toolbar? (and works in other apps) just so we know the next troubleshooting steps other than just the usual cdf traces and wait for results?
on a similar note, when it DOES work, is it expected behavior right now to show a HD preview of myself but the other side see's a pretty rough looking video ? (ie. my side see's what looks like 720p and the other side 320p). curious if thats just how it works right now w/ WebRC since if i. get a call from a physical laptop w/ Teams it doesnt seem to degrade the video like that
-
1 hour ago, Daniel Szomboti said:
DDC doesn't matter. The only think is you will have to create the regkey to activate the MS Teams optimization feature manually. 7.15 DDCs don't have the Studio policy.
Regards,Daniel
so in our case where the VDA is 1912, and DDC's are 7.15.2000 (upgrading this weekend to 1912 cu1) would we need to do anything? we were told we cant get supports help w/out having the DDCs to 1912 so going to get that done first. I sent you what my current ticket # is (i think it was archived now) so any help you might have would be appreciated!
-
1 minute ago, Daniel Szomboti said:
Depends what GEO you are located in, if Europe yes. Regardless I will be working with that engineer if it's Teams :)
thanks! i am on the phone w/ the tech now actually. they are saying even though we are running the 1912 workspace for windows and 1912 VDA, it may not work because our DDCs are still on 7.15.2000.....would that sound right? we are planning a maintenance window to get those DDCs upgraded to 1912 soon but i thought just the VDA agent and Workspace were the critical pieces here? i'm actually having inconsistent behavior now where my teams client doesnt even show optimized when it should nor does it always see the usb headset/mic (even though they are showing as redirected to the session
-
On 5/7/2020 at 9:38 AM, Daniel Szomboti said:
Ok, well in that case we can certainly take traces and have a look. Can you open a TS case to my attention?
great thank you! i'll open a case this morning .....should i just add your name in the notes and it will get redirected to you ?
-
thank you for your input here! so to start yes if we run teams native on the windows client everything works perfect so i think the specs are not the issue here. It doesn't sound like i'm alone w/ these weird sound/video issues w/ the teams optimization at least recently as i'm reading around on it. I SHOULD have most everything in that article taken care of as far as the allusers install, up to date workspace client and VDA .....and i can confirm it DOES show optimized. Like i was saying when i start a video call the video preview looks great, its when the call actually starts it is starting to go south on us so just was curious how to even troubleshoot that (what end it could be at, what else is affecting it). So is the UDP audio option not worth digging into for this specific issue ya think? was just a thought as i've known that can help w/ some other voip situations
-
We are just starting to try Teams video/audio calls w/our Windows clients (using the latest Workspace app and 1912 VDA ) and having mixed results......In some cases it works just fine but in others audio calls sound robotic/choppy and video can be super grainy (like a webcam feed from the late 90s). In those cases the pre-view of your own video feed looks perfect.....curious what others experience has been. Also if anyone has best practice recommendation for Citrix policies, setups they've found help? We currently arent using UDP for audio but looking into that in case that might help.
any advice here would be appreciated! thank you
-
as it turns out my issue is the new "Use cache to accelerate actions processing". Once i turn that off all works fine......i opened a case yesterday on it so i'll see where that turns
-
Has anyone noticed an issue with 2003 agents not getting policy changes? all was fine on 1912 (and still is on the machines w/ that older agent) but my test machines w/ 2003 wont get any assignment changes I am pushing out (registry, file associations, etc) for some reason. I've tried a 1912 to 2003 agent upgrade and a fresh from scratch 2003 agent install for comparison so far
hoping its just something dumb i'm missing because the file association changes in 2003 seem to work really well so far in testing!
Edit: this may be a cache issue so i may have to check my boot up script to see if its running correctly to refresh cache at that point. However i have found that if i make a policy change i used to only need to refresh the agent host settings and/or workspace agent settings but now i have to refresh the cache to show any new changes...maybe something new w/ 2003?
-
you are our hero here on this one! this looks to have done the trick for us too on 1903! we were running about 70-80 seconds for 2 screens........25-40 on single and now i'm getting that on both so thank you! i have an escalated ticket w/ Citrix that i had to gather more difficult logs than i can remember at this point so i'm thrilled to be able to put this one behind us!
-
yup good addition......i completely forgot about that one too , we ran into that a couple of years ago when we first implemented AHV. we had that but also needed the studio settings i posted above to get things better
-
Well sort of.......in our tests with windows clients and setting that key to a 0 brings back the sharing button but it only shares in a teams call sort of way (no give take). If i do the same on my mac client (same session). i get the normal sharing and give take options. however if i share with someone on a windows client w/ workspace i'm unable to use the dropdown to give them control.....if i do the same w/ a person using an html5 session all works fine
so it seems something isolated to just windows clients for some reason w/ the 1912 vda (not 100% is the 1912 is playing a part but given how this thread started i'm betting it does)
and even stranger is on a windows client if i have that key set to 1 the desktop sharing is gone completely .....is that specific behavior the microsoft bug that was referenced? just so i'm keeping track of whats "expected" now and what isnt
-
fair enough.......so here's what i'm seeing:
Windows Client:
-Current Workspace for Windows client
-1912 LTSR VDA on Windows 10 x64 1903
- Computer\HKEY_CURRENT_USER\Software\Citrix\HDXMediaStream\MSTeamsRedirSupport Set to "1" =. Screen Share button completely missing
- Computer\HKEY_CURRENT_USER\Software\Citrix\HDXMediaStream\MSTeamsRedirSupport Set to "0" =. Screen Share button is there but sharing acts like a Teams call where it DOES share but w/no give/take options
Mac Client:
-Current Workspace for Mac client
-1912 LTSR VDA on Windows 10 x64 1903
-Computer\HKEY_CURRENT_USER\Software\Citrix\HDXMediaStream\MSTeamsRedirSupport Set to "1" or "0" =. Screen Share button is there and screen sharing appears to function normally (i can share and see the give/take option.....however clicking the "give control" dropdown now does nothing if i share with someone on a Windows client on the other end.......if i share w/ someone using an HTML5 based connection on the other end works fine)
I have not tested yet on a Linux client but i'd imagine it will do similar to the Mac (being a client that does not currently support Teams optimization
Odd thing is this all used to work just fine on my Mac so not sure what changed here
-
are you we talking about teams web here or the full client? the issue that we're seeing w/ this is the full Windows Client for reference. and we HAVE been able to use the share screen and give/take control option pretty regularly until recently (i want to say it was around when we started using 1912 but cant say for certain)
and when you say microsoft limitation do you mean limitation when working with Citrix?
-
Has anyone had any luck w/ this? we cannot get any rhyme or reason to screen sharing to actually work consistently. Some days its there, some days its gone ......in some cases if we delete the Teams folder under appdata\roaming it helps for a little while. even weirder now more often when some of us try it will give the option to share but when we try it it almost acts like a Teams call and not just sharing so we are unable to give control (that toolbar is flat out missing). so we are stumped
-
thank you for the info here! we actually are using app layering w/ user layer as well so really only have that first time logon once for each user (since user layer gives persistence ) so we may have a slightly different issue ...... i do have that first time animation turned off in our image so all set with that and right now we get around 30-40 seconds (sometimes less) for single monitor logon and 70-80 for dual. I have noticed in some cases if i lower the resolution down to something like 800x600 it drops the time so the display res seems to play a part here for some reason.
good to know you're working with microsoft on it. we have an escalated ticket w/ citrix still going and i've done a ridiculous amount of log collecting so far (client, vda, ddc, procmon, video recording, etc) and currently being sent to engineering i'm told so maybe between both of our tickets we can get somewhere here!
in our case when i test rdp w/ dual screens its just as fast as single so not sure why we are seeing that different than your tests but we'll keep plugging away! thanks for chiming in!
-
ya i agree that sounds like it could be messy. thank you for checking! i noticed defender is not listed on this site so was curious if there is anything specific for that app specifically too https://docs.citrix.com/en-us/citrix-app-layering/4/layer/layer-antivirus-apps.html
yup thats what i thought which wouldnt be the end of the world i guess.....just possibly could get a mismatch on the non persistent machines depending on if someone is signed in and user layer mounted or not vs what file is on the not in use one
New Microsoft Teams MSIX / Citrix integration
in XenDesktop 7.x
Posted
My worry is this new client is a total rebuild under the hood so I'm not sure the current method would work the same way but I'm hoping I'm wrong? and it sounded like it's a ready or not here it comes situation with the new teams and new outlook so this will be interesting