Deploy Microsoft Teams Client with Configuration Manager. Not a perfect method – but work very well. SCCM으로 테스트 1610 and SCCM 1702 설치.
업데이트: There are now *.MSI files 사용 가능, 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. (나의 경우에는 디:\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
메모: if you have very fast PC’s in your network – decrease timeout;
3. 로 이동 Software Library\Application Management\Applications. 딸깍 하는 소리 Create Application 상단 메뉴에서;
4. 을 위한 일반적인, 옵션을 선택 Manually specify the application information 그리고 클릭 다음;
5. 을 위한 General Information, fill out all fields that you wish, 딸깍 하는 소리 다음;
6. 을 위한 the Application Catalog, fill out all fields that you wish, add Icon (250×250);
7. 딸깍 하는 소리 다음;
8. 을 위한 Deployments Types 딸깍 하는 소리 추가하다;
9. 을 위한 일반적인, ~에 유형choose Script Installer 그리고 클릭 다음;
10. 을 위한 General Information, 입력하다 your 이름, and add some Administrator Comments 또는 Languages. 딸깍 하는 소리 다음;
11. 을 위한 Content, 선택하다 Content-Location. At the Installation program 입력하다:
"teams.bat"
메모: 이것 is a *.bat file from the beginning.
12. ~에 Uninstall program 입력하다:
"%LocalAppData%\Microsoft\Teams\Update.exe" --uninstall -s
메모: Microsoft Teams installing to user folder “씨:\users\<사용자 이름>\AppData\Local\Microsoft\Teams\”.
13. 딸깍 하는 소리 다음;
14. 을 위한 the Detection method 딸깍 하는 소리 Add Clause;
15. ~에 Setting Type choose:
Registry
16. ~에 Hive choose:
HKEY_CURRENT_USER
17. ~에 열쇠 입력하다;
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Teams
18. ~에 Value 입력하다:
DisplayVersion
19. Set check mark at This registry key is associated with a 32-bit application on 64-bit systems
20. ~에 Data Type choose:
String or Version
메모: 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. 딸깍 하는 소리 좋아요;
22. 딸깍 하는 소리 다음;
23. 을 위한 User Experience, at installation behavior choose:
Install for user
24. ~에 Installation program visibility choose:
Hidden
25. 세트 the Estimated installation time (분) 그리고 클릭 다음;
26. 을 위한 Requirements, config as you need, 딸깍 하는 소리 다음;
27. 을 위한 종속성, config as you need, 딸깍 하는 소리 다음;
28. 을 위한 요약, 딸깍 하는 소리 다음;
29. 딸깍 하는 소리 닫다;
30. 을 위한 Deployments Types, 딸깍 하는 소리 다음;
31. 을 위한 요약, 딸깍 하는 소리 다음;
32. 딸깍 하는 소리 닫다;
33. 콘텐츠 배포 에게 배포 지점;
34. Deploy Application to Device Collection;
Install Microsoft Teams Client from Software Center
1. Go to the client and open 소프트웨어 센터;
2. Select the app and click 설치하다;
메모: 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;
완벽한!
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?
안녕. 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
감사합니다. timeout solved my problem.