Guide Deploy Microsoft Teams Client with Configuration Manager. In this guide, we Deploying Microsoft Teams Client with SCCM. Not perfect – but work well. Tested with SCCM 1610 and SCCM 1702 installation (not Hybrid).

Let’s go:

1. Create folder at your SCCM Distribution Point for Microsoft Teams Client setup files. (in my case D:\Install\Microsoft Teams\1.0.00.7405);

2. Place to folder Client setup file and create *.bat file with next strings;

NOTE: if you have very fast PC’s in your network – increase timeout;

3. Navigate to Software Library\Application Management\Applications. Click Create Application in upper menu;

4. For General, select option Manually specify the application information and lick Next;

5. For General Information, fill out all fields that you wish, click Next;

6. For Application Catalog, fill out all fields that you wish, add Icon (250×250);

7. Click Next;

8. For Deployments Types click Add;

9. For General, at Type choose Script Installer and click Next;

10. For General Information, enter Name, add some Administrator Comments or Languages. Click Next;

11. For Content, select Content Location. At Installation program enter:

NOTE: this is *.bat file from beginning.

12. At Uninstall program enter:

NOTE: Microsoft Teams installing to user folder “C:\users\<username>\AppData\Local\Microsoft\Teams\”.

13. Click Next;




14. For Detection method click Add Clause;

15. At Setting Type choose:

16. At Hive choose:

17. At Key enter;

18. At Value enter:

19. Set check mark at This registry key is associated with 32-bit application on 64-bit systems

20. At Data Type choose:

NOTE: you may click OK and set detection method to installed or not installed. Or set second options and enter at Value your version.

21. Click OK;

22. Click Next;

23. For User Experience, at installation behavior choose:

24. At Installation program visibility choose:

25. Set Estimated installation time (minutes) and click Next;

26. For Requirements, config as you need, click Next;




27. For Dependencies, config as you need, click Next;

28. For Summary, click Next;

29. Click Close;

30. For Deployments Types, Click Next;

31. For Summary, click Next;

32. Click Close;

33. Distribute content to Distribution Point;

34. Deploy Application to Device Collection;

Install Microsoft Teams Client from Software Center:

1. Go to client and open Software Center;

2. Select app and click Install;

NOTE: App installation time increase by the time from timeout in *.bat file

3. Desktop link created, so app installation goes good, wait for timeout;

4. Cool, application installed;

5. Worked;

6. Let’s Uninstall it;

Perfect!

P. S. Deployed for the company:

  • Grainger

    If SCCM runs under the System account context then won’t %localappdata% be for that account and not the currently logged on user?

    • Andrei Pryymak

      In this case you run as service account, but app install for current logged user. App can be installed only if user logged in. Installation behavior – For current user, run as account not current user, it’s only run installation for current user.

  • Paul Turpie

    What is the timeout for?

    • Andrei Pryymak

      There is timeout (based on PC perfomance), because detection rule don’t recognize installation if you run simple silent installation “Teams_windows_x64 /s”, there is some idle with keys creation. But with timeout after product installation – detection rule work as it must. In simple words timeout for correctly detection.