Why are my Windows 7 64 Bit clients being detected as Vista?
Created: 13 Feb 2013 | Updated: 14 Feb 2013 | 12 comments
This issue has been solved. See solution.
I have like 8 machines out of date and when I look, they are being detected as Vista clients.
Seriously?!?!?!
Discussion Filed Under:
Comments 12 Comments • Jump to latest comment
Likely just a "cosmetic" bug...or perhaps some sort of bug when is tries to enumerate the registry to figure out the OS and it doesn't return the correct info. I've seen the same thing from time to time showing incorrect OS.
SEP Knowledge Base
Endpoint SWAT
Sheesh!!!
Next thing you know, OS Detected, Windows 3.1 :-D
or even better Windows ME
You have bigger issues than
SEP Knowledge Base
Endpoint SWAT
There have been already similar cases reported with the detection of windows 7 editions as well:
https://www-secure.symantec.com/connect/forums/com...
Best bet is to open a case with Support for them to have a check with engineering - but most likely they would be already aware of something that visible.
I would certainly hope so, 12 has had some really bizarre issues that I have NEVER encountered before.
Who uses Vista anymore? :-D
There are still some ppl... you would be amazed:P
"Windows Server 2008 R2" in many places across the SEPM interface and/or its Report areas etc incorrectly appears as "Windows Server 2008". This is a massive flaw, because it is like trying to suggest that Vista and 7 are the same OS, when clearly they're not.
I reported this error to the then SEP product manager back in 2011 in a face-to-face meeting, who did nothing about it as the defect is still even in the most latest 12.1.2 release.
I'm told product managers have since changed a few times, but simply defects such as these go ignored.
Very frustrating for enterprise reporting to customers who demand accuracy.
“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”
Hi,
You should log a call with symantec technical support team.
Thank& Regards,
Ambesh
Please mark your thread as 'SOLVED' with the answer that helps you.
The support team is already aware it. The point I'm making when a global alliance partner gives a product manager a heads up for their benefit when a product is still in beta, they should listen for the benefit of their product.
Failure to do so has allowed such a simple, yet critical governance issue to be released in the final release, and every subsequent build since then.
“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”
HI,
Same Problem thread
https://www-secure.symantec.com/connect/forums/sepm122-showing-wrong-os
https://www-secure.symantec.com/connect/forums/computer-status-log-reports-wrong-os-sepm-12120152015
Thanks In Advance
Ashish Sharma
SEPM Knowledgebase Documents
Hi
What is the version of Symantec Endpoint Protection Manager
Regards
Hi Bryan,
This kind of issue have seen in past windows 7 home edition machine was detecting as Windows XP home edition . I would request you to create a Case with Support team to investigate this further.
Administrators should treat this as a "known issue." The SEPM should be installed on a suitable platform
Check this article:https://www-secure.symantec.com/connect/articles/could-not-install-symantec-endpoint-protection-manager-windows-7-home-premium-64-bit-operat
How to create a new case in MySupport
http://www.symantec.com/business/support/index?page=content&id=TECH58873
Phone numbers to contact Tech Support:-
Regional Support Telephone Numbers:
Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp
Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |
Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.&
Would you like to reply?
Login or Register to post your comment.