new Teams Group sharing on AVD

Hello guys, wondering if anyone faced the same below issue and you were able to solve it.

Golden image has no teams installed on it, i installed the new teams on my 5 AVDs using the script provided by Nerdio while creating the session hosts.

Fslogix is up-to-date and other posts recommend and teams is working good But on a group call and people need to share their screens, it works for the first person and when the second person tries to shares it just shows white screen. 

any ideas? and Thank you

0

Comments (7 comments)

Avatar
Erik

Having this issue currently, working with my VAR to find solutions. Not only screen sharing, but webcams are also impacted by this issue.

0
Avatar
Dave Stephenson

Fouad Chaar & Erik there is another topic on here (Teams showing blank boxes for shared content and camera images in meetings) where other partners had a similar issue and they were able to fix it by installing the March 2024 release of the WebRTC client (see https://nmmhelp.getnerdio.com/hc/en-us/community/posts/28915016868237/comments/29241760006925).

Have you tried that by chance?

0
Avatar
Erik

I think this is suggesting an old version of the WebRTC redirector? I am afraid of doing that, because an older WebRTC had other issues...

 

0
Avatar
Dave Stephenson

Correct. The other partners found that by rolling-back to the March 2024 release, they weren't having the issue anymore.
There are other potential issues (that they fixed in the v1.54.2407... release), but it seems like the immediate problem with shared content/videos went away when they did that.

0
Avatar
Erik

Not working still, unfortunately..

Here are screenshots from my freshly imaged host with your script running at provision-time. Always strange that Teams always says update available even when bootstrapped freshly :( . And video / screenshare works neither with this teams version nor after "update now" + relaunch. I will echo this on the other thread.

Script reference: https://cssa1fe5c8f4467ad140f129.blob.core.windows.net/custom-scripts/x.ps1
Pass environment variables: TenantDomain:x.com, DefaultDomain:x, TenantId:x, SubscriptionId:x, CustomerName:x
Script output:
Directory: C:\Windows\temp\NerdioManagerLogs\ScriptedActions
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 8/14/2024 3:52 PM msteams
Transcript started, output file is C:\Windows\temp\NerdioManagerLogs\ScriptedActions\msteams\ps_log.txt
################# New Script Run #################
Current time (UTC-0): 08/14/2024 15:52:20
INFO: Adjusting registry to set Teams to WVD Environment mode
The operation completed successfully.
INFO: No per-user teams install found.
INFO: Deleting any possible Teams directories (per user installation).
VERBOSE: Operation completed for: MSTeams_24033.813.2773.520_x64__8wekyb3d8bbwe
INFO: WebRTC Install Found, uninstalling Current version of WebRTC
Directory: C:\Windows\Temp\msteams_sa
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 8/14/2024 3:52 PM install
VERBOSE: GET https://go.microsoft.com/fwlink/?linkid=2243204&clcid=0x409 with 0-byte payload
VERBOSE: received 1308800-byte response of content type application/octet-stream
INFO: Installing MS Teams
VERBOSE: GET https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RW1jLHP with 0-byte payload
VERBOSE: received -1-byte response of content type application/x-msdownload
INFO: Installing WebRTC component
INFO: Finished running installers. Check C:\Windows\Temp\msteams_sa for logs on the MSI installations.
INFO: All Commands Executed; script is now finished. Allow 5 minutes for teams to appear
Transcript stopped, output file is C:\Windows\temp\NerdioManagerLogs\ScriptedActions\msteams\ps_log.txt
Extension added successfully

 

0
Avatar
Peter Yasuda

Hi Erik, it looks like the Teams bootstrapper installs 24180.205.2980.1757, which then auto updates to 24193.1805.3040.8975, which is the version I am showing in Teams now. This directory timestamps are very close: 

    Directory: C:\Program Files\WindowsApps

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----           8/14/2024  3:19 PM                MSTeams_24180.205.2980.1757_x64__8wekyb3d8bbwe
d----           8/14/2024  3:21 PM                MSTeams_24193.1805.3040.8975_x64__8wekyb3d8bbwe

Get-AppxPackage shows the older version: 

PS C:\> Get-AppxPackage | Where-Object { $_.Name -like "*Teams*" }

RunspaceId             : 603fb70e-3430-4e01-852f-80aa8eda0d49
Name                   : MSTeams
Publisher              : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
PublisherId            : 8wekyb3d8bbwe
Architecture           : X64
ResourceId             :
Version                : 24180.205.2980.1757
PackageFamilyName      : MSTeams_8wekyb3d8bbwe
PackageFullName        : MSTeams_24180.205.2980.1757_x64__8wekyb3d8bbwe
InstallLocation        : C:\Program Files\WindowsApps\MSTeams_24180.205.2980.1757_x64__8wekyb3d8bbwe

I am going to try the Scripted Action tonight. I hope I have better results. 

 

0
Avatar
romilda

Such a informative info

0

Please sign in to leave a comment.