Today I was asked whether it is possible to stop the Teams desktop client from automatically loading on start-up once deployed to a user.
The reason we have to consider this is because IT need to control the deployment of the application and therefore we all know that deployment success rates are hard to achieve within a short window of time. Typically it can take anything from 10 to 30 days to reach 95% deployment coverage across devices. This is mainly due to device availability impacted by user connectivity and use.
Obviously the best way to enable Teams, is to ensure that users have the tools to use Teams from the moment they are enabled. It is frustrating to be told you are enabled for Teams, but you cannot find the client. Yes they can use the web version and yes they could probably download the client and install themselves, but there is such thing as application control policies in organizations.
This means that the Teams client is going to deployed ahead of time. And the default auto launch is just a frustration to users who are yet to be enabled.
We can’t get them to login and change the behaviour in the UI because they are not enabled yet for internal logistical reasons.
As there are no installation options for automatic silent deployment we have to add a post installation task to the SCCM deployment.
This task should remove the registry key made in the following location
and remove the string value:
Remove Via PowerShell
Remove-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Run -Name "com.squirrel.Teams.Teams"
Via Command Prompt
reg delete HKCU:\Software\Microsoft\Windows\CurrentVersion\Run /v "com.squirrel.Teams.Teams" /f
Mark is an Independent Microsoft Teams Consultant with over 15 years experience in Microsoft Technology. Mark is the founder of Commsverse, a dedicated Microsoft Teams conference and former MVP. You can follow him on twitter @UnifiedVale