1Password silent installation

spitf1r3

Hi,

I'm installing 1Password silently, which is:
msiexec.exe /i "AgileBits.OnePassword.Desktop.msi" REBOOT=ReallySuppress /QB-! TARGETDIR="C:\Program Files (x86)\AgileBits\1Password" /L*v "C:\WINDOWS\Logs\Software\AgileBits.OnePassword.Desktop_Install.log"

and I currently have 2 issues with it:

1. It wipes data on every upgrade (I have to sign in each time after I update 1Password) - is it normal?

2. It starts 1Password after installation - any way (like an MSI parameter) to prevent it?
   I have looked though the MSI with Orca, and found nothing that could help me.

---

1Password Version: 6.0.214
Extension Version: Not Provided
OS Version: Windows 10 x64
Sync Type: 1Password for Family

MikeT

Hi @spitf1r3,

Have you tried installing it normally without the parameters to see if it is working better?

It wipes data on every upgrade (I have to sign in each time after I update 1Password) - is it normal?

No, that's absolutely not normal. It sounds like it is not retaining the previous database directory. By default, it is using this path: %LOCALAPPDATA%\1Password\data\. In this case, it is likely not wiping out data but creating a new database file for you.

Unfortunately, the MSI installer we're using has a few issues and we're working on a custom MSI installer to see if we can do better. Right now, it does not retain customized TARGETDIR, so it will install the upgrades to your %LOCALAPPDATA%\1Password directory each time. Can you check to see if you see both app and data directories inside that local app directory?

spitf1r3

Looks like it is retaining the data directory %LOCALAPPDATA%\1Password\data\, but deletes %LOCALAPPDATA%\1Password\data\1password10.sqlite during the installation (leaves %LOCALAPPDATA%\1Password\data\1password10.cache.sqlite alone, though). I'm using TARGETDIR every time, so it doesn't need to remember the last installation directory to retain it.

What about preventing 1Password from starting after installation? I'm using PowerShell App Deployment Toolkit for the installation script, and it's ability to prevent from starting the application that is being installed - the unnecessary startup is just annoying - it would be nice to have an option to disable it (like many other apps doing the same thing have).

MikeT

Hi @spitf1r3,

That is strange because our MSI file doesn't deal with the DB files, only our app will manage it and there is no delete rule either, we only create a new one once it detects there is no existing db file. Are you using any system tools that cleans up files for you?

Right now, 1Password 6 Beta is not tuned for MSI customization nor settings like that, it's not something that's high on our list to focus until we finish the app first. We recommend that you stick with the default install method and wait until we finish our custom MSI installer that might work better.

spitf1r3

Nope - I'm not messing with any files at all.
All my script does is:
Runs MSI with said parameters
Prevents 1Password executable from running during the installation

I can send you the log file (as it creates one using MSI /l*v), but I'd rather not do it publicly.

mohamedosman

Hey @spitf1r3 can you send the logs over so I can have a look, there may by a couple different things at play that are causing this. You can send an email to support+windows@agilebits.com. Also, in the email, include the link to this thread along with your forum username, so that we can connect the email to this thread.

Let us know here when you've sent it, so we can confirm we got the email.

spitf1r3

@mohamedosman just sent an e-mail with the log file. Thanks!

mohamedosman

Got it, thanks @spitf1r3, we'll continue the conversation there :).

ref: CJH-94594-488