KMS server

I built KMS server and install VAMT for windows 7 activation. I’ve imported computer names from AD when I right click on a computer name – Update Status –Current Credential and I have a message attached “Unable to connect to the WMI service on the remote machine”. What I have to configure in desktop level and VAMT to activate Windows 7. Additional details, I put KMS product key to my answer file (unattend.xml).

 
Itsa56Asked:
Who is Participating?
 
Ivano ViolaConnect With a Mentor System AdministratorCommented:
Good seeing you again!

As long as your media is a volume license installation, the setup key is installed by default, which makes the system a KMS client. It should automatically look for a KMS server in DNS.

If you want to specify a KMS server in your unattend.xml file, you need to add a command in the AsynchronousCommand section under "Microsoft-Windows-Shell-Setup"
Microsoft-Windows-Shell-Setup - LogonCommands - AsynchronousCommand
Example:

            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Description>KMS Authentication</Description>
                    <CommandLine>c:\windows\system32\slmgr.vbs -skms KMS.SERVER.HERE</CommandLine>
                    <Order>1</Order>
                </SynchronousCommand>
            </FirstLogonCommands>

Let me know how you make out.

0
 
Ivano ViolaConnect With a Mentor System AdministratorCommented:
Itsa,
If you used the KMS Windows 7 Install media then then you don't have to specify the product key in your unattend.xml file (leave the product key blank). The Windows 7 installation already has the KMS key included. You need to make sure your KMS server is registered in DNS. The Windows 7 clients will automatically check DNS for the activation server and activate automatically. You also have to make sure the KMS server is listening to port 1688.

http://certcollection.org/forum/topic/8746-setup-a-kms-server/
0
 
Itsa56Author Commented:
Nice to hear from you again ivanoviola.
How can I specify the name of KMS server in my unattend file. The other word, how PCs will know KMS server is there.
FYI, yes I installed Windows 7 pro from media which I downloaded from https://www.microsoft.com/licensing/servicecenter/ 
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Itsa56Author Commented:
I did follow your instruction on my unattend file. It comes up without error after sysprep, but it's still not activated Win7. I've scaled down the problem.
1. PCs tries to talk to wrong server. I fixed this issue with running  c:\windows\system32\slmgr.vbs /skms KMS
2. KMS server is not responding to PCs request for activation.
Any idea why KMS's not responding.
0
 
Ivano ViolaConnect With a Mentor System AdministratorCommented:
The KMS server will only start activating clients when it reaches a threshold of 25 clients. Run the following command on a command prompt on the KMS server:
slmgr /dlv
This is a section of the output:
 KMS outputIf everything is running as it should your current count should start to go up. Once the count reaches 25, all clients that have requested activation will activate. Any requests for activation after 25 will occur immediately. It stops counting at 50. Also, make sure the KMS server is listening to port 1688.
0
 
Itsa56Author Commented:
At the moment I don't have 25 PCs yet. However when I run slmgr /dlv on KMS server. I got the output attached. The current count is still :0 , even I already have more than 20 clients.  

 
Kms-output.docx
0
 
Ivano ViolaConnect With a Mentor System AdministratorCommented:
Try changing the the product key on one of the computers using one of the client KMS keys listed in this link (matching your OS):
http://technet.microsoft.com/en-us/library/ff793406.aspx
When done activate the computer by running cscript slmgr.vbs /ato at a command prompt.
0
 
Ivano ViolaSystem AdministratorCommented:
Forgot to mention.....check the KMS client to see if the count changes to 1.
0
 
Itsa56Author Commented:
It did not regonise the client KMS key. It came with error Code 0xC004F074. However when I added the same key in KMS host and ran update Status - Current Credential -the output is Successful Installed product key. But in Genuine status shows Non Genuine.
0
 
Itsa56Author Commented:
I've worked it out with my KMS server. Now it's working.
0
 
Ivano ViolaSystem AdministratorCommented:
Hi Itsa,

Sorry, have been away for Thanksgiving. What was causing the problem?
That's great you got it working.

IV
0
 
Itsa56Author Commented:
1. My server 2008 is not R2.
2. I need to activate Server 2008 R2 licence with microsoft first and then apply virtual licence key on client PCs. I also need to modify my unattend file set Skip rearm to 0 (not 1).
0
 
Ivano ViolaSystem AdministratorCommented:
I use server core for my KMS server so I forgot about the R2. The skip rearm to 0 is important as the machines will then be assigned different CMID's. Every time a KMS client activates, the rearm count goes to 1, which actually means you can sysprep the same machine multiple times.

Well done.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.