PGP Universal(TM) Server Version 2.10 Release Notes

Transcription

1 PGP Universal(TM) Server Version 2.10 Release Notes Thank you for using this PGP Corporation product. These Release Notes contain important information regarding this release of PGP Universal Server. PGP Corporation strongly recommends you read this entire document. PGP Corporation welcomes your comments and suggestions. Please use the information provided in Getting Assistance to contact us. Product: PGP Universal Server Version: Warning: Export of this software may be restricted by the U.S. government. Note: To view the most recent version of this document, please go to the PGP Support Portal and view the Knowledge Base article PGP User Guides, Administrator Guides, Quick Start Guides, and Release Notes. About PGP Universal Server PGP Universal Server provides your enterprise with secure messaging: it transparently protects your messages without user interaction. It automatically creates and maintains a Self-Managing Security Architecture (SMSA) by monitoring authenticated users and their traffic. You can also send protected messages to addresses that are not part of the SMSA. The PGP Universal Server encrypts, decrypts, signs, and verifies messages, providing strong security through policies you control. PGP Universal Server Satellite provides PGP security for messages all the way to the computer of the user, it allows external users to become part of the SMSA, and it gives end users the option to create and manage their keys on their own computer. Note to PGP Universal Server Technology Partner Edition users If you purchased PGP Universal Server Technology Partner Edition, many features described in the documentation are not available. If you want to upgrade to the full version of PGP Universal Server, please visit the PGP Web Site. To determine if you have this version, navigate to the System/System Settings screen. If you have this version, your license information includes the words PGP Universal Server Technology Partner Edition. Common Criteria Environments To be Common Criteria compliant, please refer to the best practices shown in PGP Universal Server 2.9 Common Criteria Supplemental. Note that these best practices supersede recommendations made elsewhere in this and other documentation. What's Included in This File About PGP Universal Server Changes in This Release System Requirements Upgrade/Migration Requirements Additional Information Getting Assistance Copyright and Trademarks Changes in This Release This section lists the changes and new features in PGP Universal Server in this release. What's New in PGP Universal Server 2.10 PGP Universal Web Messenger External Authentication. PGP Universal Web Messenger users can now enroll and log in using passwords stored on an existing authentication server. Administrators can specify an external authentication server on PGP Universal Server. LDAP and RADIUS are the supported authorization techniques. External authentication enables compliance for PGP Universal Web Messenger passwords with corporate password policies. Resolved Issues For a list of issues that have been resolved in this release, please go to the PGP Support Portal and view Knowledge Base article If you are distributing PGP Desktop MSI installer files using Microsoft Systems Management Server (SMS), the installer is distributed in the

