11-10-2009 06:06 AM
Solved! Go to Solution.
11-10-2009 06:52 AM
As my systems appear to do the same thing (with the key being recreated on a service restart of the BE Remote Agent), I would suggest you log a proper support case with Symantec Technical Support about the issue as it looks like an oversite that was introduced when they added the VMWare agent to the product - as such it is not likely to be solved on a community supported forum.
Your other option of course would be to configure your security product to ignore that key as it is not likely to be an actual vulnerability.
11-10-2009 06:52 AM
As my systems appear to do the same thing (with the key being recreated on a service restart of the BE Remote Agent), I would suggest you log a proper support case with Symantec Technical Support about the issue as it looks like an oversite that was introduced when they added the VMWare agent to the product - as such it is not likely to be solved on a community supported forum.
Your other option of course would be to configure your security product to ignore that key as it is not likely to be an actual vulnerability.
11-10-2009 08:28 AM
I figured as much. I was just curious to see if he was happening to others. Now my burden is to get some documentation on it so I can get an exception from the guys in IA.
thanks for your help
11-30-2009 07:24 AM