Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Windows Server 2008 shows up as Windows Vista in ESM Console with 6.5.3sp2 agent

Updated: 22 May 2010 | 2 comments
Sunny G's picture
0 0 Votes
Login to vote

Hello,

I am having an odd sort of issue.  When installing the ESM 6.5.3sp2 agent on a MS Windows Server 2008 service pack 2 (sp2) the install is successful and there are no issues, but when it registers to the ESM Manager it is detected as Windows Vista.  - Actually, i suspect this happens locally and not at registration time, but it becomes apparent after registration.

I have also installed a windows 2008 server agent and it showed up as Windows 2008.  It may not have been service pack 2, however.

So the question is, does anyone know why this would be happening, if there is a fix/workaround, any other information that would be helpful?

In the mean time, I can still run a policy with WinVista checks against this system, but it is not the ideal scenario.  I have not tried the ESM 9.0 or 9.0.1 agent yet since the manager is not upgraded.  But as I said, i was able to install a 6.5.3sp2 agent  properly in the past.  I suspect there is some registry entry, file, keyword or something somewhere that makes the agent installer think its Vista rather than 2008.  Maybe it has to do with the 2008 sp2 as I hear it is very similar to that of Vista's.

thanks,
Sunny

discussion Filed Under:

Comments

kevin_stultz's picture
16
Nov
2009
0 Votes 0
Login to vote

Updated 6.5.3 Agent for Windows 2008 SP2

There was an issue with SP2 causing ESM 6.5.3 agent to not recognize Windows 2008.  There is an updated agent which resolves this issue. See:
http://service1.symantec.com/support/intrusiondetectkb.nsf/854fa02b4f5013678825731a007d06af/593abeabf5f065ba882576200074d78b?OpenDocument

Sunny G's picture
17
Nov
2009
0 Votes 0
Login to vote

esm agent on windows server 2008 shows up as vista

Hi Kevin,

thanks very much for pointing me to this KB.  I searched but couldn't find anything on my own.

this updated agent has resolved my issue.

Sunny