locked
Unable to activate deployed servers against KMS error 0x80072EE2

    Question

  • I have a Windows 2008 R2 server that is my KMS server. I am deploying Windows 2008 R2 servers and setting the KMS server via 'slmgr ipaddressofmykms' and then using slmgr /ato activate the server. I had this working but now on the new servers I am getting the Error: 0x80072EE2. Running the command slui 0x2a 0x80072EE2 comes back Description: The operation timed out. I turned off all firewalls for troubleshooting, still unable to activate. I thought slmgr /dli or /dlv should return your KMS server IP but I dont see it listed. I was looking for this to verify the /ato command took place.

    Anyone had this issues or know other troubleshooting steps I can take? I can ping my KMS server from the client and even do remotedesktop so I know there is connectivity.

    TIA
    -cybercoaster out

    Event logs
    Log Name:      Application
    Source:        Microsoft-Windows-Security-SPP
    Date:          10/5/2009 11:26:02 AM
    Event ID:      8200
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      hostname
    Description:
    License acquisition failure details.
    hr=0x80072EE2
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" />
        <EventID Qualifiers="49152">8200</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-10-05T16:26:02.000000000Z" />
        <EventRecordID>418</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>utinhp52</Computer>
        <Security />
      </System>
      <EventData>
        <Data>hr=0x80072EE2</Data>
        <Data>00010001(0x00000000, 11:25:38:632 - http://go.microsoft.com/fwlink/?LinkID=88342)
    00020001(0x00000000, 11:25:38:632)
    00030001(0x00000000, 11:25:38:648 - http://go.microsoft.com)
    00030002(0x00000000, 11:25:38:648 - 0)
    00040001(0x00000000, 11:25:38:648 - http://go.microsoft.com)
    00040002(0x00000000, 11:25:38:663 - 1, &lt;NULL&gt;, &lt;NULL&gt;, &lt;NULL&gt;)
    00040004(0x80072F94, 11:25:41:226 - &lt;NULL&gt;)
    00040006(0x00000000, 11:25:41:226 - 1, http://go.microsoft.com, &lt;NULL&gt;, &lt;local&gt;)
    00020005(0x00000000, 11:25:41:226 - 0)
    00020007(0x80072EE2, 11:26:02:304)
    00010002(0x80072EE2, 11:26:02:304 - &lt;NULL&gt;)
    00010003(0x80072EE2, 11:26:02:304)
    </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-Windows-Security-SPP
    Date:          10/5/2009 11:26:02 AM
    Event ID:      1008
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      hostname
    Description:
    Acquisition of Secure Processor Certificate failed. hr=0x80072EE2
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" />
        <EventID Qualifiers="49152">1008</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-10-05T16:26:02.000000000Z" />
        <EventRecordID>419</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>utinhp52</Computer>
        <Security />
      </System>
      <EventData>
        <Data>hr=0x80072EE2</Data>
        <Data>8fe15d04-fc66-40e6-bf34-942481e06fd8</Data>
      </EventData>
    </Event>

    Monday, October 05, 2009 4:18 PM

Answers

  • Here was the solution -

    slmgr /ipk 489J6-VHDMP-X63PK-3K798-CPX3Y (KMS client product key from deployment guide)
    slmgr /ato

    slmgr now correctly shows it is a KMS client.

    So somehow the systems were set to be a KMS server although slmgr /skms was set. So executing the /ipk switch reset the system to be a KMS client.
    -cybercoaster out
    • Marked as answer by cybercoaster Tuesday, October 06, 2009 2:25 PM
    Tuesday, October 06, 2009 2:25 PM

All replies

  • Looks like it's an issue just with my virtual Enterprise Full images. The physical's and virtual Core works. I have tried all I know to try and resolve this error by cleaning out the KMS setting, reapplying etc... still no luck. If anyone has any ideas other than redeploying, I would appreciate it.

    Thanks
    -cybercoaster out
    Monday, October 05, 2009 8:54 PM
  • I think I see whats going on. The KMS clients are not coming up as clients. If I do slmgr /dli, I dont see the client information screen. Anyone know how I can force the system to know that it is a KMS client?


    -cybercoaster out
    Tuesday, October 06, 2009 2:25 AM
  • Hi,

     

    I suggest checking your proxy settings in IE.

     

    In addition, please refer to the following article to deploy KMS clients:

     

    Volume Activation 2.0 Deployment Guide

    http://technet.microsoft.com/en-us/library/cc303280.aspx#_Configure_KMS_Clients

     

    Hope it helps.

     

    Tim Quan - MSFT

     

     

    Tuesday, October 06, 2009 3:54 AM
    Moderator
  • Here was the solution -

    slmgr /ipk 489J6-VHDMP-X63PK-3K798-CPX3Y (KMS client product key from deployment guide)
    slmgr /ato

    slmgr now correctly shows it is a KMS client.

    So somehow the systems were set to be a KMS server although slmgr /skms was set. So executing the /ipk switch reset the system to be a KMS client.
    -cybercoaster out
    • Marked as answer by cybercoaster Tuesday, October 06, 2009 2:25 PM
    Tuesday, October 06, 2009 2:25 PM
  • If I might add...

    I had ran into issues with this during a recent deployment.  Client initially got KMS keys for only four Windows 2008 R2 Ent servers.  This obviously was an issue as we needed at least five to get the KMS server to activate clients.

    The client was requested to get replacement MAK keys so that we could do the 'traditional' install.

    After installing the new keys none servers would not activate, at all (error 0x80072EE2).

    I removed KMS server and DNS SRV records, rebooted everything and still no luck.

    After troubleshooting for a bit I found that I could get to all internet sites but Microsoft.com

    Resolution:
    - Reset IE8 to default
    - Ran through the basic customization wizard again
    - Reboot
    - Activated correctly after that.
    Tuesday, October 06, 2009 9:06 PM