locked
Don't Report virtual Machines in KMS Management Pack para SCOM 2007 RRS feed

  • Question

  • I have installed SCOM 2007 and KMS Management Pack for SCOM 2007.

    The reporing begun run when there were pass some days... is normaly.

    The problem is that the Virtual Machines are not reporting into the Microsoft.Windows.KeyManagement.Service.VirtualMachineSummary report of Reporting Service, but the physical machines have not problem in these report.

    I have discovered the next things:

    The Database to this report to use KMS is:

    - OperationsManagerDW

    The tables involves are:

    Select * from KMSEvent.ActivationCount
    Select * from KMSEvent.ActivitySummaryByComputerName
    Select * from KMSEvent.CumulativeData
    Select * from KMSEvent.KMSEventStage
    Select * from KMSEvent.KMSReportDataAll
    Select * from KMSEvent.ReportDataLatestByCMID
    Select * from KMSEvent.TimePeriods
    Select * from KMSEvent.WindowsEditions

    The info of the virtual machines keeping into the column dwVMInfo into the table KMSEvent.KMSReportDataAll

    When this records is = 1 The machine is Virtual
    When this records is = 0 The machine is Physical

    If I make set an update of this table and I modify this records = 1, the report is correct and there are a correct Virtual Machines number, but when the SCOM use de script against , I want to say ...  when have passed several days this records is automatic update = 0 by the SCOM and my report is bad.

    I'm understand ing that the Virtual Machine or the KMS Server is reporting bad to the database's SCOM

    Who is reporting to who .... where is save the dwVMInfo ??

    Into the virtual Machine ... Into the KMS Server... WHERE ???






    www.ivanzito.com
    • Edited by IvanZito Tuesday, May 26, 2009 7:32 AM
    Tuesday, May 26, 2009 7:15 AM

Answers

  • This data is collected from the event 12290 generated on KMS server machine. The event is generated as a result of communication between client and KMS server regarding activation state. Each event contains data that is collected by KMS management pack and stored in the database you mentioned and then used in the reports. So basically you should investigate those events to search for VMInfo parameter value to confirm if there is a problem with management pack . Following is event 12290 data format :

    12290

    KMS server side log for each request

    An activation request has been processed.%nInfo:%n%1

    HRESULT

    Return code

    N-Policy

    Client product minimum count needed to activate

    Machine

    Client machine name

    CMID

    Client Machine ID

    Client Time

    Request timestamp

    VM Info

    Client OS is running in a virtual machine

    Licensing Status

    License status
    0 - Unlicensed
    1 - Licensed (Activated)
    2 - OOB grace
    3 - OOT grace,
    4 – NonGenuineGrace

    5 – Notification

    Time to Expiration

    Time remaining (minutes)

    ActID

    Activation ID - identifies the license



    Thursday, May 28, 2009 10:39 PM
  • Ivan -

    Recent innovations in hardware may cause the detection logic in KMS to falsely identify a virtual machine as a physical machine.  We provided alterations to this logic in SP2 of Vista and Windows Server 2008 which should minimize errors.  Since the management pack reports on event data, and that event data is not showing the correct values, there is no other workaround except to operate SP2 on the virtual guests exhibiting this behavior.

    Please note that the virtual dection logic in Vista and Windows Server 2008 detect software virtualization only.  Future operating systems will support detection of hypervisor-based virtualization. 

    Hope that helps!
    /Ty
    Friday, May 29, 2009 12:05 AM

