/build/static/layout/Breadcrumb_cap_w.png

Microsoft Teams Machine-Wide Installer will not run properly from a script

I've tried pushing it by script and via Managed Install and no matter what I try it looks like it runs but fails.  I can go to the KBot directory and run the exact same command and it runs perfectly.  I tried running via a .bat file in the scripting and that also fails but if I run that exact same .bat file from the KBot directory it installs fine.  What am I missing.

Asked 4 years ago 3078 views
6 Comments   [ + ] Show comments
  • Can you please share your command line and batch file? - chucksteel 4 years ago
  • On the Managed Install it's msiexec.exe /i "Teams_windows_x64.msi"
    On the Scripted install the bat is C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\319\Teams_windows_x64.msi - rlbass1 4 years ago
  • Just wanted to mention I am having basically the same issue, I was just about to make a post when I saw this.

    Chuck,
    I posted some more info in the Application Packaging channel in Slack, not sure whether you want me to post it here (it's a bit long-winded) or whether you can just see it there. - ajones88 4 years ago
  • As I said the command line and .bat file absolutely work when run locally but fail when pushed by Kace. - rlbass1 4 years ago
    • Same results here, I am testing the command while run in the SYSTEM context right now, since that is how KACE runs them. - ajones88 4 years ago
  • I think I have it working now, it looks like there can be issues with the uninstall process, which is leaving some registry keys behind.

    Additionally, when installing from the system account it doesn't seem to create an entry in Programs and Features, but does appear to function (Installs teams for users on login).

    The OP's edit in this post highlights the issue with the uninstaller. https://www.reddit.com/r/SCCM/comments/bip1ue/ms_teams_msi_cant_be_uninstalled/ - ajones88 4 years ago
  • add the following options to your install line
    ALLUSERS=1 OPTIONS="noAutoStart=true" /qn /norestart - ggibson 4 years ago

Answers (2)

Posted by: jedinger 4 years ago
White Belt
1

If you're installing this as part of Office 365 (or rather as an addition to Office 365 already being installed), you're best bet is to use the Office Deployment Tool (ODT) with the Office Customication Tool (OCT) to make an xml file that installs it and just push the xml and a batch file to run it. You can hard code the xml file to look to a previous K1000 distro package (the one that installed O365 apps) then just say add teams in the xml (basically in the application picker in the OCT, you add everything that's already there AND teams) and run the ODT setup.exe /configure <xml>. I can upload a sample batch/xml if needed. Only thing I'm having issue with is finding a way to get a custom inventory rule to realize it's installed because it lives in the users appdata\local\microsoft\teams folder.

Posted by: ggibson 4 years ago
White Belt
1

To use the system wide installer make sure you download the msi and install on you test box with an agent install so you get the software name in you software inventory. Then upload the msi file to server.


Then use the following commands to install:

via Kscript or Manage Install

msiexec.exe /i Teams_windows_x64.msi ALLUSERS=1 OPTIONS="noAutoStart=true" /qn /norestart


 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