Anyone here using the “Repair” section of the script?
If so, do you do it for every package?
Do you have a generalized standard method for repair?
Do you just re-run your installer again?
We haven’t used this yet at our organization, and I’m wondering if/how we should…
I haven’t used it much, but one example where I have used it is for Microsoft Teams Machine-Wide Installer. I don’t get that involved in day-to-day support issues, but I was told that users sometimes have to reinstall Teams to fix issues. As we use the “Machine-Wide Installer” and that triggers a per-user install of Teams, I have “Repair” do the following tasks:
Uninstall Teams from each user profile on the device
MSI uninstall of Team Machine-Wide
MSI Install of Teams Machine-Wide
And finally I launch Teams for the current logged on user, which I thought was a generous but a helpful step. Execute-processAsUser runs Teams from ProgramFilesX86, which triggers the per-user copy of Teams to install and open.
( I can’t remember why I didn’t use the MSI repair switch, instead of “uninstall then install”. There may have been a good reason - or not!)
( I can’t remember why I didn’t use the MSI repair switch, instead of “uninstall then install”. There may have been a good reason - or not!)
The MSI does not install Teams to the users’ profile. It just stages the installation files.
That’s why the MSI repair switch is useless for Teams. MS is using MSI as a glorified ZIP file.