Jump to content

Recommended Posts

Posted

Is anyone using Teams? If so how did you deploy it. I would want to push it out via SCCM and also put it on my Citrix session host image.

 

Thanks.

Posted
We use it but we just use the web version. I couldn't see any difference in terms of functionality (even the GUI looks the same). Therefore we decided just to stick with the web client. I also don't need to update the web client.
Posted

Well as far as I can work out it installs in %APPDATA% which is dumb idea. I can get away with that with SCCM however that isn't going to work on a terminal server.

 

Thanks MS.

 

I'll be using the Web Version too.

Posted
Yeah, that would be the plan with SCCM. That's not possible with Citrix as I don't run an SCCM client on the session hosts. It'd have to be a GPO login script or something.
Posted
Teams will auto-update in the same way the OneDrive client will. The problem with packaging the client is the sheer rate of updates you see with it, so it's almost out-of-date as soon as its been packaged!
Posted

We have deployed it via the exe and a powershell script but one of my team came across this which looks promising

 

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17380159-improve-install-options-install-for-all-users-an

 

My biggest bugbear which they said is on their roadmap...

 

If we want to add a colleague from another college into our teams - they have to essentially log out of their teams and into ours.

 

Not cool.

  • 1 month later...
Posted
We have deployed it via the exe and a powershell script

 

Could you share the PS script?

 

I've gotten it to install via SCCM, but something is not quite right. It's creating a folder for each user that runs the install in ProgramData (e.g. "C:\ProgramData\username\Microsoft\Teams\..."), instead of installing to LocalAppData – which itself isn't a great location, but let's not go there.

Posted
Could you share the PS script?

 

I've gotten it to install via SCCM, but something is not quite right. It's creating a folder for each user that runs the install in ProgramData (e.g. "C:\ProgramData\username\Microsoft\Teams\..."), instead of installing to LocalAppData – which itself isn't a great location, but let's not go there.

 

Disregard. We have a GPO that blocks installs from %AppData% and I did not whitelist Teams. This was causing the installer to default to ProgramData instead.

  • Thanks 1
  • 6 months later...
Posted

Hi

I put a blog togther on how i've done it. The MSI is still lacking. Seems like it will autostart for all users or only start if the user seeks out the exe in the profile.

  • 1 year later...
Posted

This might be of interest to anyone deploying Teams...

 

Download: www.masterpackager.com/uploads/file_archive/teams_windows_x64.mst

 

MST to install Microsoft Teams MSI (VDI) to regular Windows 10

 

Microsoft has finally released Microsoft Teams installer that installs all files to Program Files. But still, it is not perfect, because it supposed to be only for Virtualized Desktop Infrastructure (VDI). The big question is if it is possible to install it on regular Windows 10? This is what the Master Packager team tried to figure out.

 

MST to install Teams on regular Windows 10

We created MST file that will enable Teams MSI to be installed on regular Windows 10. Here are the changes we made in the MST file:

 

  1. Created [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\PortICA] registry key
  2. Set ALLUSER property to 1
  3. Created ALLUSERS property and set to 1 to make Microsoft Teams entry visible in Add/Remove Programs
  4. Created ARPNOMODIFY property and set to 1 to not show modify button in Add/Remove Programs
  5. Changed ProductName property from “Teams Machine-Wide Installer” to “Microsoft Teams”
  6. Added Microsoft Teams Icon to be displayed in Add/Remove Programs
  7. Created Custom Action “CA_DeleteDesktopShortuct" that will delete the desktop shortcut.
  8. Created NODESKTOPSHORTCUT=1 property to delete the desktop shortcut. To leave the desktop shortcut just change NODESKTOPSHORTCUT property to 0. Default value set to 1.
  9. Create Custom Action “CA_DisableMSTeamsAutoRun" that will delete Teams run registry to stop auto launching for every user.
  10. Created DISABLEMSTEAMSAUTORUN=1 property to delete Teams run registry. To leave run registry unattached just change DISABLEMSTEAMSAUTORUN property to 0. Default value set to 0.

As just described, with little modification via MST file it is possible to install Microsoft Teams MSI to all Windows 10 machines, not just on VDI. It would be nice to see a proper MSI for Teams that use MSI tables instead of being bundled in a binary file inside the MSI.

 

https://twitter.com/MasterPackager/status/1247988489200848900

 

1gSvmuW.png

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...