Windows 8.1 Ente. KMS client

Hi,
I need to download windows 8.1 enterprise KMS client. Is it available to download?
Win 8.1 Evaluation available on TechNet is retail channel.
N.A.Malik

EDIT: Not for public download. If you have an MSDN or TechNet subscription, you may have access to the VL channel product in your subscriber downloads. It's also available from VLSC if you have a VL agreement.
As per
http://technet.microsoft.com/en-us/evalcenter/hh699156.aspx?ocid=wc-tn-wctc upgrade/conversion from evaluation to retail/full license is not supported.
You *might* be able to change the product key of the evaluation license to a KMSclient, but I would think this would be blocked, or, would leave the evaluation timer in place.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

  • Windows 7 KMS client activation error

    hi,
    Windows 7 KMS client activation error
    Any known issue?
    Thanks

    This problem occurs if the KMS server does not find a valid Windows marker in the ACPI_SLIC table in the computer's BIOS program. This problem occurs for one of the following reasons.
    Cause 1
    You purchased a computer that has a qualifying Windows operating system installed. However, the Windows marker in the ACPI_SLIC table is corrupted.
    Cause 2
    You purchased a computer that does not have a qualifying Windows operating system installed. In this case, the Windows marker is not present in the ACPI_SLIC table.

  • Can i Host the KMS Server in the Server which is a KMS client of other KMS Server

    Hi,
              Is it Possiblei can Host the KMS Server in the Server(2012 R2) which is a KMS client of other KMS Server..?
            If yes ... Do i need to do any special configuration for that or normal Host configuration is enough..?
    Thanks
    Balaji K 

    Hi Sir,
    "The KMS service does not require a dedicated server. The KMS service can be co-hosted with other services, such as Active Directory® Domain Services (AD DS) domain controllers and read-only domain controllers (RODCs).
    KMS hosts can also run on physical computers or virtual machines that are running any supported Windows operating system, including Windows Server 2003. Although a KMS host that is running Windows Server 2008 R2 can activate any Windows operating
    system that supports Volume Activation, a KMS host that is running Windows 7 can activate only computers running Windows 7 and Windows Vista."
    Based on this ,it should work .
    If you want to activate a windows server please enable KMS on a server .
    "By default, client computers connect to the KMS host for activation by using anonymous RPCs through TCP port 1688. (You can change the default port.) After establishing a TCP session with the KMS host, the client sends a single request packet.
    The KMS host responds with the activation count. If the count meets or exceeds the activation threshold for that operating system, the client is activated and the session is closed. The KMS client uses this same process for renewal requests. The communication
    each way is 250 bytes."
    https://technet.microsoft.com/en-us/library/ff793434.aspx
    Also you can change it if that port is used by other service :
    https://technet.microsoft.com/en-us/library/ff793407.aspx?f=255&MSPPError=-2147217396
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Activating Windows 7 by using KMS Without the Active Directory Domain environment

    Dear,
                 Can we able to activate the Windows 7 O/S Machines by using KMS without the Active Directory Domain environment,As our some of the Computers will not connect with AD domain, we need to setup the speprate KMS
    server for this.
    Thanks
    Balaji K 

    You can point the KMS clients to the KMS host machine by opening an Elevated CMD prompt:
    and running slmgr /skms to point directly to the KMS host.
    You do not need a Domain controller.
    Volume Licensing: Key Management Service (KMS) Client Options:
    /skms <Name[:Port] | : port> [Activation ID] [Activation ID]                                                                                                          
    Set the name and/or the port for the KMS computer this machine will use. IPv6 address must be specified in
    the format [hostname]:port                          /ckms [Activation ID]                  
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Setting KMS client key in MDT

    where exactly in MDT, Windows KMS client key should be entered?
    Thx.
    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Short answer is you really don't need to:
    https://social.technet.microsoft.com/Forums/en-US/c9691329-702e-42e1-9593-c8c06618ff0f/mdt-2010-kms-activation?forum=mdt
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • KMS Client Keys

    We just rolled out 1200 Windows 8 Pro workstations in our environment. Our image was scripted with KMS client setup key NG4HW-VH26C-733KW-K6F98-J8CK4. The workstations are activating with no problem for our internal KMS Volume License Activation server.
    They are renewing the activation every 120 days. However, when I go to one of the clients to look to see if windows is activated, it shows a license expiration date of 10-7-2014. I am seeing this in Computer>Properties>Windows Activation>View Details
    in Windows Activation. Are all our workstations going to expire and stop working?

    "KMS activations are valid for 180 days—the activation validity interval. To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers
    attempt to renew their activation every seven days. If KMS activation fails , the client will retry every two hours. After a client computer’s activation is renewed, the activation validity interval begins again."
    Ref:
    Understanding KMS
    Carey Frisch

  • Cannot install KMS key in VAMT for KMS clients

    Dear Sir / Madam,
    I have some technical problems about setup the KMS host and KMS clients.
    OS of the KMS host: Windows Server 2012 Standard
    OS of the KMS client: Windows 7 Professional (32bit)
    Question 1:
    I want to use KMS host server to handle KMS keys and activations for KMS clients. Which type of KMS key need to install in KMS host ?
    Would I need to install Windows 7 Professional KMS key or
    Windows Server 2012 Standard KMS key in the Volume Activation Management Tool (VAMT) ?
    Question 2:
    I found that I cannot installed the Windows 7 Professional KMS key in the Volume Activation Management Tool (VAMT), it pop-up an error message said that the KMS key invalid. How can I fix the problem?
    Thanks for your help!

    Hi Siu Wai,
    You can also follow these steps:
    1. Select a computer that you want to be your KMS host:
    2. Install Windows Server.
    3. At cmd prompt type the following:
    Slmgr.vbs /ipk  <your KMS KEY from MVLS>
    The /ipk installs your MVLS key.  Note if you need to change your key. For example change from a KMS_B to KMS_C key you must restart the Software Licensing service.
    4. At cmd prompt type the following:
    Slmgr.vbs /ato
    The /ato activates the KMS host with Microsoft. You must activate the KMS host.
    5. Restart the Software Licensing service.
    6. Install the KMS client computers by using volume license media. You should not be prompted for cdkey during installation
    7. By default these KMS client computers will query DNS and locate your KMS host and activate
    KMS Client Setup Keys
    To reset computers to be KMS clients type the following at elevated command prompt:
    Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the generic VL key from the following link.
    http://technet.microsoft.com/en-us/library/ee355153.aspx#EFAA
    Refer to:
    Is it possibile to host multiple KMS Keys
    on a single KMS server?
    If there is anything else regarding this issue, please feel free to post back.
    Best Regards,
    Anna Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • KMS client activation failed, but got server response?

    I've been using KMS for several years. Generally there are no problems with KMS, but I have a single machine that is refusing to activate, and I cannot determine why. I've been doing extensive web searching but I'm not finding anything useful.
    Windows 7 Pro client is using the Windows 7 Pro KMS client key GPDD4 as usual.
    KMS Server is in Windows 2008 R2
    The event log says the client is getting a response from KMS server (see below).
    ============================
    Server: slmgr /dlv
    Name: Windows Server(R), ServerStandard edition
    Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel
    Partial Product Key: 7GCM2
    License Status: Licensed
    Key Management Service is enabled on this machine
        Current count: 50
        Listening on Port: 1688
        DNS publishing enabled
        KMS priority: Normal
    Key Management Service cumulative requests received from clients
        Total requests received: 444
        Failed requests received: 297
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 86
        Requests with License Status Initial grace period: 12
        Requests with License Status License expired or Hardware out of tolerance: 2
        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 47
    ===============================
    Client ability to find KMS Server: 
    C:\Users\foo>nslookup -type=srv _vlmcs._tcp
    Server:  UnKnown
    Address:  172.20.0.8
    _vlmcs._tcp.XXXXXXXXXXXX        SRV service location:
              priority       = 0
              weight         = 0
              port           = 1688
              svr hostname   = dc3.XXXXXXXXXXX
    dc3.XXXXXXXXX        internet address = 172.20.0.11
    ===============================
    Client: slmgr /dlv
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
    Installation ID: 011751536521019726056115618440708701492313365893152065
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 43200 minute(s) (30 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 7/28/2014 9:36:41 AM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
    =========================
    Client:    slmgr /ato
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.
    Activating Windows(R) 7, Professional edition (b92e9980-b9d5-4821-9c94-140f632f6312) ...
    Error: Product activation failed.
    =========================
    Client: Application Event log
    Security-SPP Event ID 12288
    The client has sent an activation request to the key management service machine.
    Info:
    0x00000000, 0x00000000, dc3.XXXXXXXXXX:1688, 637b796e-5348-4ce1-b0b5-4d750e9d471e, 2014/07/28 14:43, 0, 2, 43200, b92e9980-b9d5-4821-9c94-140f632f6312, 25
    Security-SPP Event ID 12289
    The client has processed an activation response from the key management service machine.
    Info:
    0x00000000, 0x00000000, 1, 0, 50, 120, 10080, 2014/07/28 14:43
    Security-SPP Event ID 1033
    These policies are being excluded since they are only defined with override-only attribute.
    Policy Names=(IIS-W3SVC-MaxConcurrentRequests) (Microsoft.Windows.Smc-Enabled) (Shell-InBoxGames-FreeCell-EnableGame) (Shell-InBoxGames-Hearts-EnableGame) (Shell-InBoxGames-Minesweeper-EnableGame) (Shell-InBoxGames-PurblePlace-EnableGame) (Shell-InBoxGames-Shanghai-EnableGame)
    (Shell-InBoxGames-Solitaire-EnableGame) (Shell-InBoxGames-SpiderSolitaire-EnableGame) (Shell-MultiplayerInboxGames-Backgammon-EnableGame) (Shell-MultiplayerInboxGames-Checkers-EnableGame) (Shell-MultiplayerInboxGames-Spades-EnableGame) (Shell-PremiumInBoxGames-Chess-EnableGame)
    (Telnet-Client-EnableTelnetClient) (Telnet-Server-EnableTelnetServer) (TiffIFilterLicensing-EnableTiffIFilter) (WindowsAnytimeUpgrade-CanUpgrade) 
    App Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Sku Id=b92e9980-b9d5-4821-9c94-140f632f6312
    Security-SPP Event ID 1003
    The Software Protection service has completed licensing status check.
    Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Licensing Status=
    1: 4de78642-0f7f-4b61-9392-8add86d70ae8, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    2: 50e329f7-a5fa-46b2-85fd-f224e5da7764, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    3: 5a79ecd8-d33f-406c-a619-7785899b5d59, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    4: 770bc271-8dc1-467d-b574-73cbacbeccd1, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    5: 90a61a0d-0b76-4bf1-a8b8-89061855a4c9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    6: 92f9d22a-65f5-49a7-90fe-06491b4fc379, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    7: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    8: 9ccffaf9-86a2-414e-b031-b2f777720e90, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    9: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 0 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30
    43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]
    10: c1027486-8ae8-4633-9cf9-9658ed80504d, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    11: c1e88de3-96c4-4563-ad7d-775f65b1e670, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    12: c33001fc-5e9c-4f27-8c05-e0154adb0db4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    13: cf3c5b35-35ff-4c95-9bbd-a188e47ad14c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    14: cff07cac-7534-4cc3-b3f3-99e1a0aa3c20, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    15: d188820a-cb63-4bad-a9a2-40b843ee23b7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    16: d8e04254-f9a5-4729-ae86-886de6aa907c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    17: da22eadd-46dc-4056-a287-f5041c852470, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    18: e120e868-3df2-464a-95a0-b52fa5ada4bf, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    19: e838d943-63ed-4a0b-9fb1-47152908acc9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    20: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    21: afd5f68f-b70f-4000-a21d-28dbc8be8b07, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    Security-SPP Event ID 1003
    The Software Protection service has completed licensing status check.
    Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Licensing Status=
    1: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 1 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30
    43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]
    ============================
    Client MGA output:
    Diagnostic Report (1.9.0027.0):
    Windows Validation Data-->
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
    Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
    Windows Product ID: 00371-868-0000007-85411
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {5A310AE8-BFD2-49F1-A8BF-688D339981E8}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.140303-2144
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Professional Plus 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    File Scan Data-->
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{5A310AE8-BFD2-49F1-A8BF-688D339981E8}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85411</PID><PIDType>1</PIDType><SID>S-1-5-21-3521851180-3244512111-2218252725</SID><SYSTEM><Manufacturer>Dell
    Inc.</Manufacturer><Model>Inspiron 546 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A09</Version><SMBIOSVersion major="2" minor="5"/><Date>20090808000000.000000+000</Date></BIOS><HWID>095F3D07018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central
    Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>FX09
      </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft
    Office Professional Plus 2007</Name><Ver>12</Ver><Val>1208E0A87E81D86</Val><Hash>FlQRxKwAwaRad03SQZkKxNggIRU=</Hash><Pid>89409-707-0082056-65245</Pid><PidType>14</PidType></Product></Products><Applications><App
    Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12"
    Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>
    Spsys.log Content: 0x80070002
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
    Installation ID: 011751536521019726056115618440708701492313365893152065
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 43200 minute(s) (30 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 7/28/2014 9:31:36 AM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 6:23:2014 07:16
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    HWID Data-->
    HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJRe04hAjl+cEVTyEDPMabbK6kXsLQilArQ=
    OEM Activation 1.0 Data-->
    N/A
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value
    OEMTableID Value
      APIC DELL  
    FX09   
      FACP DELL  
    FX09   
      HPET DELL  
    OEMHPET 
      MCFG DELL  
    OEMMCFG 
      SLIC DELL  
    FX09   
      OSFR DELL  
    FX09   
      OEMB DELL  
    FX09   
      SSDT A M I
    POWERNOW
    ================================
    Windows 7 Pro was installed on this machine using Microsoft's volume activation media, and is a standard image applied via Windows Deployment Services to some 200 other computers with no problems. 
    We also use a variety of surplus/off-lease machines, usually Dell brand, never with any activation problems.

    It's a Dell Inspiron desktop. Apparently a "for the home" system? Yet it was bought with Win 7 Pro OEM installed, and so I had hoped I could roll it into the KMS easily. Tried updating the BIOS but still acts the same.
    How can a "home edition" BIOS that's incompatible with KMS come with Win 7 Pro OEM?
    Oddly, we have several Dell XPS systems that are using KMS just fine. Those are almost exclusively marketed as "power gamer" systems for home use. I should see if there's some way to figure out which specific Dell products do this so they can be avoided.
    Fortunately it seems Windows 7 Pro edition software does not care if I use the OEM key from the sticker, so I typed that in and it activated.
    (Great, one weird machine that has to be treated specially from everything else we've got.)
    Probably a question for Dell to answer. For whatever reason, Dell have not performed all the necessary OEM Activation (OA) configuration tasks on this machine, perhaps due to their manufacturing/marketing strategy for this model, or perhaps due to a defective
    configuration pass in the factory. Perhaps the mainboard in this machine was repaired or replaced at some stage, and wasn't correctly re-configured. Only Dell can resolve the missing marker, since it requires OEM tools.
    Activating using the COA sticker product key, doesn't depend on the marker being present.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Unable to activate Windows 7 automatically from KMS

    Hi
    We use KMS in our environment to activate windows 7. But we have a set of windows 7 VM's that is not getting activated from KMS. When we manually do using SLMGR commands it gets activated. Kindly suggest
    Regards Sushain KApoor

    Hi,
    Please take a look at the following article regarding KMS client activation:
    Configuring KMS Clients
    Make sure the connection between the VMs and the KMS host is configured well.
    By default KMS clients automatically attempt to discover KMS hosts. Auto-discovery can be disabled by manually assigning a KMS host to a KMS client. This action also clears the KMS host name from the KMS client’s cache. If auto-discovery is disabled, it
    can be re-enable by running slmgr.vbs /ckms at a command prompt.
    Best regards
    Michael Shao
    TechNet Community Support

  • Switching WSUS server and Windows 8.1/Server2008/Server2012 clients won't connect, Windows 7/Server2003 is fine

    I need to split the load of my WSUS on to another site because the amount of computers is straining the internet connection in the amount of uploads performed.
    However I'm having an issue at the second WSUS where only Windows 7 and Server 2003 clients will update...
    Windows 8.1 and Server 2008 and Server2012 won't update giving the following error codes: 8024400A and 80072EE2
    The WSUS is a Server 2012 with Local Update Publisher 1.1 installed. It works fine locally at the site but not across our WAN. 
    The clients appear in the WSUS console but fail to check for updates.
    I've tried it with the firewall turned off...  
    Both WSUS servers are using Microsoft SCEP 2012.
    Has anyone out there experienced this? Or have any suggestions to fix?
    Cheers.

    Hi there,
    I spoke too soon, I think I got one Windows 8 client to update yesterday by fluke. Now today it won't. 
    There's not much different between the W7 and W8 systems they both use the same antivirus. Same software but updated on W8. 
    Here is the windows update.log:
    2014-06-05 10:44:14:561
    976 954
    Misc ===========  Logging initialized (build: 7.9.9600.17093, tz: +1000)  ===========
    2014-06-05 10:44:14:639
    976 954
    Misc  = Process: C:\Windows\system32\svchost.exe
    2014-06-05 10:44:14:639
    976 954
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-06-05 10:44:14:561
    976 954
    Service *************
    2014-06-05 10:44:14:639
    976 954
    Service ** START **  Service: Service startup
    2014-06-05 10:44:14:639
    976 954
    Service *********
    2014-06-05 10:44:15:311
    976 954
    IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
    2014-06-05 10:44:15:311
    976 954
    Agent  * WU client version 7.9.9600.17093
    2014-06-05 10:44:15:326
    976 954
    Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2014-06-05 10:44:15:326
    976 954
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-06-05 10:44:15:326
    976 954
    Agent  * Access type: No proxy
    2014-06-05 10:44:15:326
    976 954
    Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326
    976 954
    Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326
    976 954
    Agent  * Network state: Connected
    2014-06-05 10:44:15:326
    976 954
    Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-06-05 10:44:15:326
    976 954
    Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-06-05 10:44:16:123
    976 954
    Agent ***********  Agent: Initializing global settings cache  ***********
    2014-06-05 10:44:16:123
    976 954
    Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-06-05 10:44:16:123
    976 954
    Agent  * WSUS server: http://10.155.194.59:8530
    2014-06-05 10:44:16:123
    976 954
    Agent  * WSUS status server: http://10.155.194.59:8530
    2014-06-05 10:44:16:123
    976 954
    Agent  * Target group: Test Group
    2014-06-05 10:44:16:123
    976 954
    Agent  * Windows Update access disabled: No
    2014-06-05 10:44:16:170
    976 954
    WuTask WuTaskManager delay initialize completed successfully..
    2014-06-05 10:44:16:170
    976 954
    AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:24:13, not idle-only, not network-only
    2014-06-05 10:44:16:170
    976 954
    AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2014-06-05 05:36:25, not idle-only, not network-only
    2014-06-05 10:44:16:170
    976 954
    AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2014-06-05 05:36:25, not idle-only, not network-only
    2014-06-05 10:44:16:170
    976 954
    Report CWERReporter::Init succeeded
    2014-06-05 10:44:16:170
    976 954
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-06-05 10:44:16:170
    976 954
    DnldMgr Download manager restoring 0 downloads
    2014-06-05 10:44:16:170
    976 954
    AU ###########  AU: Initializing Automatic Updates  ###########
    2014-06-05 10:44:16:170
    976 954
    AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:44:16:170
    976 954
    AU AIR Mode is disabled
    2014-06-05 10:44:16:170
    976 954
    AU  # Policy Driven Provider: http://10.155.194.59:8530
    2014-06-05 10:44:16:170
    976 954
    AU  # Detection frequency: 22
    2014-06-05 10:44:16:170
    976 954
    AU  # Target group: Test Group
    2014-06-05 10:44:16:170
    976 954
    AU  # Approval type: Scheduled (Policy)
    2014-06-05 10:44:16:170
    976 954
    AU  # Auto-install minor updates: Yes (Policy)
    2014-06-05 10:44:16:170
    976 954
    AU  # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Scheduled)
    2014-06-05 10:44:16:170
    976 954
    AU  # Will interact with non-admins (Non-admins are elevated (Policy))
    2014-06-05 10:44:16:186
    976 954
    AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032
    2014-06-05 10:44:16:186
    976 954
    AU AU finished delayed initialization
    2014-06-05 10:44:16:202
    976 954
    AU Adding timer: 
    2014-06-05 10:44:16:202
    976 954
    AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 03:47:12, not idle-only, not network-only
    2014-06-05 10:44:16:217
    976 99c
    DnldMgr Asking handlers to reconcile their sandboxes
    2014-06-05 10:45:17:562
    976 954
    AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.
    2014-06-05 10:45:31:453
    976 778
    IdleTmr Incremented idle timer priority operation counter to 1
    2014-06-05 10:45:34:562
    976 778
    AU Triggering AU detection through DetectNow API
    2014-06-05 10:45:34:562
    976 778
    AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:45:34:562
    976 778
    AU Triggering Online detection (interactive)
    2014-06-05 10:45:34:562
    976 778
    AU Adding timer: 
    2014-06-05 10:45:34:562
    976 778
    AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-06-05 00:45:34, not idle-only, not network-only
    2014-06-05 10:45:34:609
    976 954
    AU #############
    2014-06-05 10:45:34:609
    976 954
    AU ## START ##  AU: Search for updates
    2014-06-05 10:45:34:609
    976 954
    AU #########
    2014-06-05 10:45:34:609
    976 954
    AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
    2014-06-05 10:45:34:609
    976 954
    IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 15; does use network; is not at background priority
    2014-06-05 10:45:34:609
    976 954
    IdleTmr Incremented idle timer priority operation counter to 2
    2014-06-05 10:45:34:797
    976 954
    Report ***********  Report: Initializing static reporting data  ***********
    2014-06-05 10:45:34:797
    976 954
    Report  * OS Version = 6.3.9600.0.0.65792
    2014-06-05 10:45:34:797
    976 954
    Report  * OS Product Type = 0x00000004
    2014-06-05 10:45:34:813
    976 954
    Report  * Computer Brand = Microsoft Corporation
    2014-06-05 10:45:34:813
    976 954
    Report  * Computer Model = Virtual Machine
    2014-06-05 10:45:34:813
    976 954
    Report  * Platform Role = 1
    2014-06-05 10:45:34:813
    976 954
    Report  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Revision = 090004 
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Name = BIOS Date: 03/19/09 22:51:32  Ver: 09.00.04
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Release Date = 2009-03-19T00:00:00
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Sku Number unavailable.
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Vendor = American Megatrends Inc.
    2014-06-05 10:45:34:813
    976 954
    Report  * Bios Family unavailable.
    2014-06-05 10:45:34:828
    976 954
    Report  * Bios Major Release unavailable.
    2014-06-05 10:45:34:828
    976 954
    Report  * Bios Minor Release unavailable.
    2014-06-05 10:45:34:828
    976 954
    Report  * Locale ID = 3081
    2014-06-05 10:45:35:578
    976 954
    Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609
    976 954
    AU <<## SUBMITTED ## AU: Search for updates  [CallId = {CDA6DEA2-9874-4DB5-AAA7-9A05D933C012} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-06-05 10:45:35:609
    976 fc4
    Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609
    976 fc4
    Agent *************
    2014-06-05 10:45:35:609
    976 fc4
    Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
    2014-06-05 10:45:35:609
    976 fc4
    Agent *********
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * Online = Yes; Ignore download priority = No
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
    and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * Search Scope = {Machine & All Users}
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * Caller SID for Applicability: S-1-5-21-1323361640-3159480285-1943353560-1532
    2014-06-05 10:45:35:609
    976 fc4
    Agent  * RegisterService is set
    2014-06-05 10:45:35:625
    976 fc4
    EP Got WSUS Client/Server URL: "http://10.155.194.59:8530/ClientWebService/client.asmx"
    2014-06-05 10:45:35:641
    976 fc4
    Setup Checking for agent SelfUpdate
    2014-06-05 10:45:35:641
    976 fc4
    Setup Client version: Core: 7.9.9600.17093  Aux: 7.9.9600.17093
    2014-06-05 10:45:35:641
    976 fc4
    EP Got WSUS SelfUpdate URL: "http://10.155.194.59:8530/selfupdate"
    2014-06-05 10:45:35:672
    976 fc4
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-06-05 10:45:35:734
    976 fc4
    Misc Microsoft signed: NA
    2014-06-05 10:45:35:734
    976 fc4
    Misc Infrastructure signed: Yes
    2014-06-05 10:45:35:734
    976 fc4
    Misc WARNING: Cab does not contain correct inner CAB file.
    2014-06-05 10:45:35:734
    976 fc4
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-06-05 10:45:35:734
    976 fc4
    Misc Microsoft signed: NA
    2014-06-05 10:45:35:750
    976 fc4
    Misc Infrastructure signed: Yes
    2014-06-05 10:45:35:766
    976 fc4
    Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2014-06-05 10:45:35:766
    976 fc4
    Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-06-05 10:45:35:907
    976 fc4
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    --continued--

  • Upgrade Windows 8.0 Pro. to Windows 8.1 Ent.

    Due to a requirement of one of our schools we are purchasing quite a number of Gesture based devices.
    These devices come with Windows 8.0/8.1 Pro pre-installed.
    I'm looking into ways of upgrading to Windows 8.1 Ent. I thought "setup.exe /auto:upgrade" might work, however when I run it on these devices nothing happens.  I believe this is due to an "error" I receive when running through the
    setup wizard dealing with the Display languages needing to be re-installed.
    I'd like to confirm that this is indeed the issue, and if so find a solution that would allow me to perform this upgrade.

    Hi,
    Would you please let me know what tool you plan to use to deploy Windows 8.1 Enterprise?
    Please help to post back the full description of the error message you got.
    Also, if you got any other language packages besides English were installed on the Pro version computer, please try to remove it and try again.
    As I known, if you have any folder redirection GP in your current environment, the deployment will fail.
    For further plan, please help to upload the setuperr.log and
    setupact.log under C:\Windows\Logs\PBR\PreRollbackLogs\ and C:\WINDOWS\PANTHER\ here for research.
    Here is the article for your reference:
    Upgrading to Windows 8.1 in the Enterprise
    http://windowsdeployments.net/upgrading-to-windows-8-1-in-the-enterprise/
    Hope this could be helpful.
    Kate Li
    TechNet Community Support

  • BlueTooth driver installation bluescreen "VIDEO_DXGKRNL_FATAL_ERROR" on Windows 8.1 ENT

    Dears,
    My new Lenovo ThinkPad E440  turns into a blue screen with the error code: VIDEO_DXGKRNL_FATAL_ERROR when im trying to install the bluetooth driver using Lenovo System Update Program or using the downloaded package "Realtek RTL8723BE Bluetooth version : 1.3.769.3"
    My OS is: windows 8.1 ENT
    From Event Viewer , i can only see this information event 
    Log Name: System
    Source: BTHUSB
    Date: 11/4/2014 12:28:43 PM
    Event ID: 18
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: xx
    Description:
    Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during start-up.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="BTHUSB" />
    <EventID Qualifiers="16389">18</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-04T10:28:43.015337000Z" />
    <EventRecordID>3291</EventRecordID>
    <Channel>System</Channel>
    <Computer>xxl</Computer>
    <Security />
    </System>
    <EventData>
    <Data>
    </Data>
    <Binary>00000800010000000000000012000540000000000000000000000000000000000000000000000000E000000000000000</Binary>
    </EventData>
    </Event>
    Best Regards,

    Hi Mwahab,
    I am glad to hear that your issue has been resolved after uninstalling the graphic driver, and now your query is that you wanted to if your system is shipped with additional graphic card.
    Below is the link where you can verify the system hardware configuration by giving the complete system MTM (Machine Type Model) number, if you provide us the MTM number we can assist on that.
    http://support.lenovo.com/us/en/products/search
    Hope this helps.
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • I can't install Windows 7 key over KMS host with WS 2012 R2

    Hi
    I have a KMS Host with Windows Server 2012 R2. I don't have problems installing keys for Windows 8, Windows 8.1, Office 2013, Windows Server 2012 R2. However, when I tried install keys for Windows 7, Windows 2008 R2 and Windows 2008, I have the next message:
    C:\slmgr.vbs /ipk <Windows 7 key>
    Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid
    I've installed the keys from the same source.
    Gary

    Hi
    I have a KMS Host with Windows Server 2012 R2. I don't have problems installing keys for Windows 8, Windows 8.1, Office 2013, Windows Server 2012 R2. However, when I tried install keys for Windows 7, Windows 2008 R2 and Windows 2008, I have the next message:
    C:\slmgr.vbs /ipk <Windows 7 key>
    Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid
    I've installed the keys from the same source.
    Gary
    For a KMShost with the OS=WS2012R2, you cannot, and, there is no need to, install any other Windows KMShost keys. The WS2012R2 KMShost key, by itself, will activate the KMShost OS, and will also enable the issuing of activations for ALL Windows KMSclients.
    Office KMS features are different, and do need to be installed for Office KMSclient activations.
    The error you are experiencing is expected, and is a result of your attempt to perform an unnecessary configuration step.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Connect SQL Server 2012 from Windows Server 2003 with native client 9.0

    Hi,
    I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
    Now I have the requirement to upgrade the SQL server from 2005 to 2012.
    My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
    As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
    So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
    Thanking you in advance! 

    Hi Soumya,
    Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
    Regards,
    Mike Yin
    TechNet Community Support

  • M500 120 GB mSATA hanging/crashing Windows 8.1 Ent after 1 year of use

    Hi, I purchased a M500 120GB mSATA disk June '14 from Amazon, and installed it in my Sony Vaio T-Series laptop.
    I have been using it ever since and it has been fine and speedy.
    Since last week, I noticed my laptop started hanging applications and then crashing without reason.
    At first I thought about some Windows update, since I did not install any application recently. I formatted and reinstalled Windows 8.1 ENT and then Windows 7 Professional and in all cases, I noticed that it would install fine, but after sometime, during normal operations, some random application ie Word, Excel, Google Chrome, IE, would hang by itself, and would not come back. The mouse pointer is showing the busy (spinning wheel) sign as well. Eventually, after much waiting, I would have to manually reset the laptop and then it would be fine again, until this starts again. Eventually I installed Windows 8.1 Ent on my HDD and everything went away. Yesterday, after doing some reading, I installed and ran CrystalDiskInfo and it says that my disk is 98% good. I dont understand the other parameters returned by the SMART function. I am attaching a screenshot here and hoping someone can diagnose it for me. 

    Hi bym007,
    Looking at SMART values I would say the drive is completely healthy. After clean OS install did you install any chipset and storage drivers? What is the exact model of your Vaio?

Maybe you are looking for