Symantec Encryption Desktop 10.3.0 MP3 and above correct this issue. As one of the symptoms of this issue is the invalid MACHINEGUID values, database cleanup will be needed. Please contact support in order to work out a resolution strategy and to correct this situation. 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.
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. Confirm the invalid data is no longer sent to the server.
Checking to see if systems deployed in the environment are affected by this issue:
1. Login to Symantec Encryption Management Server via SSH (for more information on how to login to the server using SSH, see article TECH149673):
2. Run the following commands:
psql oviddb ovidr -c "select count(*) from client_machine where machine_id ilike '%00000002-0000-0000-%';"
psql oviddb ovidr -c "select count(*) from client_machine where machine_id ilike '%00000003-0000-0000-%';"
psql oviddb ovidr -c "select count(*) from client_machine where hostname ='';"
If either of these result in something other than "0", then most likely the server has invalid data and needs to be corrected. Please contact a member of Symantec Support in order to obtain assistance in resolving this issue.
Check the machines for the MACHINEGUID value:
Windows 32-bit Systems with Symantec Encryption Desktop before version 10.3.2:
HKEY_LOCAL_MACHINE\SOFTWARE\PGP Corporation\PGP
Windows 64-bit Systems with Symantec Encryption Desktop before version 10.3.2:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PGP Corporation\PGP
Windows 32-bit Systems with Symantec Encryption Desktop version 10.3.2 and above:
HKEY_LOCAL_MACHINE\SOFTWARE\PGP Corporation\PGP\Common\AllUsers\MACHINEGUID
Windows 64-bit Systems with Symantec Encryption Desktop version 10.3.2 and above:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PGP Corporation\Common\AllUsers\MACHINEGUID
NOTE: If systems are missing this MACHINEGUID value from the registry, the systems may be affected and could be sending invalid data to the server. Any incorrect entry could cause this issue. If the MACHINEGUID entry is there, then check the value data to ensure a value similar to "{54CC7DE3-1432-4947-B88C-366ED5B3D931}" is also listed. If not, the system may be sending invalid data to the server. The screenshot below is an example of a properly formatted MACHINEGUID value for a system prior to Symantec Encryption Desktop 10.3.2:

Thanks for your feedback. Let us know if you have additional comments below. (requires login)