none
Vista Ultimate as a KMS Host?

    Question

  • Today I was working on a brand new Windows 7 x64-bit machine that suddenly started saying it wouldn't activate because our KMS server says it doesn't have enough Windows 7 machines contacting it.  When I looked into this, I came upon the realization (through checking our DNS server for _VLMCS service entries) that instead of the 2 KMS Hosts we should have, we actually have 4.  Two were ones I set up, one I suspect was a server activated using the KMS Host key instead of a MAK key, but the fourth one is a real head-scratcher.....a Vista Ultimate machine we have handling TV signal distribution is injecting _VLMCS entries into DNS!

    I've been searching and reading for how this could be possible, and more importantly, how to kill it, but I haven't had much luck.

     

    What should I do?


    • Edited by Brett242 Thursday, December 08, 2011 9:18 PM
    Thursday, December 08, 2011 9:17 PM

Answers

  • Well, I did the method 2 to rebuild the license store, rebooted, and then Windows said it was not genuine and wanted me to re-enter the product key.  Problem is, this machine was set up so long ago, I'm not sure what the key is that was used.  Looks like we'll just have to back it up and reformat it with Windows 7.  Wasn't quite the way I wanted to solve the problem, but I'm sure this will take care of it.

    • Marked as answer by Brett242 Thursday, March 22, 2012 10:09 PM
    Wednesday, March 21, 2012 6:17 PM

