Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

Created: 10 Jan 2013 • Updated: 10 Jan 2013 | 19 comments

Currently running SEPM ver 12.1.2015.2015.

When running a Computer Status Log Report out of "Monitors" within the SEPM console, some hosts are reporting the incorrect OS version.  I have not been able to find a common factor.

One example I have is a large number of hosts are displaying "Windows 7 Home Premium" although they are running "Windows 7 Enterprise"

Service Pack seems to be irrelvant as there are some running SP1 (6.1.7601) and some not (6.1.7600) that are reporting the incorrect OS version of "Windows 7 Home Premium"

Side note - The correct OS version is displayed elsewhere for the same host(s) within the console (i.e.  Reports > Computer Status > Client Inventory Details & within the Clients portion of the console).

 

Is there any information regarding a fix?

If additional information is needed please let me know.

Cheers

Comments 19 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

Are the clients migrated to the SEP 12.1 RU2 as well??

This could to be a defect. I would request you to create a Case with Symantec Technical Support Team to investigate this further.

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:

  • United States: 800-342-0652 (407-357-7600 from outside the United States)
  • Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
  • United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

I would also request if you could PM me the Case # so that I could look into it.

Hope that helps!!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

amccartn's picture

Some of the clients are running RU2, some are still running a previous version.

amccartn's picture

I think this is how to send a PM.

 

I just opened a case with Tech Support. Case #03435602

.Brian's picture

Sounds like some sort of cosmetic defect. I would open a case with Symantec.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Mick2009's picture

Hi amccartn,

That does sound odd. And I agree with Brian: it does sound liek a minor cosmetic issue that can be fixed in a future release.  Please get in touch with Technical Support and pass along the details in full!  &: )

Many thanks,

Mick  

With thanks and best regards,

Mick

Steven Kintakas's picture

These defects have existed since beta, and were not addressed before the inital 12.1 release, despite feedback to technical staff, and have remained in each subsequent release.

“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”

SameerU's picture

Hi

Please upgrade the clients to the same version which will resolve the issue

Regards

 

Steven Kintakas's picture

No that's incorrect.

We are running a brand new clean install of the latest release SEP 12.1.2 (aka RU2) and when you go to Monitors and generate the 'Computer Status' report, it reports Windows Server 2008 R2 machines as Windows Server 2008. And yet on the initial RTM release of 12.1 this used to correctly report the OS. So did the RU1 release. Which mean it's been broken in RU2.

Also, go to Reports, and generate a Computer Status->Client Inventory report, and 2008 R2 machines appear as regular 2008. And yet like above, in the RTM release and the RU1 release it did report it as 2008 R2. So again, more broken functionality in RU2.

Go to Clients, right-click a 2008 R2 machine and select Edit Properties, and look at the OS field. it too incorrectly reports it as Windows Server 2008.  This defect has been in SEP 12.1 from the RTM release, and has never been fixed.

So in summary, this defect has become worse than before with the most latest release.  Surprised no one else has identified this. While to many it may not seem critical, in large enterprises customers want accurate details of their fleet, especially for reports to management.

“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”

LinwoodR's picture

I have the same issue. SEPM is 12.1.2.

For all SEP clients not yet upgraded to SEP12.1.2, Windows 7 Professional is being reported as Window 7 Ultimate.

Windows Server 2008, 2008 R2, both Enterprise and Standard are all being reported as Windows Server 2008 Standard.

Case has been opened on 2/22 with Support: # 3738563.  No response yet.

SebastianZ's picture

Issue apparently seen still by several users in 12.1 RU2 - really hope next release of SEP will fix that.

SameerU's picture

Hi

Have you upgraded clients to SEP 12.1.2

Regards

 

Steven Kintakas's picture

Sameer,

I recommend you read my entire post from above.

https://www-secure.symantec.com/connect/forums/computer-status-log-reports-wrong-os-sepm-12120152015#comment-8358721

This issue has existed in one form or another since the 12.1 Beta, and has become considerably worse in 12.1.2, so why would it be recommended that people upgrade to 12.1.2 in an attempt to fix an issue that this version is responsible for further errors in information?

“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”

LinwoodR's picture

I have upgraded a handful of clients to 12.1.2.  Windows 7 Professional is being reported correctly. Windows Server 2008 R2 Standard is still being reported as Windows Server 2008 Standard.

Other issues with 12.1.x are not resolved by 12.1.2, and I am holding back on further 12.1.2 client upgrades.  New client installations will be 12.1.2.

Ch@gGynelL_12's picture

i have the same problem too..

 

please help us to fix this issue.

Steven Kintakas's picture

Latest response from support says that they have no idea when this will be fixed. In fact they don't have a fix yet for it was their wording.

“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”

SameerU's picture

Hi

Please upgrade all clients to SEP 12.1 RU2

Regards

 

Ch@gGynelL_12's picture

Is this will fix this issue? How about the latest release of SEP 12.1 RU2 MP1? I have'nt try but all of us try to upgrade our SEPM servers including our clients to this Latest Release.

Hopefully it will now fix..

Steven Kintakas's picture

Incredibly unlikely. I've had a support case open about this for some time, and the most recent thing I was told is the fix would be released in a much later version approx. 1st half of 2014. I'm incredibly disappointed with this estimate, as this issue has been present for over 2 years since the beta versions, and now we're told the fix is about a year away.

“When it comes to enterprise software…you need to work within the product’s ‘strengths’.”