On a server 2008 R2 enterprise Edition machine, I am attempting to manually set the KMS server value as follows: (from an elevated command prompt) cscript c:\windows\system32\slmgr.vbs -skms <FQDN-of-KMS-server> However, none of the KMS client service options (such as -skms) are available. Only the options for the KMS service are available. So i cannot use the -skms switch. The KMS server is up and is successfully activating other machines. any guidance would be appreciated.--- ian

Hello Ian, This is normal on a KMS server. You should have no need to activate the KMS server or use any client options because the KMS Host Key acts as a license for the server as well if I remember correctly. Regards, Andrew

I am not attempting to set up this server as a KMS server -- I wish for it to be a client of another server that is functioning as the KMS server. thanks,--- ian

Hi, First please run slmgr.vbs /ipk KmsKey on the machine to convert it from a KMS host to a KMS client. Tim Quan

Hi Tim, I ran slmgr.vbs /ipk with my volume license key and the got a success. I still don't have the KMS client options. Rebooted but the problem persists. Any additional help would be appreciated! --- ian

Hi, Please run slmgr.vbs /ipk 489J6-VHDMP-X63PK-3K798-CPX3Y. After that, please run slmgr.vbs /dlv and paste the result. Tim Quan

Hi Tim, thanks for your help with this. I ran slmgr /ipk 489J6-VHDMP-X63PK-3K798-CPX3Y but the OS tells me it is an invalid key --just FYI. Here is the result of the slmgr.vbs /dlv : Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Software licensing service version: 6.0.6001.18000 Name: Windows Server(R), ServerEnterprise edition Description: Windows Operating System - Windows Server(R), VOLUME_KMS_B channel Activation ID: 56df4151-1f9f-41bf-acaa-2941c071872b Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 55041-00152-339-003119-03-1033-6001.0000-1782011 Installation ID: 011671737776643404479481865096840713106850753156802062 Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48189 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48190 Use License URL: http://go.microsoft.com/fwlink/?LinkID=48192 Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48191 Partial Product Key: 24MWC License Status: Initial grace period Time remaining: 81000 minute(s) (56 day(s))--- ian

Hi, Thank you for the reply. “Software licensing service version: 6.0.6001.18000” indicates you are running Windows Server 2008 instead of Windows Server 2008 R2. As 489J6-VHDMP-X63PK-3K798-CPX3Y is for Windows Server 2008 R2 Enterprise, it is not suitable for your system. Now please run slmgr.vbs /ipk YQGMW-MPWTJ-34KDK-48M3W-X4Q6V. Then check the result. Tim Quan

Hello, That is an installation of Windows Server 2008 and the key listed above with /ipk was for Windows Server 2008 R2 Enterprise The KMS client keys are version specific as well as edition specific, the KMS host keys are not which is why the machine above has the Windows Server 2008 R2 KMS host key installed. This version number is for Windows Server 2008 Software licensing service version: 6.0.6001.18000 Use this key below Server Windows Server 2008 Enterprise YQGMW-MPWTJ-34KDK-48M3W-X4Q6V Link to keys http://technet.microsoft.com/en-us/library/ff793421.aspx 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

hi Tim, thanks very much for your help. I can now set this machine to use our kms server for activation, but activating gives the error '0xC004F042' = 'the software licensing service determined that the specified KMS cannot be used.' The kms server is activating other clients on our network, however. here is the result if the /dlv switch: Software licensing service version: 6.0.6001.18000 Name: Windows Server(R), ServerEnterprise edition Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel Activation ID: c1af4d90-d1bc-44ca-85d4-003ba33db3b9 Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 92516-00152-082-250088-03-1033-6001.0000-1802011 Installation ID: 010232517343280176657670043522802623522821580241350615 Partial Product Key: X4Q6V License Status: Initial grace period Time remaining: 86400 minute(s) (60 day(s)) Key Management Service client information Client Machine ID (CMID): 6839f4fe-db77-4fc4-981f-a05c0667908f Registered KMS machine name: kms.cc.columbia.edu:1688 KMS machine extended PID: Activation interval: -1 minutes Renewal interval: -1 minutes --- ian

Hi, 0xC004F042 indicates there is a mismatch between the KMS client and the KMS host. To work around this issue, verify that a beta version of the KMS client is not being activated by a release version of the KMS host. Or, verify that a release version of the KMS client is not being activated by a beta version of the KMS host. If your KMS host and client are not beta systems, please run slmgr /dlv on the KMS host and paste the result. Are your other clients running Windows Server 2008 Enterprise? Tim Quan

Tim, it turns out that the KMS host had recently been moved to a VM and had not yet reached its 5 client activations yet. After spinning up 5 clients and activating them, I was able to activate my server. thanks for the help.--- ian