This message was deleted.

That feature will be introduced in version 12.0 of Teams.

I do this all the time - click on three dots and kill video ???

That doesn't look like an optimized Teams session...

Yeah I want it turned off permanently

I feel seen @Nick Panaccio 😄

😄

We're testing Teams with video tomorrow on our W10 vdi's will be interesting I don't even think they people here realise the demands of this application. THe main boss sent out an email asking for everyone to join a meeting tomorrow ideal with video .

IME, without having Teams optimized, video killed our W10 VDAs. CPU above 90% full time. This was on 4 vCPU/8GB RAM VMs, too.

Too be honest I started working here about 6 months ago I haven't been involved in anything regarding teams rollout and testing, which is annoying. Lets see what happens.

I look forward to you joining our clan of Teams hatred.

Jeez we only have 6 gig and 2.4gig x2 logical processors it's going to crumble hard tomorrow,

ProcMon will kill the CPU just as fast, really. I don't know of any scripts to run, and you can probably just look at Task Manager to figure out the bottleneck. IMO, the key is to make sure that you have Teams optimization enabled, which it is by default, and are using the machine-based install. Unless you have a GPU for your boxes, though I don't know what that experience would be like.

If you don’t have GPU accelerated VM’s make sure to disable GPU hardware acceleration. You are NOT able to do this with a regkey or GPO (Remember, we are talking about MS TEAMS here), you have to change this in the desktop-config.json file of each user. There is a simple way to do this. BEFORE your users start MS Teams for the first time, copy a template.json file to “C:\Users\Default\AppData\Roaming\Microsoft\Teams”. You can use my Teams Evergreen script to do it: GitHub - Mohrpheus78/Evergreen If users already started Teams, you can change the settings with a powershell script (run as logon script):

<#

.SYNOPSIS

Change Teams setting per user

.Description

Change the MS Teams VDI installer app settings, such as GPU acceleration or fully close Teams app

.EXAMPLE

WEM:

Path: powershell.exe

Arguments: -executionpolicy bypass -file "C:\Program Files (x86)\SuL\Scripts\Teams User Settings.ps1"

.NOTES

Execute as WEM external task, logonscript or task at logon

You can add seeting

#>

# Define settings

param(

# Enable or disable GPU acceleration

[boolean]$disableGpu=$True,

# Fully close Teams App

[boolean]$runningOnClose=$False

)

## Get Teams Configuration and Convert file content from JSON format to PowerShell object

$JSONObject=Get-Content -Raw -Path "$ENV:APPDATA\Microsoft\Teams\desktop-config.json" | ConvertFrom-Json

# Update Object settings

$JSONObject.appPreferenceSettings.disableGpu=$disableGpu

$JSONObject.appPreferenceSettings.runningOnClose=$runningOnClose

$NewFileContent=$JSONObject | ConvertTo-Json

# Update configuration in file

$NewFileContent | Set-Content -Path "$ENV:APPDATA\Microsoft\Teams\desktop-config.json"

^Yep. I preconfigure Teams with a custom JSON file that is copied down at logon, with some settings that we want to enforce - disabling hardware acceleration being one of them.

Be careful what you edit the JSON file with. Certain editors seem to stop it applying

Notepad2 or bust

Banging stuff

According to MS it makes a difference, performance-wise, GPU or not

Yeah even I know this I mean i knew you had to switch it off - I don't recall how technically it impacts I/O, threads, cpu load and so on.

It could well be there's a software GPU built in to allow things that need a GPU to run at all - Citrix had one that often made apps slower but allowed apps that literally refuse to work without a GPU present to run https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/graphics/opengl-software-accelerator.html

we use horizon here

I have a vague memory VMware had something similar ... there was a rumour Citrix's was actually something VMware open sourced ....

All Windows 10 Pilot users are experiencing issues connecting to Win10 Test Pools on VDI and some other users may have been disconnected from ***** Desktops on VDI. As a workaround, all Windows 10 Pilot users have been given access to * Deskops as a temporarily to access VDI while the issue is being resolved.   Windows 7 VDI users should be able to login again, although if still experiencing issues, please contact Service Desk. Reason for Downtime Power issues in the IT Data Centre. Alternative Arrangements if Applicable This is under investigation with 3rd party suppliers as a priority one incident.

Sounds like something isn't configured properly, or multiple things. Also, Windows 7? Jesus.

I still have 15000 users on Windows 7 <shrugs>

wtf

So much faster than windows 10 😀

Yeah, you're not going to convince me that it's a good thing, lol.

67000 w7 vdi's here atleast on average, I don't think w10 vdi solution will be ready anytime soon, they should void off teams as being a neccessity for W10 vdi, esp as we're rolling out physical desktops across the offices and thin clients (horizon,imprivata across the hotdesk/patient areas)