#365 BUSINESS STANDARD OFFLINE INSTALLER INSTALL#

#365 BUSINESS STANDARD OFFLINE INSTALLER INSTALL#

At the time, I had to roll my own registry hack to make it install for everyone on the machine. There also wasn't a Teams Machine-Wide installer back then. I built the original Landesk/SCCM 365 rollout package for my last company way back in 2016 or so, and at the time, Teams wasn't even built into the Office installer. It just needs the user to log out and back in before Teams shows up. In practice, occasionally even this fails and the user has to run the installer manually, but usually it works. Teams doesn't show up until the next time the user logs in. After the next login, you should see a second line item in A/RP for Microsoft Teams. The result of this is that after a new O365 installation, You should see a Teams machine-wide installer in Add/Remove Programs. The way it accomplishes this is that the Teams machine-wide installer places an ActiveSetup registry key that's designed to run the user context installer once per each user the first time they login. It can't actually be installed machine-wide it has to be installed into each user's profile. Now, the problem is that Teams is user-specific. What's supposed to happen is that the Office install runs a Teams machine-wide installer MSI that places a Teams Machine Wide Installer in Add/Remove programs. Teams installs differently from the rest of Office. Have you restarted the machine after the installation?

365 business standard offline installer