Deploy Microsoft Equipes Client with Gerenciador de configuração. Not a perfect method – but work very well. Tested with SCCM 1610 e SCCM 1702 instalação.
Atualizar: There are now *.MSI files available, so you don’t need this publicar anymore.
Create Microsoft Teams client application deployment
1. Create a folder at your SCCM Ponto de distribuição for Microsoft Equipes Client setup files. (no meu 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
OBSERVAÇÃO: if you have very fast PC’s in your network – decrease timeout;
3. Navegue até Software Library\Application Management\Applications. Clique Create Application in the upper menu;
4. Para General, select the option Manually specify the application information e clique Próximo;
5. Para General Information, fill out all fields that you wish, clique Próximo;
6. Para the Application Catalog, fill out all fields that you wish, add Icon (250×250);
7. Clique Próximo;
8. Para Deployments Types clique Adicionar;
9. Para General, no Tipo escolher Script Installer e clique Próximo;
10. Para General Information, digitar your Nome, and add some Administrator Comments ou Languages. Clique Próximo;
11. Para Content, selecione Content-Location. At the Installation program digitar:
"teams.bat"
OBSERVAÇÃO: Esse é um *.bat file from the beginning.
12. No Uninstall program digitar:
"%LocalAppData%\Microsoft\Teams\Update.exe" --uninstall -s
OBSERVAÇÃO: Microsoft Equipes installing to user folder “C:\users\<nome de usuário>\AppData\Local\Microsoft\Teams\”.
13. Clique Próximo;
14. Para the Detection method clique Add Clause;
15. No Setting Type escolher:
Registry
16. No Hive escolher:
HKEY_CURRENT_USER
17. No Chave digitar;
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams
18. No Valor digitar:
DisplayVersion
19. Set check mark at This registry key is associated with a 32-bit application on 64-bit systems
20. No Data Type escolher:
String or Version
OBSERVAÇÃO: 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. Clique OK;
22. Clique Próximo;
23. Para User Experience, at installation behavior choose:
Install for user
24. No Installation program visibility escolher:
Hidden
25. Definir the Estimated installation time (minutos) e clique Próximo;
26. Para Requirements, config as you need, clique Próximo;
27. Para Dependencies, config as you need, clique Próximo;
28. Para Resumo, clique Próximo;
29. Clique Fechar;
30. Para Deployments Types, Clique Próximo;
31. Para Resumo, clique Próximo;
32. Clique Fechar;
33. Distribute content para Ponto de distribuição;
34. Deploy Application to Device Collection;
Install Microsoft Teams Client from Software Center
1. Go to the client and open Centro de software;
2. Select the app and click Instalar;
OBSERVAÇÃO: 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;
Perfect!
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?
Oi. 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
Obrigado. timeout solved my problem.