Login to Symantec Encryption Management Server via SSH (for more information on how to login to the server using SSH, see article TECH149673): Confirm the invalid data is no longer sent to the server.Ĭhecking to see if systems deployed in the environment are affected by this issue:ġ. Once the client is updated to Symantec Encryption Desktop 10.3.2, delete the invalid machines from the server, and then stop and restart the PGPtray services, then update policy. Although this issue was fixed in 10.3.0 MP3, in order to prevent the invalid machine data from being sent to the server, please update to the latest version of Symantec Drive Encryption 10.3.2. Please contact support in order to work out a resolution strategy and to correct this situation. As one of the symptoms of this issue is the invalid MACHINEGUID values, database cleanup will be needed. Symantec Encryption Desktop 10.3.0 MP3 and above correct this issue. "Error sending logging configuration data to the server: corrupt data (-11976)" "The administrative server is not available for storing the Whole Disk TIP: A normal MACHINEGUID value, or Machine ID\Device ID value does not start with "00000003" or "00000002", and looks similar to the following example:Īn example of this invalid data can be seen in the following screenshot where there are multiple Blank hostname Computers listed:Īlthough the screenshot does not display the "00000003" value, upon clicking a blank hostname, this value can then be seen. Machine ID values for machines will appear abnormal, such as the following samples:.Duplicate hostname data, including duplicate blank hostnames sent to the server.
Blank hostname data sent to the server.Garbled hostname information associated to the server.See article TECH214364 for more information on including Symantec Encryption Desktop in a system image.Įxamples of this invalid data include the following: Symantec Encryption Desktop 10.3.2 introduced the ability to include PGP in a Corporate image, and so the MACHINEGUID value was changed to generate during enrollment.This is why PGP could not be included in a system image as this would assign the same MACHINEGUID value to each system the image is deployed to. On Symantec Encryption Desktop before 10.3.2, this unique MACHINEGUID value is created during installation.This value needs to be a unique identifier for each computer and if the value is either missing or malformed, invalid data can then be sent to the Symantec Encryption Management Server. This is a unique value generated by the client to identify the Device ID with the Symantec Encryption Management Server (previously PGP Universal Server). Symantec Encryption Desktop (previously PGP Desktop) includes a registry value called MACHINEGUID.
0 kommentar(er)