All replies

  • "Brett242" wrote in message news:71edbca3-6ee7-4343-b86b-6406abe0822c...

    Today I was working on a brand new Windows 7 x64-bit machine that suddenly started saying it wouldn't activate because our KMS server says it doesn't have enough Windows 7 machines contacting it.  When I looked into this, I came upon the realization (through checking our DNS server for _VLMCS service entries) that instead of the 2 KMS Hosts we should have, we actually have 4.  Two were ones I set up, one I suspect was a server activated using the KMS Host key instead of a MAK key, but the fourth one is a real head-scratcher.....a Vista Ultimate machine we have handling TV signal distribution is injecting _VLMCS entries into DNS!

    I've been searching and reading for how this could be possible, and more importantly, how to kill it, but I haven't had much luck.

     

    What should I do?


     
     
     
    I have NO idea whether it will help – but please post an MGADiag report for the errant machine. It may give us some idea as to what happened.
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
      - **in your own thread**, please
     
    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine, but do NOT quote the Key on the sticker!
    http://www.microsoft.com/howtotell/content.aspx?pg=coa

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 08, 2011 10:01 PM
  • Hi, if you have machines operating with KMShost pkeys, and you don't want them to be KMShosts, you need to "change" the current pkey on that machine to be a KMSclient pkey, or a MAK pkey. This will disable the KMShost function of the machine.
    You should then clean up the unnecessary DNS records in the _vlmcs zone.

    BTW, Server03, Vista/08 & Win7/08R2 can all be KMShosts... (there are some limitations e.g. Vista/7 cannot activate Servers)


    Don
    • Edited by DonPick Saturday, December 10, 2011 1:52 AM
    Saturday, December 10, 2011 1:49 AM
  • Hello,

    Yes I want to see the MGAdiag output as well.

    Windows Vista Ultimate is not supposed to be able to become a KMS host( only Windows Vista Professional and Windows Vista Enterprise)

    To kill it you would need to change the product key installed to a Retail or OEM key for Windows Vista Ultimate, activate with the new product key and reboot.  It would no longer be a KMS host machine, but you may have to manually remove the DNS entry from your DNS server.

     


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    • Marked as answer by Sabrina Shen Thursday, December 15, 2011 2:56 AM
    • Unmarked as answer by Brett242 Tuesday, January 24, 2012 5:05 PM
    Sunday, December 11, 2011 12:23 AM
  • Here is the output of MGADiag:

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-GB77H-W9WPC-V6CD8
    Windows Product Key Hash: QHx6z3yHyiYMef8q/M4gUysgL3Y=
    Windows Product ID: 89580-378-8126972-71901
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6002.2.00010100.2.0.001
    ID: {F3141CE6-2833-4EF4-B5C9-28F5658D09C3}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Vista (TM) Ultimate
    Architecture: 0x00000000
    Build lab: 6002.lh_sp2rtm.090410-1830
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6002.16398

    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: 109 N/A
    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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>{F3141CE6-2833-4EF4-B5C9-28F5658D09C3}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010100.2.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-V6CD8</PKey><PID>89580-378-8126972-71901</PID><PIDType>5</PIDType><SID>S-1-5-21-3751951819-1228981564-2619953409</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>080015 </Version><SMBIOSVersion major="2" minor="5"/><Date>20080530000000.000000+000</Date></BIOS><HWID>9F313507018400F2</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/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, Ultimate edition
    Description: Windows Operating System - Vista, RETAIL channel
    Activation ID: 30fab9cc-8614-4339-989f-7ce61fb7a5c4
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89580-00142-378-812697-00-1033-6001.0000-1182009
    Installation ID: 022193038551942341334284064772716103192423884332395892
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: V6CD8
    License Status: Licensed

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: NgAAAAEAAgABAAEABAACAAAAAQABAAEA6GEmUboAAHWWkpb2CHySvHJk8vTwIoIyyuAuotbH

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            053008        APIC1459
      FACP            053008        FACP1459
      HPET            053008        OEMHPET0
      MCFG            053008        OEMMCFG
      WDRT            053008        NV-WDRT
      OEMB            053008        OEMB1459
      INFO            053008        AMDINFO
      NVHD            053008        NVHDCP
      SSDT            A M I         POWERNOW



    Wednesday, December 21, 2011 4:11 PM
  • This machine cannot be activated by a KMS server - because there is no SLIC table in the BIOS to prove validity of a prior Windows install.

     

    It's 10 days since the initial post - perhaps you have some more data that would be useful?

     


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 21, 2011 7:23 PM
  • following on from this, on the Vista machine, if you could run "cscript slmgr.vbs /dlv" and post the output here?

    this article details what it should look like: http://technet.microsoft.com/en-us/library/ee939272.aspx


    Don
    Wednesday, December 21, 2011 9:57 PM
  • Hello Noel,

    The rule is for Volume License media only, and this is not volume license media.

    If it was volume license media, the check is does a SLIC table exist, if it does then a Windows Marker needs to be present. If there is no SLIC table there cannot be Windows Marker so no check can be done, so machines could be a KMS client.

     

    But to get back to the issue this:

    Actually this machine is runing with Retail actvation, plus it's Windows Vista Ultimate for which no Volume licensing is available. This is not a KMS machine, either client and host and cannot be one ever.

    Why do we think it's one?

     


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    Wednesday, December 28, 2011 9:05 PM
  • Darrell is correct !!

     

    this Windows Vista machine is using Retail copy of licesence and it is already activated. we can see that in the MGAdiag report:

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, Ultimate edition
    Description: Windows Operating System - Vista, RETAIL channel
    Activation ID: 30fab9cc-8614-4339-989f-7ce61fb7a5c4
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89580-00142-378-812697-00-1033-6001.0000-1182009
    Installation ID: 022193038551942341334284064772716103192423884332395892
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: V6CD8
    License Status: Licensed

    If there is the VLMCS entry for the same machine we can delete that record from DNS.

    It may be possible that earlier we have installed the KMS host key, which would have created that entry in the DNS.

    because on vista ownwards just by changing the product key we can change the channel.

     


    Thanks, Laxmi
    • Edited by Miracle' Thursday, December 29, 2011 1:47 PM
    Thursday, December 29, 2011 1:42 PM
  • Darrell,

    I believe that this machine thinks it's a KMS server because around the time I originally posted this thread, I deleted the _VLMCS entry for this computer out of our DNS server.

     

    I just checked DNS again, and this computer has once again inserted a _VLMCS entry for itself as of 1/17/2012 at 12:00 PM.

    If a Vista Ultimate Retail-activated computer is impossible to be a KMS host, then why is the machine injecting KMS host entries into DNS?

    Tuesday, January 24, 2012 5:05 PM
  • following on from this, on the Vista machine, if you could run "cscript slmgr.vbs /dlv" and post the output here?

    this article details what it should look like: http://technet.microsoft.com/en-us/library/ee939272.aspx


    Don

    can you post this information for us please?
    Don
    Tuesday, January 24, 2012 8:46 PM
  • Hello Brett,

    On the Vista Ultimate machine, open the application event log and look for Event 12293 and or event 12294.

    Do you see any of those events?

    There should be no way this machine is publishing to DNS, you may want to check to make sure there are not duplicate computernames.

    can you do a nslookup -type=all _vlmcs._tcp from an elevated cmd prompt

    then check that the IP addresses match this machine's IP address. 


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    Tuesday, January 24, 2012 9:00 PM
  • Sorry for the delay in responding, we had a major network SNAFU occur a couple of weeks ago that threw things in turmoil when we had to move DHCP from a Windows Server to one of our routers....was waiting for the dust to settle and things to get new IP's...

    I logged into the Vista Ultimate machine in question and on the very first screen of the application event log, I found an event 12294 that occurred at 12:54:39 PM today:

    "Publishing the Key Management Service (KMS) to DNS in the 'bucolor.com' domain was successful."


    Digging further in the log, this appears to be happening daily at 12:54PM.  No event 12293's found, though.
    • Edited by Brett242 Friday, February 10, 2012 9:30 PM
    Friday, February 10, 2012 9:27 PM
  • This information was posted a couple of responses above yours.
    Friday, February 10, 2012 9:32 PM
  • I logged into the Vista Ultimate machine in question and on the very first screen of the application event log, I found an event 12294 that occurred at 12:54:39 PM today:

    "Publishing the Key Management Service (KMS) to DNS in the 'bucolor.com' domain was successful."


    Digging further in the log, this appears to be happening daily at 12:54PM.  No event 12293's found, though.

    So this confirms your Vista Ultimate machine is acting as KMShost and successfully publishing itself into your DNS, advertising its KMShost service.
    you could dig into why it has a KMShost product key installed in it, and consider changing that to a KMSclient pkey or a retail pkey or whatever. unless you really want to pursue the matter of "why is it doing that, when it's not supposed to be *able* to do that"

    Don

    Friday, February 10, 2012 10:58 PM
  • Mainly, I just want that Vista box to stop messing with my KMS stuff.

    Also, to address your suggestion to change the machine to a KMS Client key or Retail key, if you look up to the top of the thread in the MGADiag output that I posted, it clearly says the machine is licensed with a Retail key.

    Any other ideas?

    • Edited by Brett242 Wednesday, February 15, 2012 10:16 PM
    Tuesday, February 14, 2012 8:36 PM
  • Hello,

    Can you open the registry and look under this key location

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL

    Is there an entry for DnsDomainPublishList and what value is it set at if it exists

    I don't think it should exist on this system, but if it does the value should be zero.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Thursday, February 16, 2012 8:11 PM
  • Darrell,

    The key is present, but I don't see anything called "DNSDomainPublishList".  The only values under that key are SkipRearm (0), VLActivationInterval (120), VLRenewalInterval (10080) and WAUSetupLocation (null).

    Thursday, March 01, 2012 5:30 PM
  • Hello Brett,

    Well there shouldn't be a key since this should not be a KMS host, but that would be a key for publishing if it was a KMS host.

    Let's try rebuilding the license store

    See this article, method 2 for steps on how to do that.  There is a FIXIT in the article for those steps.

    978305 Error 0xC004E002 during activation for Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;978305


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Saturday, March 03, 2012 11:45 PM
  • Well, I did the method 2 to rebuild the license store, rebooted, and then Windows said it was not genuine and wanted me to re-enter the product key.  Problem is, this machine was set up so long ago, I'm not sure what the key is that was used.  Looks like we'll just have to back it up and reformat it with Windows 7.  Wasn't quite the way I wanted to solve the problem, but I'm sure this will take care of it.

    • Marked as answer by Brett242 Thursday, March 22, 2012 10:09 PM
    Wednesday, March 21, 2012 6:17 PM