Updating and upgrading SystoLOCK is a straightforward and easy experience.
First, obtain the binaries from https://systola.com/downloads/systolock (protected resource) and copy the installation files to the respective computers. Update the server components first, then proceed with management tools, followed by Windows clients and other components.
Please note that starting with version 2.4, the management console will be "talking" to the server over a new TCP port 21573. All other components continue to use port 21572.
Older clients will work with newer servers and, if you run the recommended configuration of multiple SystoLOCK instances, you can proceed with rolling server upgrades without downtime for your users.
The server component needs to be uninstalled first and then installed again. The installer will save most settings needed to be preserved between these steps.
You will also need to uninstall Systola.SystoLock.AdcsSetup and Systola.SystoLock.Management packages as their funtionality is now fully covered by the serber installer.
|AD CS Setup scripts||Systola.SystoLock.AdcsSetup||MSI|
You will require Enterprise Admin privileges for update to succeed. Domain Admin privileges will suffice for some tasks, but may fail for other.
The client component can be installed manually by running the MSI package or can be distributed with software distribution systems with MSI packages. A reboot might be required after a client update.
You will require local administrator privileges for a manual update to succeed.
32-bit package is no longer distributed, but available upon request.
With an exception of the server component, all other installers can be run over existing installations and will correctly upgrade the respective components.
|AD FS Adapter||Systola.SystoLock.Adfs.Adapter||MSI|
|AD FS Identity Provider||Systola.SystoLock.Adfs.IdentityProvider||EXE|
|RD Web Access||Systola.SystoLock.Rds.Web||EXE|
|NPS RADIUS Plugin||Systola.SystoLock.NpsPlugin||MSI|
You will require domain administrator privileges for update to succeed for all packages, except MMC and NPS plugin, where you will only need local administrator privileges.