Appendix A:  Upgrading from NLES version 4.6.x

 

If you are upgrading from NotifyLink Enterprise Server version 4.6.x, please be aware of the following:

 

1.  DO NOT use the “Install All 3 Components“ button on the installer’s launch page for upgrades.

2.  Due to IT Policy reconfiguration, Administrative Login Levels may need edited after an upgrade to NLES 4.7.  In an upgrade to 4.7, new permissions will be added to any existing Administrative Login Level (including Full Access).  The new permissions default to a READ ONLY status.
If you want an Admin Level to have WRITE status (editing capabilities), you must edit the levels once your 4.7 upgrade is completed.  The new permissions are: Edit SMTP Servers, Emergency Calling Rules, and General Security Settings

      Select Server Administration > Administrative Logins > Edit Admin Levels > (choose an Admin Level) > Edit Level

      Check the Write box for the following permissions if you wish to grant write status.

 

Located under Server Administration

 

Located under Edit IT Policies
and User IT Policies

 

Located under Edit IT Policies
and User IT Policies

 

3.  Database re-encryption will occur on some systems.  With the application of the NLES 4.7.0 upgrade, the existing NLES SQL database may be re-encrypted using a more stringent 256 bit encryption key size.

Re-encryption will take place only if:

The version of NLES originally installed was less than 4.6.0 and

You are now upgrading from 4.6.0 or less

The installer will detect a system requiring re-encryption and will display a dialog informing you that it is necessary. 

 

4.  Upgrades requiring re-encryption will take longer.  Test scenarios, on a machine with a Quad Core Xeon Pro X3210 processor and 4GB memory, revealed that approximately 45,000 SyncMLCheckpoint and Attachment records were re-encrypted per hour.  Schedule sufficient downtime for your upgrade so as to avoid having to interrupt the database upgrade.  Canceling or stopping the upgrade would require you to restore from a backup before beginning again.

 

5.  Database re-encryption will require temporary space in the database transaction log.  Prior to a 4.7 upgrade, verify that the log size is at least 4GB and that there is sufficient free hard drive space to accommodate this.  Also, verify that the recovery mode is set to “Simple.”  See the Database Maintenance Guide for instructions.

 

6.  The NotifyLink installer will detect a system requiring re-encryption and will display the dialog shown in Figure 1 during the upgrade.  On a live system, actual record counts will display allowing you to calculate an approximate time required for the database re-encryption. 

Figure 1

 

For upgrades on systems still accommodating users on PIM server types that are no longer supported. 

The NotifyLink installer detects and reports users with PIM server assignments that do not meet the requirements.  The dialog shown in Figure 2 displays the log where this information can be found.  Administrators may reassign these users or remove them from the NotifyLink system prior to the upgrade.  See Appendix B.

Figure 2