PGP Universal Server 3.0.1 - Resolved Issues


Article ID: 153726


Updated On:


Symantec Products


This article details a list of resolved issues in PGP Universal Server 3.0.1.



  • Significant improvements have been made to the performance of the PGP Universal Server in a number of important areas. [19863, 25985, 26922, 26997, 27034, 27035, 27062, 27206]
  • Fixed an issue that caused the server to become unresponsive to client requests, requiring services to be restarted. [26400]
  • Fixed a problem that allowed a redirect from the PGP Universal Server UI to a page outside the Universal Server, when using a browser with Javascript disabled. [27163]


  • Fixed a problem that caused the "expert" option of the PGP Universal Server Installation function to fail. [27235]
  • After a migration to PGP Universal Server 3.0, a misleading error message regarding failure to request customized PGP Whole Disk Encryption BootGuard settings would be logged for new enrolling clients. This no longer occurs. [26474]
  • After a migration to PGP Universal Server 3.0.1, excluded users are correctly included in the Everyone group in the Administrative Console. [26535]
  • After a migration to PGP Universal Server 3.0.1, consumers that are members of groups that do not have an associated consumer policy are now correctly displayed. [26547]
  • After a migration to PGP Universal Server 3.0, SCKM keys are now displayed correctly, rather than being shown as SKM keys. [26557]

PGP Universal Server Administration

  • The administrator interface now indicates (at admin login) when the number of user licenses has been exceeded. [26768]

LDAP Directory Synchronization

  • When searching for a consumer in all ordered LDAP directories, and the consumer is not found in the first searched directory, the search now continues to the other ordered directories, even when LDAP referrals are enabled. [25975]
  • PGP Universal Server now correctly follows LDAP referrals for directory synchronization. [26107]
  • Fixed a problem that could cause client connections using LDAP authentication to deadlock. [27262]
  • A user's Lotus Notes ID is no longer removed when an LDAP synchronization occurs. [26740]


  • Fixed an issue that caused periodic mail gateway crashes. [25362]
  • In some instances, after a migration to PGP Universal Server 3.0, an error was raised when modifying or adding custom policies. This has been fixed. [26681]

Keys and Certificates

  • Certificates associated with SCKM signing subkeys for S/MIME users are now properly renewed upon expiration. [26555]

PDF Messenger

  • Emails sent through PDF Messenger that contain already encrypted PDF documents in addition to other attachments, are now properly encrypted without requiring selection of the "Encrypt body text and all attachments" option for the PDF Messenger action. [26230]


  • The performance of a query for a large data set, such as for all WDE computers, has been improved. However, if a query still takes too long, it will now time out with an error: "An unexpected error has occurred. Please check the logs for details." [27705]


  • Client connections were timing out, causing error messages to fill the error log. These connections no longer time out under normal circumstances. [26889]
  • Fixed a problem that caused duplicate WDE alerts to appear unnecessarily. [27576]


  • Significant improvements have been made to PGP Universal Server clustering to enable support for migration of clusters in "Home Server" mode and for large numbers of internal and external users. Performance has been significantly improved as well. [23694, 25966, 26193, 26480, 26510, 26710, 26713, 26728, 26784, 26826, 26849, 26855, 26857, 26859, 26860, 26894, 26895, 26901, 26935, 26977, 26985, 27010, 27014, 27123, 27185, 27197, 27238, 27259, 27404, 27478, 27582, 27644, 27706 ]
  • In some instances, cluster nodes designated as a DMZ nodes without private keys could not be correctly backed up and restored. This has been fixed. [26585]
  • Use of a secondary NIC for cluster communication is now supported. [27007]
  • The hosting of private keys on cluster members that are internal nodes cannot be disabled. Private key hosting can only be disabled on cluster members that are located in the DMZ. [27411]