Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
Expected behaviour of the (newish) MANAGED_UPDATE=1 MSI deployment parameter
The article https://support.1password.com/deploy-1password/?windows#msi-deployment-options
states:
and the https://releases.1password.com/windows/stable/ page states in the release notes for version 8.10.72:
But when I deploy the machine-wide (.msi) 1Password for Windows with the MANAGED_UPDATE=1 parameter specified, users are still prompted to update the application when new versions become available,
and they also have the ability to "Check for Updates".
I expected MANAGED_UPDATE=1 to stop both of these things from occurring and a recent https://www.reddit.com/r/1Password/comments/1k1dnsj/controlled_update_of_1password/ appears to support this assumption:
Am I missing something here?
1Password for Windows (1PfW) 8.11.0 installed with 8.11.2 available.
After overcoming an install string regression issue and sorting out rogue .msi files in the %LocalAppData%\1Password\ directory, I think the MANAGED_UPDATE=1 parameter is now working as intended.
The behaviour now - from the 1PfW main dialog, the "Check for Updates..." menu item is still enabled and launches the 1PfW "Settings" dialog "About" pane, but available updates are no longer listed or generating update notification banners.I should also reference the related community discussion Disable 1Password Updates | 1Password Community, in case you're interested in the MANAGED_UPDATE related registry settings.
10 Replies
1Password for Windows (1PfW) 8.11.0 installed with 8.11.2 available.
After overcoming an install string regression issue and sorting out rogue .msi files in the %LocalAppData%\1Password\ directory, I think the MANAGED_UPDATE=1 parameter is now working as intended.
The behaviour now - from the 1PfW main dialog, the "Check for Updates..." menu item is still enabled and launches the 1PfW "Settings" dialog "About" pane, but available updates are no longer listed or generating update notification banners.I should also reference the related community discussion Disable 1Password Updates | 1Password Community, in case you're interested in the MANAGED_UPDATE related registry settings.
Having remnant .msi files in the %localappdata%\1Password\ directory appears to be responsible for the update notification banner, even when the latest release of 1Password for Windows (1PfW) is installed:
That said, I also see that 1PfW (at least 8.11.0) appears to do a good job of deleting older/current .msi files from this directory.
8.11.0 has now been widely deployed. I'll keep monitoring.
Just deployed 8.10.82 to clients. Let's see how it handles the next 1Password for Windows update. I did notice on the first launch (post install) of 8.10.82, that the application was still flagging the update to 8.10.82. What's with that?
Diagnostics sent to mailto:support@1password.com.
Support ticket ID is HWF-93255-152From my point of view, the MANAGED_UPDATE=1 MSI deployment parameter is still not working as intended.
The %localappdata%\1Password folder was preserved in between installs, but it was empty of msi files before version 8.11.0 was released. When 8.11.0 was released the file 1PasswordSetup-8.11.0.msi automatically appeared in the folder (no user checking for updates were requested from the application).
The check for and download of the latest version, 8.11.0, appears to have been triggered by the launch of 1Password for Windows 8.10.82.1Password for Windows 8.10.82 is, of course, displaying:
And “Check for Updates…”:
Version 8.10.82 was Intune deployed with the command line:msiexec /i 1PasswordSetup-latest.msi MANAGED_INSTALL=1 MANAGED_UPDATE=1 REBOOT=ReallySuppress /qn /l*v %TEMP%\1PasswordSetup81082_msi_install.logYes, the %localappdata%\1Password folder would have been preserved between the installations. No .msi in the folder at the moment but I'll monitor that folder when we deploy the next version of 1Password for Windows. Thanks.
TimG1PModerator
Would the %localappdata%\1Password folder happened to have been preserved in between installs? It sounds like the app may be finding the installer downloaded by the previous instance. Deleting the .MSI file downloaded to that folder will prevent this toast from appearing moving forward.
If the issue persists, I'd like to ask you to create a diagnostics report from your Windows PC so that the team can review logs and determine whether the flags are being applied:
Send a diagnostics report (Windows)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:- A link to this thread: https://www.1password.community/discussions/1password-work/expected-behaviour-of-the-newish-managed-update1-msi-deployment-parameter/157697
- Your forum username: TSC-Dean
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
Nope. 8.10.82 released and 8.10.80 installed with the MANAGED_UPDATE=1 parameter configured and still:
Thanks for the quick response. We only upgraded from 8.10.76 to 8.10.80 yesterday. I'll monitor the upgrade notification behaviour when the next version becomes available. That said, the "Check for Updates" option is still visible and operational with 8.10.80 installed with MANAGED_UPDATE=1 specified.