2 correct language, without requiring a change in registry key. [7345, 9249] System Requirements PGP Universal Server is a customized Linux OS installation; it cannot be installed on a Windows server. Every PGP Universal Server requires a dedicated system that meets the system requirements listed below. The installation process deletes all data on the system and reconfigures it as a PGP Universal Server. PGP Universal Server Supported Hardware List - Valid 2/19/09 through 2/19/10 Please obtain the latest copy of this list for hardware purchasing decisions after 2/19/09. The following systems are supported for use as the hardware for PGP Universal Server: 1. Dell PowerEdge Dual Quad-Core Intel Xeon 2.50 GHz - 8 GB RAM - DVD-ROM Four 146 GB 15K SAS HD - PERC6/i RAID Redundant Power Supply (See the Additional Information section for more information on using PGP Universal Server with this system.) Note: This model requires an external network card to be compatible with PGP Universal Server. The default Broadcom NetExtreme II BCM5708 Gigabit Ethernet controller does not work with PGP Universal Server and is not supported. The following external network card is supported: Intel 10/100/1000 Dual/Quad port - Intel 82571EB Gigabit Ethernet controller Intel LAN Card: D Dell PowerEdge SC1435-2x Quad-Core AMD Opteron 1.9 GHz - 4 GB RAM 2 x 250 GB SATA Small/medium environment production unit 3. Dell PowerEdge Dual Core Intel Xeon 2.4 GHz - 1 GB RAM - DVD-ROM 80 GB SATA II 7200 RPM 4. IBM System x Quad-Core Intel Xeon E GB RAM 3 x 73 GB 15K RPM 3.5" Hot-Swap SAS - SeveRAID-8k 5. IBM BladeCenter HS21-2x Dual Core Intel Xeon GB RAM 2 x 146 GB 10K RPM SAS RAID LSI Logic 1064E Small/medium environment production unit (See the Additional Information section, Installing on IBM BladeCenter HS21, for more information on using PGP Universal Server with this system.) 6. SunFire Intel Xeon E GHz Quad-Core - 8 GB RAM - DVD-ROM 3 x 146 GB 10K 2.5" SAS Adaptec AAC-RAID 7. HP Proliant DL120 G5 - Dual Core Intel Xeon GHz 2 x 250 GB SATA Small/medium environment production unit Note: This model requires an external network card to be compatible with PGP Universal Server. The default Broadcom NC105i Gigabit adapter does not work with PGP Universal Server and is not supported. The following external network card is supported: HP NC360T PCI Express Dual Port Gigabit Server Adapter - Intel 82571EB Gigabit Ethernet controller 8. HP Proliant DL360 G5 - Quad Core Intel Xeon - 8 GB RAM - DVD-ROM 3 x 146 GB 10K RPM 2.5" Hot Swap SAS disk - Smart Array P400i RAID 9. HP ProLiant DL385 G2- Dual AMD Opteron 2216 HE Dual Core - 8 GB RAM - DVD-ROM Dual 72 GB 10K SAS Drives - RAID controllers: Smart Array P400, P600, and P800 Redundant Power Supply 10. HP Proliant BL460c - Single 3 GHz Quad Core Intel Xeon E GB RAM HP Blc300 Server Blade Enclosure and GbE2c Ethernet Blade Switch for HP c-class Dual 146 GB SAS HD - SmartArray E200i RAID Small/medium environment production unit

3 11. NEC Express Rj-2 - Dual 3 GHz Quad Core Intel Xeon GB RAM - DVD-ROM Disk Array Controller (Internal SAS HDD) 146 GB HDD x 3 (RAID 5) 12. VMWare ESX 3.0.2, 3.5, ESXi Supported platform, non-hardware. Sufficient processing power equivalent to a 3 GHz Intel Xeon must be dedicated to the PGP Universal VM. VMWare tools must be installed and configured inside the PGP Universal operating system. Disk space requirements: Small/medium environment - 50 GB minimum allocated to the VMWare instance; 4 GB RAM dedicated to the VMWare instance. Medium/large environment GB minimum allocated to the VMWare instance; 8 GB RAM dedicated to the VMWare instance. While a broad array of other hardware may work well with PGP Universal Server, incompatibilities related to hardware that is not one of the above systems will not be supported. Changing the sizes of hard disks within the same type of drive (for example, 36 GB SCSI to 73 GB SCSI), increasing memory configurations, and increasing processor speeds within the same type and family qualifies as the same system for Support purposes. PGP Universal Server minimum hardware requirements: Intel or AMD Processor 1 GB RAM, DVD/CD -ROM 80GB hard disk drive Mailserver Requirements PGP Universal is compatible with many mailservers. However, it is tested and supported on the most common mailservers. Mailservers not on this list may not be fully compatible or supported: Microsoft Exchange Server 2007 Microsoft Exchange Server 2003 SP2 Microsoft Exchange Server 2000 SP3 Lotus Domino Server Lotus Domino Server 6.5 Lotus Domino Server Stalker Communigate Note that in addition to Microsoft Exchange Server 5.5 not being a supported mailserver, it has known incompatibilities, including an incompatibility with the LDAP Directory Synchronization feature. Additionally, limited testing is performed with the following open-source mailservers: postfix 2.X sendmail 8.X uw-imapd 2002 and 2004 popa3d qpopper 4.0.X exim 3.36 and 4.X Cyrus PGP Corporation Compatibility Status with Microsoft Exchange Server 2007 PGP Corporation is pleased to announce compatibility with Microsoft's new Exchange Server PGP Desktop 9.6 introduced support for Microsoft Exchange Server 2007 and Microsoft Office When used with Internet-standard PGP/MIME (RFC 3156) messages, full message fidelity is preserved for all secured messages. With Exchange Server 2007, Microsoft has introduced a change in functionality that converts all messages to its internal MAPI format immediately upon processing, unlike previous versions of Exchange that supported the MIME standard for . Exchange Server 2007, when both sending and receiving via non-mapi clients, destroys MIME structures in . However, PGP/MIME-encoded messages are fully compatible with this Microsoft transition even when MAPI is not in use. All messages sent between PGP Corporation's MAPI clients are also fully compatible. Please note that messages encoded using the legacy "PGP Partitioned" format may not always display HTML message content properly, and foreign character sets in such messages may not reproduce correctly when processed through Exchange Server If such messages are processed from non-mapi clients, the server may delete some encrypted HTML body parts and remove non-ascii character set information, thus resulting in messages that do not preserve full fidelity. If your organization currently uses the legacy PGP Partitioned encoding with non- MAPI clients, PGP Corporation recommends not upgrading to Exchange Server 2007 at this time. PGP Corporation is working with Microsoft to seek additional solutions for compatibility between Exchange Server and the MIME standard.

4 PGP Corporation will update the Support Knowledge Base Article #713 as more information becomes available. PGP Universal Administrative Interface Web Browser Requirements Windows Mac OS X Internet Explorer 6 and greater Firefox 1.0 and greater Safari 1.0 and greater Firefox 1.0 and greater PGP Universal Web Messenger Web Browser Requirements Windows Mac OS X Internet Explorer 6 and greater Firefox 1.0 and greater Safari 1.0 and greater Firefox 1.0 and greater PGP Universal Satellite for Windows Requirements Microsoft Windows 2000 (Service Pack 4), Windows Server 2003 (Service Pack 1 and 2), Windows XP Professional 32-bit (Service Pack 2 or 3), Windows XP Professional 64-bit (Service Pack 2), Windows Vista (all 32-bit and 64-bit versions, including Service Pack 1), Windows XP Home Edition (Service Pack 2 or 3), Microsoft Windows XP Tablet PC Edition 2005 (requires attached keyboard). Note: The above operating systems are supported only when all of the latest hot fixes and security patches from Microsoft have been applied. PGP Whole Disk Encryption (WDE) is supported on client versions of Windows 2000 (Service Pack 4) and Windows XP (Service Pack 1, 2, or 3), and on Windows Vista; it is not supported on Windows 2000 Server or 2003 Server. 512 MB of RAM 64 MB hard disk space PGP Universal Satellite for Mac OS X Requirements Mac OS X 10.4.x or 10.5.x (Intel or PowerPC) 512 MB of RAM 64 MB hard disk space Supported LDAP Directory Products PGP Universal Server is compatible with the following LDAP directory products: Microsoft Active Directory 2008 Microsoft Active Directory 2003 Microsoft Active Directory 2000 Lotus Notes/Domino Directory 7.0 OpenLDAP 2.3.x Lotus Notes/Domino Directory 6.5 For directory synchronization, PGP Universal Server supports: LDAPv2 LDAPv3 LDAPS Anti-Virus Client Software Compatibility for Macintosh PGP Universal Server has no known issues with any Mac OS X anti-virus software packages. Anti-Virus Software Compatibility for Windows In all anti-virus programs, enabling real-time scanning detects any viruses as the or attachments are opened. Therefore, although it is recommended to disable scanning for some of the anti-virus products listed below, your is still being scanned and you are still being protected by your anti-virus product from viruses spread via .

