For KMS clients to be activated, do you have to join them to the domain or they can be activated if they are on the same subnet as KMS host, as workgroup clients?

Answered For KMS clients to be activated, do you have to join them to the domain or they can be activated if they are on the same subnet as KMS host, as workgroup clients?

  • Sunday, January 04, 2009 3:15 PM
     
     
    Thanks in advance.

All Replies

  • Monday, January 05, 2009 1:45 PM
     
     
    ????
  • Wednesday, January 07, 2009 2:41 AM
     
     
    Hello Undying Lament,
    Answered this in the server forums, no they do not need to be joined to the domain.  Workgroup clients can be KMS activated
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
  • Saturday, January 10, 2009 8:40 AM
     
     
    Thanks. much appreciated
  • Thursday, February 05, 2009 12:59 PM
     
     Answered
    They don't need to be joined but you need to assign the KMS host manually to them.
    • Marked As Answer by Undying Lament Thursday, February 05, 2009 12:59 PM
    •  
  • Thursday, April 30, 2009 8:43 PM
     
     
    How is this done...using the -skms option?  If so where does this option come from?

  • Friday, May 01, 2009 1:00 AM
     
     
    Hello Wes,
    Yes you set this by running slmgr /skms on the client machines.

    1.      At the command prompt, type one of the following options and press Enter:

    a.  To assign a KMS host using the host's FQDN, type:
    cscript \windows\system32\slmgr.vbs /skms <KMS_FQDN>:<port>

    b.      To assign a KMS host using the host's version 4 IP address, type:
    cscript \windows\system32\slmgr.vbs /skms <IPv4Address><:port>

    c.       To assign a KMS host using the host's version 6 IP address, type:
    cscript \windows\system32\slmgr.vbs /skms <IPv6Address><:port>

                       d.    To assign a KMS host using the host's NETBIOS name, type:
              cscript \windows\system32\slmgr.vbs /skms <NetbiosName><:port>

    Documented in the Deployment Guide
    http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en

    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
  • Friday, May 01, 2009 3:48 PM
     
     

    Darrell,

    When I run the command above (using b.) I get an "Invalid Parameter" error message.  I also tried using cscript \windows\system32\slmgr.vbs -skms <IPv4Address><:port> but I get "-skms" server not available.  If I try with the - or / skms behind the ip address I get 0x8000706BA or Invalid parameter which shows the possible command line arguments. 

    How come when you do a \windows\system32\slmgr.vbs -? "-skms" does not show up in the list of potential arguments?

    Thanks in advance,
    Wes

  • Friday, May 01, 2009 5:06 PM
     
     
    Hello Wes,
    What OS are you running this on?
    Windows Vista or Windows Server 2008?
    What is the output from slmgr /dlv?
    Are you running an elevated Command Prompt ( right-click on the command prompt link and run as administrator)?
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
  • Friday, May 01, 2009 5:24 PM
     
     

    Hi Darrell,

    The KMS server is running on windows 2003 Enterprise Service Pack 2.  The client I am trying to activate is running Windows Vista Business.  I have also tried running the server on Vista Business N with similar results.

    As far as the output from /dlv on the server....there are a lot of numbers, some URLS and a Partial Product Key.  Below are what I think would be the meat and potatoes of the output.

    License Status: Licensed

    Key Management Service is enabled on this machine

    Current count: 0 (I know I need 25....but am looking for the error code that tells me this)

    Listening on Port: 1688

    DNS Publishing enabled

    KMS Priority: Normal

    On the Vista Business client side the Partial Product key is the same as the server.  It says that we are in the initial grace period and that I have 27 days remaining. 

    I hope this helps.....let me know if you need any additional information.  I really appreciate any help.

    Wes

  • Friday, May 01, 2009 7:15 PM
     
     
    Hello Wes,
    You run the slmgr /skms on the client machines, not on the KMS host machine. 
    Essentially you are setting the value on that machine telling it what the KMS host machine( Windows Server 2003 machine) is.
    Windows Server 2003 does not KMS activate so it has no need to have the /skms option set.  Windows Server 2003 cannot be a KMS client.  So the option for SKMS should only appear on the KMS client machines


    The partial product key on the KMS client machine should match what is listed in the Deployment Guide from this download link
    KMS Client Setup Keys section

    http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
  • Friday, May 01, 2009 8:43 PM
     
     
    Darrell,

    I am running the slmgr /skms on the client machines (Vista) but it is not working.  When I look at the output from the slmgr /?, /skms is not one of the choices.  Is there something wrong with my version of slmgr?  Is there something else that I need to do to get the /skms option (i.e., service pack 1, etc)?  I really appreciate your responses.

    Wes
  • Friday, May 01, 2009 8:50 PM
     
     
    Hello Wes,
    What is the size and date of your slmgr.vbs on your client machines?
    It should have been present in RTM but I would advise using SP1.
    It's just a script file so you can open it in notepad and check if the skms option is listed inside the file
    Since it's a script file I don't think there is a version number.
    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
  • Friday, May 01, 2009 9:04 PM
     
     

    Darrell,

    Thanks again.  The size is 61,618 and its date is 10/3/2006.  I noticed that there is an "skms" variable within the script.  It just doesn't show up in the usage when i run slmgr /?.  Is there a later and greater version of this script?  If so can you send it to mailto:wes.crews@nexlevelit.com?

    I have tried to install service pack 1 but it hasn't successfully finished yet and I have had to restore twice. 

    Thanks,
    Wes

  • Friday, May 01, 2009 10:25 PM
     
     
    Darrell,

    Thanks for all your help!  Reading the script was the key.  The problem was we were using the KMS Server key rather than a client key on the clients so that the -skms option was not available.  Once I figured that out the rest became easy!  Thanks again.

    Wes
  • Friday, May 01, 2009 10:51 PM
     
     
    Hello Wes,
    slmgr /dlv
    I was looking for this output specifically from your client machine:
    C:\Windows\System32>slmgr /dlv 
                                                   
    Microsoft (R) Windows Script Host Version 5.7                                 
    Copyright (C) Microsoft Corporation. All rights reserved.                                                                                                     Software licensing service version: 6.0.6002.18005                            
    Name: Windows(TM) Vista, Enterprise edition                                   
    Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channel       

    From the Deployment Guide
    http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en
    Windows Vista Professional.
    Your partial product key listing should be 2V3X8
    If you used your KMS host key on this machine, it may think it's a KMS host machine so the option may not be present.


    Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights