Endpoint Protection

 View Only
Expand all | Collapse all

Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

Migration User

Migration UserMar 06, 2013 07:15 AM

  • 1.  Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Jan 10, 2013 10:14 AM

    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



  • 2.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Trusted Advisor
    Posted Jan 10, 2013 10:38 AM

    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: https://support.broadcom.com (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!!!



  • 3.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Jan 10, 2013 10:45 AM

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



  • 4.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Jan 10, 2013 11:08 AM

    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  



  • 5.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Jan 16, 2013 09:54 AM

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



  • 6.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Jan 16, 2013 09:56 AM

    I think this is how to send a PM.

     

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



  • 7.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Feb 14, 2013 12:27 AM

    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.



  • 8.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Feb 14, 2013 05:19 AM

    Hi

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

    Regards

     



  • 9.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Feb 14, 2013 06:26 PM

    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.



  • 10.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 01, 2013 12:47 PM

    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.



  • 11.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 02, 2013 04:12 AM

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



  • 12.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 06, 2013 07:15 AM

    Hi

    Have you upgraded clients to SEP 12.1.2

    Regards

     



  • 13.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 06, 2013 09:39 AM

    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.



  • 14.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 07, 2013 06:13 PM

    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?



  • 15.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 21, 2013 01:53 AM

    i have the same problem too..

     

    please help us to fix this issue.



  • 16.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 24, 2013 07:16 PM

    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.



  • 17.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Mar 25, 2013 04:27 AM

    Hi

    Please upgrade all clients to SEP 12.1 RU2

    Regards

     



  • 18.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Apr 17, 2013 12:07 AM

    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..



  • 19.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Apr 17, 2013 12:28 AM

     

    Hi, 

    Keep posted the Support feedback.

    Regards

    Ajin



  • 20.  RE: Computer Status Log Reports Wrong OS - SEPM 12.1.2015.2015

    Posted Apr 17, 2013 12:57 AM

    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.