5 Computer Associates etrust EZ-Antivirus 7.x Selective scanning is not compatible with PGP Universal Server. Computer Associates Internet Security Suite 2007 This product is incompatible with PGP Universal Server and should not be installed on the same system as PGP Universal Server. [12023] McAfee Internet Security Suite 2006, McAfee Internet Security Suite 2005, McAfee Internet Security 8.0, McAfee VirusScan 8.x through 10.x If scanning is enabled, the will not be processed by PGP Universal Server. Disable scanning in the McAfee product and enable real-time scanning. No additional special configuration requirements for MAPI . When using McAfee VirusScan Enterprise 8.0i, disable Prevent mass mailing worms from sending mail in the Access Protection Properties dialog box of the VirusScan console. If this option is enabled, SMTP will be blocked. To disable this option, right-click the McAfee icon in the System Tray and choose VirusScan Console. Double-click Access Protection. In the Access Protection dialog box, under Ports to block, deselect the box to Prevent mass mailing worms from sending mail (this option is enabled by default). McAfee Internet Security Suite 2006, McAfee Internet Security Suite 2005, McAfee Internet Security 8.0, McAfee VirusScan 8.x through 10.x If scanning is enabled, the will not be processed by PGP Universal Server. Disable scanning in the McAfee product and enable real-time scanning. No additional special configuration requirements for MAPI . When using McAfee VirusScan Enterprise 8.0i, disable Prevent mass mailing worms from sending mail in the Access Protection Properties dialog box of the VirusScan console. If this option is enabled, SMTP will be blocked. To disable this option, right-click the McAfee icon in the System Tray and choose VirusScan Console. Double-click Access Protection. In the Access Protection dialog box, under Ports to block, deselect the box to Prevent mass mailing worms from sending mail (this option is enabled by default). McAfee VirusScan 7.x No special configuration required. Panda Platinum 2005 Internet Security 9.x No special configuration required. Sophos Anti-Virus No special configuration required. Symantec Norton AntiVirus 11.x through 12.x, Symantec Norton Internet Security 2005, Symantec Norton Internet Security 2006 No special configuration required for MAPI . When using POP , enable Auto-Protect and disable the Anti-Spam and Scanning options. Auto-Protect, which is enabled by default, provides protection against viruses in messages when the message is opened. Disable SSL/TLS in Server Settings in PGP Desktop or PGP Universal Satellite. (In PGP Desktop, select the PGP Messaging Control Box and then choose Messaging > Edit Server Settings. For SSL/TLS, select Do Not Attempt. In PGP Universal Satellite, on the Policies tab, select Ignore SSL/TLS.) These versions of Norton AntiVirus prevent all mail clients from using SSL/TLS, regardless of the use of PGP software. Symantec Norton AntiVirus 9.x through 10.x, Symantec Norton Internet Security 2003, Symantec Norton Internet Security 2004 No special configuration required. Symantec Norton AntiVirus 8.x PGP Corporation does not recommend using PGP software with this version of Norton AntiVirus. PGP Corporation recommends that you upgrade to Norton AntiVirus version 10.x or later. [10419] Trend Micro Antivirus 12.x, Trend Micro PC-cillin Internet Security 2005 No special configuration required. Upgrade/Migration Requirements Before you upgrade to PGP Universal Server , you must back up your data. Restore the data after upgrade. You can migrate directly to PGP Universal Server version from any of the following previous versions:

