Custom Keyservers are not replicated across cluster members for Symantec Encryption Management Server 3.3.2 and above
Due to a design change in Symantec Encryption Management Server 3.3.2 the replication of Keyservers was removed. This can cause the mail policy to reference a nonexistent Keyserver and run into an exception with the following error: "451 Symantec Encryption Server: Error while processing"
In Symantec Encryption Management Server 3.4.1 MP1, this issue is resolved. The custom keyservers are now replicated across all the clustered servers.
NOTE: When upgrading your server from version 3.3.2 or later to 3.4.1 and you had manually added the custom keyservers to the cluster members, duplicate custom keyserver entries will appear. Ensure that you perform the following steps after upgrade if you had manually added the custom keyservers:
1. On the cluster members where you originally manually added keyserver entries, manually delete them. 2. Manually add the custom keyserver entry only on the sponsor node. This keyserver entry is replicated on all the cluster members.
If duplicate keyserver entries appear post upgrade, remove the duplicate entries.
Subscribing will provide email updates when this Article is updated. Login is required.