Teams - Desktop Client

[Homer]

Hi all

 

I foolishly thought that the installer would be for all users... NOPE! It installs to the local profile - hence my efforts deploying it with SCCM/in the task sequence have left me without the Teams desktop app.

 

Has anybody found a workaround for this? I'm not going to deploy it using GPO it's just a ridiculous way to slow down logons.

 

Cheers

[thimon]

I actually prefer the web version, the desktop client has crashed on me a few times On the plus side we're using it quite a lot now!

[Vasriel]

Microsoft intentionally designed it this way, for whatever reason. I had the same problem, I then found this webpage and created a software deployment that deploys to users. It still only installs on the users profile which is a pain:

 

 

https://enterinit.com/guide-deploying-microsoft-teams-client-with-sccm/

[free780]

I thought they would do a store app. Which means you need the store setup for your school/college.

[free780]

https://www.microsoft.com/en-gb/store/p/microsoft-teams/9nblggh4n9tw?rtc=1

[QwertyMash]

As it looks like Microsoft is planning on doing away with Skype and rolling out Teams I guess I am also going to have to look at a deployment method for this that doesn't suck.

 

If I find one I will come back and report it.

[Fazza]

Just tried to install the Teams desktop app and found out the hard way what you guys have already found out that it's a waste of time in a academic environment as it only installs in to the users profile and as all local profiles are deleted when a student logs off it's never going to work!

 

Microsoft must surely no this???

[Fazza]

I don't see any advantage of using the desktop client instead of web. Do you see any?

 

We're currently testing Teams to see if it's any good and our ICT Teachers have informed us they have issues with on the Web but it works fine through the Desktop App!

[Fazza]

What are the issues they are seeing in web version?

 

No idea - it's like getting blood out of a stone with some users!

 

They just said some bits dont work and could it be a port that needs unblocking?! They try to think up a random solution rather than tell us (or screenshot us) what the problem is. I've told them to log the exact issue on the helpdesk and then (and only then) can we look in to it.

[jmig]

Microsoft intentionally designed it this way, for whatever reason. I had the same problem, I then found this webpage and created a software deployment that deploys to users. It still only installs on the users profile which is a pain:https://enterinit.com/guide-deploying-microsoft-teams-client-with-sccm/

 

So I've deployed Teams using this method, and have experienced the following issue: deploying from SCCM, Teams installs to "%ProgramData%\%USERNAME%\Microsoft\Teams" instead of "C:\Users\%USERNAME%\AppData\Local\Microsoft\Teams"

 

I know this is related to the application installing as SYSTEM, but I am unsure how to resolve the issue. The deployment is setup for user to manually install from Software Catalog.

[free780]

Or you deploy to users as a required deployment. I'd go for store or web.

[victory2015]

to help others if you want try my method, i have installed on my profile and copied the teams folder from C:\Users\USERNAME\AppData\Local\Microsoft\Teams to my NETLOGON folder ( or a share on a server for apps )

 

Created a bat file with the following.

 

robocopy "\\SERVER\NETLOGON\MicrosoftTeams\Teams" "C:\Users\%username%\AppData\Local\Microsoft\Teams" /PURGE /MIR

C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe" --process-start-args "--system-initiated"

 

Created a vbs with the following to hide the console window.

CreateObject("Wscript.Shell").Run "\\SERVER\NETLOGON\MicrosoftTeams\InstallTeams.bat",0,True

 

Then assign is as a logon script to the users i want it installed on.

 

Not an elegant design but it will update and work as it should and the logon script will keep files in sync so you can manually update the netlogon with the latest version.