6 Note: On PGP Universal Server , you can only restore backed-up data from version and later. To upgrade from a version of PGP Universal Server prior to 2.5.3: 1. Back up your version 2.0.x system data to an external location. (See the PGP Universal Administrator's Guide for installation and backup and restore instructions and best practices.) 2. Upgrade to version using the CD. Restore your backed-up data. 3. Back up your version data to an external location. 4. Upgrade to version using the CD. Restore your backed-up data. 5. Go to 6. One at a time, download and install PUP updates for versions 2.5.1, 2.5.2, and Note: You do not need to back up and restore data when upgrading using a PUP file. However, it is always a good idea to have a current backup when performing maintenance tasks on PGP Universal Server. Note: When installing multiple PUP updates, download and install them one at a time. If you download multiple PUP updates before you begin installing them, only the first installation succeeds. 7. Back up your version data to an external location. 8. Upgrade to version using the CD. 9. Restore your backed-up data. To upgrade from PGP Universal Server or 2.6.x: 1. Back up your data to an external location. 2. Upgrade to version using the CD. 3. Restore your backed-up data. To upgrade from PGP Universal Server 2.9.x (on a computer with Internet access): 1. Log in to PGP Universal Server administrative interface. 2. Select the System tab, and then click Updates. 3. Click Check for Updates and wait for the check to complete. This may take several minutes. If an available update is available, it appears in the list. 4. Click the Install icon, and then follow the on-screen instructions. Note: If you are upgrading from a version prior to 2.9.1, you must perform the procedure twice, first to upgrade to 2.9.1, and then again to upgrade to Note: You do not need to back up and restore data when upgrading using a PUP file. However, it is always a good idea to have a current backup when performing maintenance tasks on PGP Universal Server. Note: You must have a valid maintenance agreement with PGP Corporation to access PUP updates. For more information, see

7 To upgrade from PGP Universal Server 2.7.x, 2.8.x or 2.9.x (on a computer without Internet access): If you are upgrading to from 2.7.x, 2.8.x, or 2.9.x (on a computer without Internet access), then download the PUP file updates from the Licenses and Entitlement Manager System (LEMS) at If you don't have access to LEMS, request the update using a link in your order fulfillment . Note: If you are upgrading from a version prior to 2.9.1, you must perform the procedure twice, first to upgrade to 2.9.1, then again to upgrade to Note: For upgrades (from versions 2.7.x or 2.8.x) to take effect on computers with more than 4GB of RAM, you must manually restart them after the upgrade completes. Once you have downloaded (and extracted if necessary) the PUP update and copied it to the computer running PGP Universal Server: 1. Log in to PGP Universal Server administrative interface. 2. Select the System tab, and then click Updates. 3. Click Upload Update Package. 4. Click Browse, select the PUP update file, and then click Open. The update appears in the list. 5. Click the Install icon, and then follow the on-screen instructions. Note: You do not need to back up and restore data when upgrading using a PUP file. However, it is always a good idea to have a current backup when performing maintenance tasks on PGP Universal Server. Note: You must have a valid maintenance agreement with PGP Corporation to access PUP updates. For more information, see Upgrade Best Practices As a best practice, PGP Corporation recommends that you test your upgrade in a lab environment before changing your production environment: Perform a fresh install on a test system in a lab environment, or upgrade/migrate an existing lab system running a previous version of PGP Universal Server. Test the lab system to ensure that your mail policies and other basic functionality of your server work as you expect. Migrate your live environment. See the PGP Universal Server Upgrade Guide for upgrade/migration information. Additional Information Installation Restoring a backup of to a PGP Universal Server with a different IP address than the one stored in the backup does not change the IP address of the PGP Universal Server. [19918] When you back up data on one PGP Universal Server and then restore the data onto a different PGP Universal Server, MAC address information is incorrect. The MAC address on the restored PGP Universal Server is set to the MAC address of the backed-up PGP Universal Server. This cannot be fixed through the user interface. Contact PGP Support to correct the MAC address. [19895] Installing PGP Universal Server will reformat your disk, removing any existing operating system. Please do NOT insert the PGP Universal Server installation disk into any machine you do not intend on formatting for PGP Universal alone. [18616] After PUP updates, the screen is formatted incorrectly. Workaround: clear the cache or refresh the browser screen. [18011] If you are using PGP Universal on VMWare ESX with an attached SAN using an LSI controller, review this VMWare Knowledge Base article for best practices. [16047] When installing PGP Universal on a Dell PowerEdge 2950, ensure that you connect your Ethernet cable to the port "GB2," which corresponds to "eth0" as seen by the operating system. Otherwise, you may receive an error during installation. [10721] Do not use international characters when specifying file names for backup files. [10834] Deployment When a NIC is set to a custom link mode, rather than auto-negotiate, the network driver no longer advertises other link speeds. PGP Universal Server requires access to the list of possible link speeds to populate the Network Settings Link Speed menu. If you want to change the Link Speed from a custom setting, and no other custom settings appear, select Auto from the menu. Restart PGP Universal Server. After restart, the Link Speed menu is populated with all available options for the NIC. [19287] MAC ID, MTU, and Link Speed are not applicable to PGP Universal Server hosted on VMWare because the ESX server controls the network settings. However, when you create a new virtual interface, those settings are automatically populated. If your PGP Universal Server runs on VMWare and you want to create a new interface or edit an existing interface, you cannot save your changes until you clear the auto

8 populated MTU, MAC ID, and Link Speed settings. [19810] Organization Keys with Japanese passphrases cannot be imported. [18620] The Silent Enrollment option does not work with existing certificates or keys, including CAPI and token keys. [16044] You cannot use spaces in the name of the backup FTP server. [15491] Recovery from a Windows PE environment requires the use of a Whole Disk Recovery Token. TPM and hardware token users cannot be authenticated from within Windows PE. [15101] To replace an installation of PGP Desktop with embedded policy with an installation of PGP Desktop that retrieves policy from PGP Universal Server, you must first delete the PGP Corporation folder in %ALLUSERSPROFILE%\Application Data. If you do not delete this folder, your new PGP Desktop installation will not receive policy from the PGP Universal Server. [13252] PGP Keys The PGP Verified Directory is not searched for keys when verifying signatures by default. Workaround: Add the Universal Server's ldap directory using the hostname of the Universal server (e.g. keys.example.com:389) to the default keyserver list (Policy>Servers). [16325] Exporting or deleting tens of thousands of user keys at a time can take hours or fail. Export fewer keys at a time, or contact PGP Support for help. [15998] When making any changes that affect which TLS client certificates are permitted to access the Keyserver service, you must disable, and reenable the Keyserver service for these changes to take effect. [6533] PGP Messaging Adding text below a block of ciphertext in a message may cause PGP Universal mail policy to have errors when processing the message. [18536] When sending PDF Messenger messages to large groups of people at a time, for example mass statement delivery, limit the mailserver sending the Secure PDFs to PGP Universal Server to less than 100 recipients total in the To, CC, and Bcc fields, with a message size less than 6 MB. [17840] Sending concurrent PDF Messenger messages to large numbers of recipients is not recommended. Limit the number of concurrent recipients to 200 at a time. [17751] If a user's Thunderbird client is set to send in HTML-only format, and the message is encrypted by either PGP Universal Server or PGP Desktop before it arrives at the BES gateway, the recipient will be unable to view the message on his or her BlackBerry. To work around this issue, configure the Thunderbird client so that it does not send HTML-only messages. [16273] When a PDF Messenger message with a large attachment is sent out of the mail stream, the connection to the PGP Universal Server times out before the mail is sent. [15916] Microsoft Windows Mail in Windows Vista may incorrectly deliver the PGP Desktop enrollment message to the Junk folder, instead of to the Inbox. If using that client in a managed setting, please disable the Junk feature. [13149] Microsoft Outlook 2007 uses extensive processing time to handle extremely large HTML attachments. The connection with the PGP Universal Server may time out before the message can be sent. [12545] Characters added in versions of Unicode after 3.0 are not supported in PGP Universal Dictionaries. [10367] Some of the more obscure authentication methods for POP/IMAP/SMTP may not work through PGP Universal. We recommend always activating SSL/TLS between your client machines and PGP Universal. If you are also deploying PGP Universal Satellite internally, it will automatically probe for SSL/TLS on the server and upgrad connections to use it whenever possible. Plain, Login, MSN, NTLM, and CRAM- MD5 authentication are officially supported in this release. [NBN] Stalker's CommuniGate Pro mailserver contains a MAPI client adapter to redirect MAPI over IMAP. This adapter is not currently compatible with PGP Universal Satellite. [2430] PGP Universal Web Messenger PGP Universal Web Messenger passphrases authenticate to the Radius server even if the account port configured on the PGP universal Server is incorrect. [20130] PDF Messenger messages with very long subject lines cause errors. [17502] Text that appears in PGP Universal Web Messenger before the user logs in is not translated. Workaround: Perform a complete customization of the template From Services>Web Messenger, click Add Template, and choose Complete Customization. When you modify the template, leave the "Welcome to Web Messenger" string blank. Then replace the string in the HTML with the appropriate text (e.g., "Welcome to Web Messenger"). Next, in the five properties files, create a localization reference for each language. The string should then appear translated. Complete Customization requires expertise in HTML. [17177, 17179, 17181] Depending on your Microsoft Windows version, opening files with non-latin filenames directly from PGP Universal Web Messenger may result in garbled filenames. To avoid this problem, save attachments to your desktop before opening them. [12011] Replies to PGP Universal Web Messenger messages may not work if a load balancer is directing traffic for the untrusted interfaces of a cluster of PGP Universal Servers in gateway placement. A workaround is to disable any rules your hardware may enforce that prohibit traffic to a virtual server from a member of the load balancing pool. Check with your hardware vendor to determine if this is possible. [NBN] PGP Universal Web Messenger mailbox quotas of up to 2 GB are supported for this release. [7986] PGP Whole Disk Encryption In some cases, the PGP Whole Disk Encryption Admin Key does not unlock removable devices. Use the Whole Disk Recovery Token to

9 access data on the devices instead. [20406] Bad sector log entries in the Client log on the PGP Universal Server do not report the correct number of bad sectors, and may erroneously report 0. When no bad sectors are encountered, there are no log entries referring to bad sectors. [18105] The PGP Whole Disk Encryption "Force Encrypt" setting is not set and enforced correctly after upgrade. If you are using this option, review and verify your policy because you now have more settings you can choose. [17793] Changing the PGP Whole Disk Encryption BootGuard screen overwrites the previous image. It is not possible to go back to the default PGP Corporation image. [17459] The PGP Universal Server does not display encrypted device status on the Internal User Information screen for PGP Desktop prior to 9.7, and instead displays the "Unknown" status for all such devices. To see encrypted device status, you must upgrade the client to 9.7. [15606] PGP Universal Server does not validate images uploaded for use with PGP BootGuard. For more information on creating, uploading, and testing images, see Knowledge Base article 885. [15457] PGP Netshare Files protected by application-based encryption policy are locked (requiring authentication to access) after the user associated with the policy logs off or shuts down the system. [17491] Please see the PGP Universal Satellite Release Notes installed with PGP Universal Satellite for additional information. Installing on IBM BladeCenter HS21 Due to a known bug, you cannot use a physical CD-ROM to install PGP Universal Server on a blade in the IBM BladeCenter HS21. If you insert the PGP Universal Server installation CD into the IBM BladeCenter CD drive, a prompt appears, asking you to choose an installation method. This means the server cannot read the CD. To install PGP Universal Server on a blade, use virtual CD installation. 1. Save the PGP Universal Server installation file to your computer. 2. From your computer, open a browser to the browser-based management console for the Advanced Management Module of the IBM BladeCenter Chassis. The management console allows access to all the blades in the server. 3. Log in to the management console. The BladeCenter Advanced Management Module page appears. 4. Choose no timeout as the inactive session timeout value. 5. Click Start New Session. The System Status Summary page appears. 6. From the left side of the screen, click Blade Tasks>Remote Control. The Remote Control status page appears. 7. Click Start Remote Control. The Remote Control opens. There are two sections to the page, Remote Disk and Remote Console. 8. From the Remote Disk section, set Media Tray to None. 9. Select Chassis KVM Owner from the Mount Remote Media menu. 10. From Available Resources, select Select Image and click the right arrow. The Browse dialog appears. 11. Browse to find and select the installation image you saved to your computer. The installation image appears in the Selected Resources box. The image should be the only file in the box. 12. Click Mount All. 13. From the Remote Console section, select the blade from the KVM menu onto which you want to install PGP Universal Server. 14. Restart the blade. Make sure that the blade reboots from the virtual CD-ROM. 15. The installation screen appears. Follow the installation instructions as described in the PGP Universal Server Administrator's Guide. Note: During installation, enter IP and network information for the blade onto which you're installing PGP Universal Server, not the IP for the

10 chassis as a whole. Getting Assistance Available Documentation Documentation is available on the Documentation disc as well as from the PGP Universal administrative interface. Online Help is also available via the administrative interface for each screen. Prior to installation, complete Product Documentation is available through the PGP Support Knowledge Base. The PGP Universal Administrator's Guide (pgpuniversal.pdf) is an Adobe Acrobat Portable Document Format (PDF) file. You can view and print this file with Adobe Acrobat Reader, included on the Documentation disc and also available on the Adobe website. Documentation feedback is welcome. Send comments to [email protected] or visit the Documentation forum. Contacting Technical Support To learn about PGP support options and how to contact PGP Technical Support, please visit the PGP Corporation Support Home Page. To access the PGP Support Knowledge Base or request PGP Technical Support, please visit PGP Support Portal Web Site. Note that you may access portions of the PGP Support Knowledge Base without a support agreement; however, you must have a valid support agreement to request Technical Support. For any other contacts at PGP Corporation, please visit the PGP Contacts Page. For general information about PGP Corporation, please visit the PGP Web Site. To access the PGP Support forums, please visit PGP Support. These are user community support forums hosted by PGP Corporation. Copyright and Trademarks Copyright PGP Corporation. All Rights Reserved. "PGP", "Pretty Good Privacy", and the PGP logo are registered trademarks and PGP Universal is a trademark of PGP Corporation in the U.S. and other countries. All other registered and unregistered trademarks in this document are the sole property of their respective owners.