tburke

I would like to request the option to silently install PasswordState so I can incorporate it into an automated deployment.  There used to be a PowerShell Script Clickstudio provided to make this happen in the past but sounds like it is no longer supported with the new MSI installer.  Once the unattended options are worked out and can be passed to the MSI installer, then it can easily  be added to a Chef cookbook, packaged up in a Chocolatey package, or any automated packaging system.  I rely on being able to quickly build out test environments to test new features of passwordstate.
 
Maybe a more futuristic request is to provide a VM appliance of the passwordstate that we can drop into our environment and wire back into our existing DB data....or maybe create a container version of the service would be cool.  This may already be in your roadmap for the product eventually but I'm seeing allot of our IT tooling starting to be available as containers options.  Just incase you got that crazy dev that wants to do that you should let them investigate that setup.  🙂

I would like to request the option to silently install PasswordState so I can incorporate it into an automated deployment.  There used to be a PowerShell Script Clickstudio provided to make this happen in the past but sounds like it is no longer supported with the new MSI installer.  Once the unattended options are worked out and can be passed to the MSI installer, then it can easily  be added to a Chef cookbook, packaged up in a Chocolatey package, or any automated packaging system.  I rely on being able to quickly build out test environments to test new features of passwordstate.
 
Maybe a more futuristic request is to provide a VM appliance of the passwordstate that we can drop into our environment and wire back into our existing DB data....or maybe create a container version of the service would be cool.  This may already be in your roadmap for the product eventually but I'm seeing allot of our IT tooling starting to be available as containers options.  Just incase you got that crazy dev that wants to do that you should let them investigate that setup.  🙂

Hi tburke,
 
Looking at your forum post again, we think we know what the issue is now. The old In-Place Upgrade method is no longer available, and as of build 9300 our upgrade feature has changed to streamline the process and improve security.  Please follow this new set of instructions to help you get upgraded to the latest build available: https://www.clickstudios.com.au/downloads/version9/Upgrade_Instructions.pdf
 
Before attempting the new upgrade process. Can you please delete the c:\inetpub\passwordstate\upgrades\upgradelog.txt if it exists?
 
The manual uprade method you tried is also no longer supported, because of the way we "can" make changes to the web.config file during the upgrade process. In your web.config file, can you look for the reference to the CodePages above, and change it to the values below:
 
<dependentAssembly>
        <assemblyIdentity name="System.Text.Encoding.CodePages" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.0.0.0" />
      </dependentAssembly>

Regards
Click Studios

Hi tburke,
 
Yes, as of build 9300, there is no option in the UI to do In-Place Upgrades. You need to use the Windows Installer for this.
 
And that's correct, we no longer provide an unattended install option for our software, as we need to use the Windows Installer now - we no longre provide zip files with all the files, for security reasons.

Regards
Click Studios