All replies

  • I have installed SCOM 2007 and KMS Management Pack for SCOM 2007.

    The reporing began run when there were pass some days is normaly.

    The problem is that the Virtual Machines are not reporting into the Microsoft.Windows.KeyManagement.Service.VirtualMachineSummary report of Reporting Service, but the physical machina have not problem in these report.

    I have discovered the next things:

    The Database to this report to KMS is:

    - OperationsManagerDW

    The tables involves in this questions are:

    Select * from KMSEvent.ActivationCount
    Select * from KMSEvent.ActivitySummaryByComputerName
    Select * from KMSEvent.CumulativeData
    Select * from KMSEvent.KMSEventStage
    Select * from KMSEvent.KMSReportDataAll
    Select * from KMSEvent.ReportDataLatestByCMID
    Select * from KMSEvent.TimePeriods
    Select * from KMSEvent.WindowsEditions

    The info of the virtual machines keeping into the column dwVMInfo into the table KMSEvent.KMSReportDataAl .

    When this records is = 1 The machine is Virtual .
    When this records is = 0 The machine is Physical .

    If I make an update of this table and I modify this records = 1, the report is correct and there are a correct Virtual Machines number, but when the SCOM use de script against , I want to say when have passed several days this records is update = 0 by the SCOM and my report is bad.

    I'm understand ing that the Virtual Machine or the KMS Server is reporting bad to the database's SCOM

    someone can I tell me about it ??





    www.ivanzito.com

    which version of the KMS mp are you running?


    I didn't test the KMS managment pack yet but your probably running VMware virtual machines? The problem with that is that scom don't recognize the vmware virtual machines as a virtual machine. you can quickly check this : go to computers state view, personolize view, check virtual machine.

    If your vmware virtual machines aren't discovered as virtual machines please have a look at the management pack of Pete Zerger http://www.systemcenterforum.org/downloads/virtual-machine-discovery-mp-for-opsmgr-2007/  The MP will update the “IsVirtualMachine” property of the Windows Computer object to TRUE for VMware guests. 


    Hope this helps.


     


    Alexandre Verkinderen http://scug.be
    Tuesday, May 26, 2009 7:31 AM
  • My Virtual Machine are Hyper-V machines !!!

    www.ivanzito.com
    Tuesday, May 26, 2009 7:33 AM
  • This data is collected from the event 12290 generated on KMS server machine. The event is generated as a result of communication between client and KMS server regarding activation state. Each event contains data that is collected by KMS management pack and stored in the database you mentioned and then used in the reports. So basically you should investigate those events to search for VMInfo parameter value to confirm if there is a problem with management pack . Following is event 12290 data format :

    12290

    KMS server side log for each request

    An activation request has been processed.%nInfo:%n%1

    HRESULT

    Return code

    N-Policy

    Client product minimum count needed to activate

    Machine

    Client machine name

    CMID

    Client Machine ID

    Client Time

    Request timestamp

    VM Info

    Client OS is running in a virtual machine

    Licensing Status

    License status
    0 - Unlicensed
    1 - Licensed (Activated)
    2 - OOB grace
    3 - OOT grace,
    4 – NonGenuineGrace

    5 – Notification

    Time to Expiration

    Time remaining (minutes)

    ActID

    Activation ID - identifies the license



    Thursday, May 28, 2009 10:39 PM
  • Ivan -

    Recent innovations in hardware may cause the detection logic in KMS to falsely identify a virtual machine as a physical machine.  We provided alterations to this logic in SP2 of Vista and Windows Server 2008 which should minimize errors.  Since the management pack reports on event data, and that event data is not showing the correct values, there is no other workaround except to operate SP2 on the virtual guests exhibiting this behavior.

    Please note that the virtual dection logic in Vista and Windows Server 2008 detect software virtualization only.  Future operating systems will support detection of hypervisor-based virtualization. 

    Hope that helps!
    /Ty
    Friday, May 29, 2009 12:05 AM
  • ohhh  !!!

    Very good information ... unbelievable !!!

    Where do you find it ??

    I have a 12290 event in my KMS with de next information about a Virutal Machine:


    0x0,
    5,
    MyHostname.dominio.com,
    925c74ca-a55e-4c06-b085-d63a62567f73,
    2009/5/28 19:1,
    0, --> Here is the problema, The VM is reporting to KMS a "0" Value
    1,
    249180,
    ddfa9f7c-f09e-40b9-8c1a-be877a9a7f4b


    Is posible that the problem was hardware in my KMS Server ?
    www.ivanzito.com
    • Edited by IvanZito Friday, May 29, 2009 8:56 AM
    Friday, May 29, 2009 7:56 AM
  • The issue is not an issue on the KMS server.  A change was required on the KMS client side for SP2 and future operating systems. 

    Thanks!
    /Ty
    Friday, May 29, 2009 4:14 PM
  • I've Installed the SP2 in KMS Server and the Virtual Machine but de problem continue ... I have activated the virtual machine later ... using " slmrg.vbs -ato" then I can view into the events in KMS server the event ID: 12290 but the content is the next:
     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Security-Licensing-SLC" Guid="{1FD7C1D2-D037-4620-8D29-B2C7E5FCC13A}" EventSourceName="KmsRequests" /> 
      <EventID Qualifiers="16384">12290</EventID> 
      <Version>0</Version> 
      <Level>4</Level> 
      <Task>0</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2009-06-01T11:24:13.000Z" /> 
      <EventRecordID>905</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="0" ThreadID="0" /> 
      <Channel>Key Management Service</Channel> 
      <Computer>xxxxx.dedicados.priv</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>0xC004F041,5,xxxxxx.dedicados.priv,0d829ff5-d20c-46dc-a40b-4dd23112aa7d,2009/6/1 11:24,0,1,259200,ddfa9f7c-f09e-40b9-8c1a-be877a9a7f4b</Data> 
      <Data>0xC004F041</Data> 
      <Data>5</Data> 
      <Data>xxxxxx.dedicados.priv</Data> 
      <Data>0d829ff5-d20c-46dc-a40b-4dd23112aa7d</Data> 
      <Data>2009/6/1 11:24</Data> 
      <Data>0</Data> 
      <Data>1</Data> 
      <Data>259200</Data> 
      <Data>ddfa9f7c-f09e-40b9-8c1a-be877a9a7f4b</Data> 
      <Binary>00000400000000000100000080F403003427C95582D6714D983ED6EC3F16059F7C9FFADD9EF0B9408C1ABE877A9A7F4BE456E1336FB7524A9F91F641DD95AC48F59F820D0CD2DC46A40B4DD23112AA7D05000000C057847DABE2C9015368DA2FE24F2C4F95658F26DEB1E43F56004D00410030003000300031002E0064006500640069006300610064006F0073002E007000720069007600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000B30A09C366B8EA6D6BA20B28FE588AF8</Binary> 
      </EventData>
      </Event>
    
    This is the same.
    • Edited by IvanZito Monday, June 1, 2009 3:05 PM
    Monday, June 1, 2009 2:58 PM
  • The soluction is if your client is W7 or Windows Server R2

    Look at this into the event viewer:

    An activation request has been processed.

    Info:

    0xC004F042,5,VM-IRuiz,b0a03be2-875b-45ff-8a50-549599579b32,2009/11/16 17:42,   1     ,2,24060,620e2b3d-09e7-42fd-802a-17a13652fe7a

    But is very important this article in to use in your KMS:

    http://support.microsoft.com/default.aspx/kb/968912


    www.ivanzito.com
    Monday, November 16, 2009 5:46 PM