WAU MSI Repair CLI

[LastElf]

I've been wracking my brain over this for the last two afternoons and I can't seem to find the switch in the MSI to perform a working full repair.

Background: I'm updating WAU for my MSP from v1 to v2. We manage it via a deployment Powershell script which pulls down the installer, passes some variables from our RMM into the script and then just monitors it for any RMM config changes. If it detects the time or blacklist changes then it re-deploys over the top and everything just updates.

I have the above process working for the v2 MSI for a clean install. I can even perform a repair to change the update time if I go through it interactively, but if I try and run msiexec.exe /fpocmus <path> UPDATESATTIME=<new_time> /qn it appears to process as normal, but the schedule time doesn't change, where it does if I click through the installer and click Repair with the same properties set.

I could probably just do an if installed then uninstall and then run the installer as normal, since that's what a full repair does anyway, but am I going to lose logs that way? I did go through the MSI with Orca trying to work out if there's a hidden flag that isn't documented and I saw some protected WIX stuff but nothing that seems to be accessible in the actual process steps besides an Installed check.

And before you ask, this covers many customers with different environments, ADMX management isn't a route that we want to go down at this time and we're trying to stick to RMM managed as we had for v1. I would love to centrally manage it like that but MSP can be scared of change (And time wasted spent doing reconfig of something we offer under contract).

[KnifMelti]

msiexec.exe /fpocmus <path> UPDATESATTIME=<new_time> /qn it appears to process as normal, but the schedule time doesn't change, where it does if I click through the installer and click Repair with the same properties set.

Hello!
I can confirm this behavior, and I think it has with the custom actions to do (@Romanitho?).
This managing of the task is done in WAU-MSI_Actions.ps1 via CA_PowerShell_Install/SetCA_PowerShell_Install.

But either way (reparing/uninstall/install) you're not going to lose any logs.
You lose the black/white list and the mods (reverted to original installation)

[LastElf]

Thanks for the info. Can confirm logs don't clear, they're just not in ProgramData like v1 was and I was fixated on the repair part of the process; no issue there I'll just update the docco for my techs.

With that, I'm just going to add uninstall v1/v2 lines to my install script and leave it at that. Bit more complex but probably more reliable. Blacklist isn't an issue since the install part of the script pulls that dynamically from the RMM on script deploy anyway so that will work as intended, I just wanted to make sure I wasn't doing something wrong with the CLI msirepair since manual worked fine. v1 we could just run the install over the top and it would update, MSI is a bit pickier.