Reboot Required for After Updating Symantec Encryption Server or PGP Universal Server with PUP Files
|Article:TECH184430|||||Created: 2012-03-21|||||Updated: 2013-03-13|||||Article URL http://www.symantec.com/docs/TECH184430|
After installing an update to Symantec PGP Universal Server using a PUP file, a reboot is required to complete the update.
PGP Universal Server is now called Symantec Encryption Management Server (SEMS) starting with version 3.3.
Since some PUP files contain kernel updates, it is necessary to reboot Symantec PGP Universal Server (SEMS) after the installation has completed. When no kernel is included in the update, no reboot is required.
As kernel updates have been integrated into the PUP files of version 3.2.0 Build 1672 and version 3.2 MP4, an update to these versions require a reboot of the server to complete the installation.
Generally, if it is not possible to reboot the server, do not attempt to install a PUP file as an automatic reboot may be necessary.
As a best practice, when installing an update to Symantec PGP Universal Server, select a time when users will be the least impacted, the server may require a reboot, or in the unlikely event that the installation fails. Prior to installing an update or making significant changes to Symantec PGP Universal Server, it is recommended to perform a backup of the server.
Notable Symantec PGP Universal Server and kernel versions to help determine if a reboot is required after installation:
NOTE: (Different kernel versions denote a reboot is required)
|PGP Universal Server Version / SEMS||Linux Kernel Version|
|3.0.0 Build 2881 through 3.1.2 SP3 Build 50||2.6.18-128.4.1.el5PAE|
|3.2.0 Build 1672 through 3.2.0 MP3 Build 2317||2.6.18-194.26.1.el5PAE|
|3.2.0 MP4 Build 2526||2.6.18-274.12.1.el5PAE|
|3.2.0 MP5 Build 2599 through 3.2.1 MP3 4940||2.6.18-274.17.1.el5PAE|
|3.2.1 MP5 Build 5033||2.6.18-194.26.1.el5PAE|
|3.3.0 GA Build 8741 through 3.3.0 MP1 Build 9060||2.6.18-308.11.1.el5PAE|
Article URL http://www.symantec.com/docs/TECH184430