![]() Today I started working on a script to push out the new version only to find out that when we run: This will not install for all users as it requires elevated credentials which end users do not have. We are now starting to get users who log into PC's for the first time and get prompted about not being a updated version and click here to update, which takes them to a download link for Teams. We've only just noticed now, that despite us pushing out version 64 in the initial rollout, the end users were only receiving the updated Teams to their local profiles, so the initial installer is never updated due to being in a locked down environment. The deployment was disappointing to begin with, in that all the installer does is create a Teams Installer directory under program files and then copies the installer (approx 100mb) to every single logged in user, which chews up the hard disk for multi user devices). We pushed out the Microsoft Teams Machine-wide installer to 1,500 PC's in our organization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |