mirror of
https://github.com/Installomator/Installomator.git
synced 2026-03-02 08:52:07 +00:00
New Microsoft Teams is not completely shutting down to update #206
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sean-enright on GitHub.
The users keep receiving these prompts until they manually shut down Teams. then it finally completes.
Possibly a change in the New Teams, everything worked like a charm up until this past week.
@PeterPlanlos commented on GitHub:
also I observed that the update wants to install on every run. means the currentversion seems not readable or it searches for a wrong *app
Microsoft Teams (ork or school).app
currently its just
Microsoft Teams.app
@tully-systima commented on GitHub:
Script used:
MDM/App-update/App normal Auto-install.shVersion: 10.6
variables set:
appPath="/Applications/Microsoft Teams.app"installomatorOptions="BLOCKING_PROCESS_ACTION=ignore"Returned results:
Notice how the returned results prior to line 7 state
microsoftteamsnew succesfully installedI'm assuming that this is the
msupdatetool logs being returned here, andmsupdatehas correctly identified and installed the update forTEAMS21However, after
msupdatehas done its thing, then the installomator script starts, statesWARN : microsoftteamsnew : No previous app found, as the installomator script is now looking forMicrosoft Teams (work or school).app. I would also posit that if the msupdate tool has correctly run any available updates for the label stated, then it should not then need to run the installomator script segment at all.I am working on a fix for this fragment that will only run the installomator section of the script if msupdate is either not present or not working correctly, unfortunately Microsoft do not list the Teams2 versioning information on a git, its only listed on a Microsoft help page that has to be manually updated by hand.
Additionally, I believe that we may need to move away from using the macadmins.software xml file, I was advised that the person who was updating this is no longer able to keep it updated, the most recent update to that file was in December 2023.
@tully-systima commented on GitHub:
Yeah I'm having the same problem... Had to make a manual interception and fix in my main installomator script to specifically set the itemName to "Microsoft Teams"
@csfjeff commented on GitHub:
We're seeing these issues as well - 3 separate but related issues best I can tell:
I've tweaked a custom version of installomater changing the name and that seems to be running ok in spite of the logs noting the newest version is older than the installed version.
@PeterPlanlos commented on GitHub:
In current release
line 5924
needs to be updated to:
name="Microsoft Teams"
from name="Microsoft Teams (work or school)"
please could someone fix this asap?
Thank you very much
@JJSaysNay commented on GitHub:
This is still an issue in the newest version.