Deploy Microsoft Teams Client with Configuration Manager. Not a perfect method – but work very well. Testato con SCCM 1610 and SCCM 1702 installazione.
Aggiornamento: There are now *.MSI files disponibile, so you don’t need this post anymore.
Create Microsoft Teams client application deployment
1. Create a folder at your SCCM Distribution Point for Microsoft Teams Client setup files. (nel mio caso D:\Install\Microsoft Teams\1.0.00.7405);
2. Place to folder Client setup file and create *.bat file with text strings;
Teams_windows_x64 /s
timeout 60
NOTA: if you have very fast PC’s in your network – decrease timeout;
3. Navigare verso Libreria softwareGestione applicazioniApplicazioni. Clic Crea applicazione nel menu superiore;
4. Per Generale, selezionare l'opzione Specificare manualmente le informazioni sull'applicazione e clicca Prossimo;
5. Per General Information, fill out all fields that you wish, clic Prossimo;
6. Per the Application Catalog, fill out all fields that you wish, add Icon (250×250);
7. Clic Prossimo;
8. Per Deployments Types clic Aggiungere;
9. Per Generale, A Tiposcegliere Programma di installazione degli script e clicca Prossimo;
10. Per General Information, accedere your Nome, and add some Administrator Comments O Languages. Clic Prossimo;
11. Per Contenuto, Selezionare Posizione del contenuto. At the Programma di installazione accedere:
"teams.bat"
NOTA: This is a *.bat file from the beginning.
12. A Disinstallare il programma accedere:
"%LocalAppData%\Microsoft\Teams\Update.exe" --uninstall -s
NOTA: Microsoft Teams installing to user folder “C:\users\<nome utente>\AppData\Local\Microsoft\Teams\".
13. Clic Prossimo;
14. Per the Detection method clic Aggiungi clausola;
15. A Setting Type scegliere:
Registry
16. A Alveare scegliere:
HKEY_CURRENT_USER
17. A Key accedere;
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams
18. A Valore accedere:
DisplayVersion
19. Set check mark at This registry key is associated with a 32-bit application on 64-bit systems
20. A Tipo di dati scegliere:
String or Version
NOTA: you may click OK and set the detection method to installed or not installed. Or set the second option and enter at Value your version.
21. Clic OK;
22. Clic Prossimo;
23. Per Esperienza utente, at installation behavior choose:
Install for user
24. A Installation program visibility scegliere:
Hidden
25. Impostato the Estimated installation time (minuti) e clicca Prossimo;
26. Per Requisiti, config as you need, clic Prossimo;
27. Per Dipendenze, config as you need, clic Prossimo;
28. Per Riepilogo, clic Prossimo;
29. Clic Vicino;
30. Per Deployments Types, Clic Prossimo;
31. Per Riepilogo, clic Prossimo;
32. Clic Vicino;
33. Distribute content A Punto di distribuzione;
34. Deploy Application to Device Collection;
Install Microsoft Teams Client from Software Center
1. Go to the client and open Centro software;
2. Select the app and click Installare;
NOTA: App installation time increases by the time from a timeout in the *.bat file
3. Desktop link created, so app installation goes well, wait for timeout;
Perfetto!
If SCCM runs under the System account context then won’t %localappdata% be for that account and not the currently logged on user?
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.
What is the timeout for?
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.
0x87D00324(-2016410844) have a idea?
CIAO. Application is installed, this error code means problems with application detection. Try to check if the application installed. if everything fine – check installation detection rules
Grazie. timeout solved my problem.