This message was deleted.
# citrix-vad
s
This message was deleted.
a
Also, if i disconnect from the window client to a mac/linux that button comes back as well so its definitely something w/ the optimization (since linux/mac are not teams optimized the same way)
s
There are some screen sharing limitations when in optimized mode. Do these apply to you? https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html
For what its worth, i have the same issue and after reading the article took it as this is a limitation of the HDX optimization limitations and havent looked again.
a
i have seen that and doesnt seem to apply to what we're seeing i dont think unless i'm misunderstanding. We are not talking about it not working while on a video call or only primary monitor but more so the entire option is missing. if we start a call THEN we can share but do not have the full capabilities like giving control and its a bit confusing if you just want to share content. i was going to open a ticket on it but thought i'd ask here too
hopefully its a bug and not "by design"
s
Yes, i see the same thing. However, it may not be in that article there was a limitation of having to be in a video or audio call already before you can share the screen. That was because teams uses a certain channel for sharing and HDX optimization did not support that channel
I remember being disappointed reading that as I wanted to use teams as a shadow replacement as well as users couldnt share desktop without being in a call already.
n
That's a huge gap, IMO. We use Skype screen sharing all the time here.
👍 2
s
From the article above: "*IMPORTANT:* You can use screen sharing only when you have an audio or video call active, and not directly from a chat window that doesn’t have audio or video." Im still trying to find the official doc about the limitation being because of the certain channel tems uses. Its defiantly somewhere
s
The more i work with teams the more i get disappointed when it comes to VDI! Day by day some more things popsup🙈 this one popsup yesterday.. and today MS confirmed me that the custome background (in a Videocall) is not in any roadmap for the moment to enable on VDI setup. I am sure, more will come
n
The weird thing about the custom background is that if you do the video call test in Teams, it allows you to select a background, etc. Full featured... until you enter an actual meeting.
s
I havent had time to test but i was going to install normal teams in CVAD to see if the background limitation was specific to the VDI version. Its only listed in the MS limitation section and not the Citrix one. However, you have to remember that when teams goes into HDX mode it takes all the browser limitations as it uses the WebRTC stack for multimedia. As MS improves the browser features in teams, you will get them in HDX optimized.
But then there is a different set of limitations just for the VDI version of the MSI
And I have my answer, blur wont work in normal teams or vdi\msi teams when Citrix optimizes either of them. The reason again is because if its not suported in the browser version of teams it wont be in HDX optimized mode. https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams#browsers
a
ugh damn thats what i was afraid of here.......so it IS by design at the moment with the method that they are making the magic happen. so essentially we have to choose which is more important: 1.) video/audio calls that dont suck or 2.) being able to screen share w/out needing to first make a teams call
s
You got it, the HDX optimization magic is webRTC (think of it as browser redirection for the Teams app). If you want that magic you have to live with selling your soul to the MS team that devs the browser support. It sucks but for us, its come down to a training caveat for now.
a
well at least i know its working it it should then and by design currently. hardest thing is we've been on linux so long waiting for the teams optimization there for video and now we are probably going to pull the trigger to upgrade to all windows clients MOSTLY for the ability to do video on teams (silly if you ask me but i'm done fighting it) and we'll have to tell people oh ya that screen sharing that you've started to rely on, ya you cant do that anymore but you CAN do video calls that 90% of you wont ever care to use lol
also, thank you for everyones clarifying here! saves me a ton of time open a ticket!
its too bad because screen sharing works great even NOT optimized so its too bad that that cant be separated from the audio/video (easier said than done i'm sure)
j
So as the discussion about teams in vdi optimized state is getting hot, here’s another „bug“ which I’m monitoring a few days: Teams isn’t started, clicking „Join Teams Meeting“ in an outlook meeting, teams is starting up and „hangs“ for about 30-70 secs in a white screen till the Meeting / joining options appear. Anyone seen this?
s
new one for me, but we have team always startup up. However, there is a bug in the desktop.json where teams VDI does not respect the setting of start up minimized.
a
hmm thats interesting we've had that for a couple of people recently. we also are set to autostart at logon but a few people reported it didnt. we're app layering/user layer too and after clearing Teams folders out of the user layer it seemed to fix it so we just assumed it was somethig w/ that
n
We were just told not to include Teams in our initial (large scale) O365 migration, so if you guys could figure out the bugs for me, that’d be great.
office space Posted using /giphy | GIF by 20th Century Fox Home Entertainment
😂 1
s
One more limitation on VDI with MS Teams You can not join Live events and act as presenter🙈
a
gotta be kidding! we JUST had a demo on this and of course my boss loved the idea of it. is this another thing that doesnt work because of WebRTC and if you disable that to go unoptimized it would work again?
has anyone had an issue w/ Teams consistently running optimized and detecting your usb headset & webcam? using a windows client i can see in the Desktop Viewer that both are detected /redirected/ optimized but having a helluva time getting Teams to consistently work w/ them using the latest 1.3 release