1E 9.x (on-premises)

1

Ensure you have prerequisites ready for installation of the new version.

Review Known issues.

Determine if you will re-use the existing Web certificate or a new one. If re-using the certificate and upgrading from a version of prior to 5.0 then ensure you make a copy of the certificate files in the Switch SSL folder. If using a new certificate, then follow the guidance in Server Provisioning. If you are upgrading from 1E 5.x, the certificates will already be in the local Windows Computer Certificate Store so there is no need to backup.

If in doubt about your configuration, review each of the configurations in the 1E installation folder. A later step in this process asks you to make a backup copy of the installation folder. This allows you to review configuration settings and also retain a backup of the Switch certificate files.

1E recommends using the same server installation account as the original installation, but this is not mandatory provided the account is an existing 1E administrator user. You can check which is the original installation account by looking in the Permissions page and finding the user which does not have an edit or delete icon.

2

Inform 1E users when you plan to upgrade the system.

You should notify 1E users about the impending upgrade. This includes users of external consumers such as the extension described in Using 1E in Configuration Manager.

To help identify the users of the 1E system, you can review the 1E Permissions. You can also review the 1E Consumers in order to remind yourself of any 3rd party systems that will be affected by the upgrade.

Any instructions that are running or pending approval prior to the Platform and Agent upgrade will not be affected, other than be delayed by services being temporarily down.

3

Shutdown the existing 1E system.

If you want to keep any instruction responses, review the notes in the next step before shutting down the system.

Shutting down the system gracefully ensures there are no instructions in process and prevents access. The installer will internally shut down the services if you do not stop them manually. Stopping them manually gives you greater control over when they are stopped. The services will be restarted automatically after the upgrade.

4

Close all active connections to the 1E databases.

To avoid Known issues when upgrading, you must ensure there are no active connections to the databases.

You can use the following SQL script to identify which programs have active connections to the 1E databases.

SELECT DB_NAME(dbid) as [database], loginame, hostname, program_name
FROM sys.sysprocesses 
WHERE DB_NAME(dbid) LIKE 'Tachyon%' AND program_name LIKE 'Tachyon%'
ORDER BY DB_NAME(dbid), loginame, hostname, program_name;

With the 1E services stopped, any open connections to the database, such as 1E Consumer and 1E Portal, should not cause the upgrade to fail and can be safely ignored.

5

Backup the databases.

If you use 1E Setup to perform the upgrade, it backs up the following databases:

The following notes apply to the Responses database and whether you would need to create a backup of that database too:

6

Make a copy of the 1E Server installation folder.

The installation folder contains the following non-default files:

7

Install 1E Server.

Install 1E Server using the same configuration as before. Do not drop the databases.

Please refer to 1E Server Setup for more details.

8

Post-install tasks.

Repeat any 1E Server post-installation tasks that are relevant for an upgrade installation and are not performed automatically by 1E Setup.

9

Customizations.

Re-instate non-default settings.

10

Verify.

See Verifying page.