/build/static/layout/Breadcrumb_cap_w.png

MS TEAMS deployment issues

Hello Ninjas

I probably should have started with microsoft forums but I wanted to start with you instead , you are more friendlier and responsive. 


Here is the problem. I reilized my kace script to deploy MS Team app , stopped working. I do not know what the problem is, 

Even after updating kace sma to 12.1 didn't help. 

I am using windows 10 pro 21H2 build # 19044.2006

I downloaded the machine wide installer version 1.5.0.21668


I can see teams from "apps & features" window. However, when I sign in to windows, teams app won't automatically show up. Also when I search "team" in the start menu it is not there. 

any ideas? 


scripting and managed installations options have the same result as I described above.


0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
Posted by: Mashby1 2 months ago
Purple Belt
0

Are you using a machine wide installer? What version of office are you using (ie. 365 pro plus....or...)? Can we see the script you are using?
Problem could be in a couple places and this info may help narrow it down.

Posted by: jencam 2 months ago
Orange Belt
0

yes I am using machine wide installer,

there is no ms office installed on the computers and they are using office 365

Here is the command (script) msiexec.exe /i teams_windows_x64.msi ALLUSERS=1 /quiet /norestart

I run this from cmd.exe (as admin) command runs without an error and I can see the ms team machine-wide installer exists in the apps list. 

However, it is not in the start menu nor auto starts when the user logs in.


Comments:
  • I have had success with uploading the office installers as a zip (attach to a matching software record that existed) and using:
    msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true" ALLUSERS=1
    in a managed installation that I associated with that software record with the zip.

    I have also done this as a post installation task on SDA using only the teams installer or doing all of the o365 suite. I wonder, if the difference in syntax would make a difference? If it is on the machine, it may be installing for the admin running the task not the user you are logged in as (ignoring your args) and that is why it won't show up for them. Just taking a guess here. - Mashby1 2 months ago
    • Thanks for the answer. Will try. - jencam 2 months ago
Posted by: glen.craig 2 months ago
Senior White Belt
0

The machine installer is I believe the better option for wide scale deployment, even if MS points you to the user install. No End user likes being told to now go and install apps for themselves. However, a couple of things to also take into consideration. There is now simple way to update the machine installer, as MS in their infinite wisdom leave the MSI Code the same from one version to the other (there is a Powershell script I found online to resolve that) and you will want to ensure you keep that updated if as without it new features do not unlock. also make sure you use 'ALLUSERS' and not 'ALLUSER' as this is for VDIs only.

Also if you have used or had the User based install on endpoints prior to going to the machine installer, the removal/uninstallation of this will write a registry key to your endpoints that stop the machine installer from running as a user logs into to create the user instance

HKCU:\SOFTWARE\Microsoft\Office\Teams "PreventInstallationFromMsi"


msiexec /i "Teams_windows_x64.msi" ALLUSERS=1

Posted by: jcaine 2 months ago
Senior White Belt
0

Top Answer

So we install Teams a little differently here.  We install it using the Teams Machine Wide Installer MSI file and have it so that it does not auto start until after the end user runs it for the first time.  Subsequent login's will have Teams auto run on login. 

 

1.  Install the MSI using the command:   msiexec.exe /i Teams_windows_x64.msi OPTIONS="noAutoStart=true" /qn

2.  Copy a pre-made shortcut for Teams to the Startup folder location

3.  Copy a pre-made shortcut for Teams to the Public Desktop location


For step 2 the shortcut Target is:  "C:\Program Files (x86)\Teams Installer\Teams.exe" --checkInstall --source=default and the Start in is:  "C:\Program Files (x86)\Teams Installer"

- This one will check for the existence of the Machine Wide Installer and if so run it so that it creates the Teams install within the current user's profile.


For step 3 the shortcut Target is:  C:\Users\%USERPROFILE%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe" and the Start in is:  C:\Users\%USERPROFILE%\AppData\Local\Microsoft\Teams

- This will place a shortcut on the desktop to the Teams install located in the user's profile that was created in step 2 above.  So the end user will execute Teams for the first time from the desktop using that shortcut.  


I then add those steps to a batch file.   


I then zip up the two Team's shortcuts, the MSI file and the batch file and add it to the software inventory record.  

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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