Forum Discussion

TSC-Dean's avatar
TSC-Dean
New Contributor
11 months ago
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 ve...
discussion
windows
  • TSC-Dean's avatar
    TSC-Dean
    9 months ago

    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.

TSC-Dean's avatar
TSC-Dean
New Contributor
10 months ago

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?


 

  • TSC-Dean's avatar
    TSC-Dean
    New Contributor
    9 months ago

    Diagnostics sent to mailto:support@1password.com.
    Support ticket ID is HWF-93255-152

    From 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.log

     

  • TSC-Dean's avatar
    TSC-Dean
    New Contributor
    10 months ago

    Yes, 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.

  • TimG1P's avatar
    TimG1P
    Icon for Moderator rankModerator
    10 months ago

    TSC-Dean​ 

    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!