Deploy 1Password for Mac and Windows

Deploy 1Password for Mac

Step 1: Plan your deployment

Determine which installer is best for your use case:

• If you need automatic app updates, download the 1Password.app installer.
• If you want your IT team to manage app updates, download the 1Password.pkg installer.

Step 2: Deploy 1Password

1Password must be installed in the /Applications folder to work properly. Don’t install the app in the user ~/Applications folder.

If your deployment tool requests a bundle identifier, enter com.1password.1password. If it also requests a group identifier, enter 2BUA8C4S2C.com.1password.

Step 3: Monitor for updates

Subscribe to the RSS feed to keep track of 1Password for Mac updates. To install updates, follow the guidelines for the installer you used:

• 1Password.app: Replace the installer at least every 6 months.
• 1Password.pkg: Replace the installer at least every month.

Deploy 1Password in a virtualized environment

If you deploy 1Password for Mac to a virtualized environment, you’ll need to make sure local data for the 1Password app is preserved between sessions. This will allow your users to unlock 1Password without entering their Secret Key or repeating the steps to set up a linked app or browser every time they’re provisioned to a new virtual machine.

Local data for 1Password is stored in this folder:

~/Library/Group\ Containers/2BUA8C4S2C.com.1password/Library/Application\ Support/1Password

To make sure your users can save and fill passwords in their browser, deploy 1Password in the browser for your team. The 1Password app also needs to be installed with the local data folder preserved between sessions.

Deploy 1Password for Windows

Step 1: Plan your deployment

Determine which installer is best for your use case:

Step 2: Deploy 1Password

Follow the steps in your deployment software to deploy the installer you downloaded in step 1. For example, to deploy 1Password on a per-user basis with Intune, prepare a .intunewin file then add and assign the app.

Step 3: Monitor for updates

Subscribe to the RSS feed to keep track of updates to 1Password for Windows. To install updates, follow the guidelines for the installer you used:

• .exe: Replace the installer at least every 6 months.
• .msi: Replace the package at least every month.

MSI deployment options

You can specify different options when you deploy the 1Password MSI:

• /norestart: Include this parameter to prevent team member’s PCs from restarting automatically to complete the installation of 1Password.
• MANAGED_UPDATE: Set this property to 1 to turn off the option for team members to update 1Password themselves.
• MANAGED_INSTALL: Set this property to 1 to have other installations of the 1Password app automatically removed if they exist on a team member’s PC.

  Installations of 1Password 7 or earlier won’t be affected.

Deploy 1Password in a virtualized environment

If you deploy 1Password for Windows to a virtualized environment, such as VMWare Horizon, you’ll need to make sure local data for the 1Password app is preserved between sessions. This will allow your users to unlock 1Password without entering their Secret Key or repeating the steps to set up a linked app or browser every time they’re provisioned to a new virtual machine.

Local data for 1Password is stored in this folder:

%LocalAppData%\1Password

To make sure your users can save and fill passwords in their browser, deploy 1Password in the browser for your team. The 1Password app also needs to be installed with the local data folder preserved between sessions.