KMS Activation
I've been trying to set up my WinSer2008 kind of piecemeal since I am running a few swimlanes of my project concurrently. I't's been running i9tfor about two months. All ofa sudden I got a message when I signed in saying: Key Management Service (KMS) host could not be located in domain name system (DNS), please have your system administrator verify that a KMS is published correctly in DNS.I went to investigate. Finally I downloadedKey Management Service v1 1 for Windows Server 2003 Step-By-Step Guide.doc and KMSW2K3.exe to run the service. I got an error that there is not enough memory to run the app. This error usually is an euphemism for the fact that the OS version is too new for the exec which is the case. So the claim on the download website that it is for WinSer2003 Sp1 and Later is incorrect.What shall I do?I am an MSDN Pro subscriber, I got the WinSer2008 in mail as a DVD, so apparently I have to go thru the motions, right? I don't see any "volume" in my work however. Perhaps it is beyond the point?This is the link I used to download the files.Thanks for any help.
AlexB
November 14th, 2008 7:13pm
Hello Alex,This is MSDN correct?Did you change your product key to the MSDN product key?You are not prompted for a product during setup, to use the MSDN key you have to use the change the product key to your MSDN key. By default the MSDN Windows Server 2008 looks for a KMS server which doesn't sound like it applies in your caseThanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2008 9:15pm
Yes, this is MSDN. I don't remember changing any product key. It seems that when I installed I either put in the product key that I copied from MS Product Keys and Downloads site or it was not required (which as you understand is unlikely). I don't even recall.What shall I do about the message box with the error message then?
AlexB
November 14th, 2008 9:20pm
Hello Alex.The media does not prompt for a product key since MSDN uses Volume Media for Windows Server 2008.So unless you manually changed the product key after installation was done, you need to change to your MSDN key now.Click the start button.right-click on ComputerChoose propertiesLook for the Windows Activation sectionclick the change product key option.Or if you prefer command-line,click the start buttonClick All Programschoose Accessoriesright-click on Command Prompt and choose Run as Administratorwhile in the the elevated command promptrun slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxxwherexxxxx-xxxxx-xxxxx-xxxxx-xxxxx represents your MSDN product key.Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2008 3:32am
Thank you Darrel for instructions. I swear I did not change the key. There is no need for me to do this. My hands are full with my other developments. I guess what has happened and this is my observation that it may be the case of explanation for some my other troubles is that MS downloads upgrades and those change settings ever so slightly. I see it almost twice weekly after each upgrade on my Vista Ultimate. Every time I have to adjust this or that. Now it is the key. OMG!i will post back after I am done. I was correct. The Product key was totally bizarre. It is not the Product Key I entered. Now I remember clearly that I did it. But believe it or not I got an error:The Product Key you've entered will not work with this Edition of Widnows Server. You must either rung Windows Server Setup or enter a Windows Server Standard product Key.I wil check my DVD but I doubt the product key is there. I remember clearly that I copied it from the MS website. I actually copied two keys: one for Windows Server 2008 and the second one for Windows Web Server 2008 x64. They are identical. I forgot now the reason I got the second one. perhaps by mistake.What is my next step?There is a warning that I have 9 days left to straighten it out. I used the first method (GUI) not the command prompt.
AlexB
November 15th, 2008 4:40am
The last three characters of my product keyare9VJ.Now I tend to think that the installer did not ask me about the key perhaps.
AlexB
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2008 6:51pm
Hi Alex,
For product key issues, youd better contact your local Microsoft Customer Service for detailed information directly.
http://www.microsoft.com/worldwide/
Tim Quan - MSFT
November 17th, 2008 11:41am
Hello Alex,You need to change the product key.You will get this error message if you install using MSDN media for Windows Server 2008 and Windows Vista Enterprise and the product is not changed after setup completes.
Setup does not prompt for a product key.
Open an elevated CMD prompt and run slmgr /dlv
report back what is on the name field and what is on the Description field.Note what is listed as the last 4 digits of the product key, does it match yours?Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2008 6:12am
I explained in my previous post that the product key listed (thru HUI) has nothing to do with the product key I obtained from MSDN. I followed the list suggested Tom and got to MS Product Activation but could hot do it over the phone since they asked questions and I could not immedicately follow instructions since my situation appeared to not have matched what they suggested. I asked for "transfer" to an assistant but they cut me off because the system "overload."AlexB
November 18th, 2008 11:07am
Darrell Gorter said:
Hello Alex,You need to change the product key.You will get this error message if you install using MSDN media for Windows Server 2008 and Windows Vista Enterprise and the product is not changed after setup completes.
Setup does not prompt for a product key.
Open an elevated CMD prompt and run slmgr /dlv
report back what is on the name field and what is on the Description field.Note what is listed as the last 4 digits of the product key, does it match yours?
Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
Darrel, thank you.I posted my previous response earlier this morning, around 3AM, some temporary insomnia set in. Now I read your post more carefully.I did what you said.The partial product key does not match mine. After theslmgr /div run I got: B***2. I have no matching part in my product key for that.Name: Windows Server(R), ServerStandard Edition.Description: Windows Operating System -Windows Server(R)I will now try again activate it via the phone. I rethought my last night experience and hopefully I will do better this morning.AlexB
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2008 6:07pm
OK, I haven't called MS Product Activation Line yet. Instead I devoted a few hours this morning to reading on the subject and studying commands. The whole situation is much more clear to me and I successfully defined KMS Name with cmd prompt: slmgr -skms <name[:Port] | :Port>. It worked but still I cannot use it for activation. When I tried to use:slmgr -skms kms*****Server.******.com, I got an error:Error: 0xC004F039 The computer could not be activated. The Key Management Service could not be reached. Apparently I am still missing something. Either I will stumble on it in my further reading or perhaps, you, Darrel will give me a helpful hand. Thanks.AlexB
November 18th, 2008 7:59pm
Hello Alex,Is there anything else on the these descriptionlines, there should be more data on those lines:Name: Windows Server(R), ServerStandard Edition.Description: Windows Operating System -Windows Server(R)For example I have on mine:G:\DGG3>slmgr /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(TM) Vista, Enterprise edition Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channelThe last 5 digits areBFGM2, that is the generic product key that is used when you install volume license edition of Windows Server 2008 Standard edition.That key is published in the Volume Activation 2.0 Deployment guide.You need to change from the default installation key to your product key.from the elevated cmd prompt:slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxxThanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2008 9:17pm
Hi Darrel,Yes, there were many more lines with very long Product ID, etc, etc, etc.I provided what you asked me to. Later tonight I will post more.That key is published in the Volume Activation 2.0 Deployment guide.I have it and read parts of it. I will check more.Thanks. P.S. OMG, it is there! What a stupid character I am. But in the meantime I've learned a lot.Many thanks.
AlexB
November 19th, 2008 2:09am
Hello Alex,Mainly I want to see what is on the entire description line.That helps deteremine what key is installed, from what I have seen so far, the indications are that it is the default install key and you need to change the product key to your product keyThanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2008 3:08am
Hi Darrrel,I posted the Description line before when you asked:Description: Windows Operating System -Windows Server(R).There is nothing else on it. The whole message is very large, many lines with long strings of digits and it is impossible to copy it to Clipboard. In the meantime I tried to activate the server again and although the new key was accepted I got another error:The software licensing service reported that the computer cannot be activated. The Key management service KMS is not enabled.I did give it a name. I thought that it was tantamount to activation. Apparently it is not the case. In one episode before it complained that KMS was not named. So I named it. I will keep reading about it more.Thanks.
AlexB
November 19th, 2008 6:56pm
Darrel, I will need more help on that. I have downloaded numerous Step-byStep Guides long time ago (43 in all) and now added one more. I've been reading them but as you can imagine it is all confusing for me at this stage. I am a C# developer mostly in application area and TechNet stuff is not my forte. I do feel comfortable on a basic level of course but not much beyond that. I am sure it will be over in about two months. It was the same with Vista Ultimate more than 18 months ago when I first installed it.The things that confuse me is the duality of manuals. There are some that sound very useful but they pertain to 2003 version. I cannot seecorresponding names for 2008. I cannot find a basic description of Active Directory management for 2008 version, only for 2003.It is also puzzling that I can see numerous manuals related to Active Directory Rights management but nothing more basic.All my attempts to download and isntall managers and wizards for AD and KMS activation failed for various reasons, some of the attempts failed because the software was for 2003, others because some other causes, some of them very obscure. I download only MS stuff and neve go for 3-rd party software.I would appreciate if you help me.Thanks.
AlexB
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2008 8:07pm
Hello Alex,Have you tried changing your product key to the MSDN product key?Open an elevated CMD promptrun slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxxwherexxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your MSDN product key for Windows Server 2008.To run a cmd prompt elevated.Click StartClick All programsClick Accessoriesright-click on comand prompt and choose run as administrator.Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
November 20th, 2008 4:16am
Darrell Gorter said:
Hello Alex,Have you tried changing your product key to the MSDN product key?Open an elevated CMD promptrun slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxxwherexxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your MSDN product key for Windows Server 2008.To run a cmd prompt elevated.Click StartClick All programsClick Accessoriesright-click on comand prompt and choose run as administrator.
Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
Darrel, I've told you that I HAVE CHANGED It successfully. I changed it with Computer==>Properties==>Change Product Key.Forget about it.There is another problem that I've described. It is the next problem down the road.Am I speaking unclearly?Please read my posts.AlexB
Free Windows Admin Tool Kit Click here and download it now
November 20th, 2008 5:10am
Hello Alex,I reread the thread again, I am sorry but I do not see where you state that you changed the product key, I must have missed that point.The default key values was shown in the output.When you run slmgr /dlv does it show the last 5 digits of your product key now?The problem you are referring to is activating this machine.
The error messages you are getting are from the default key, not from your MSDN key.So again the indication is that the product key was not changed. Maybe I am unclear on what you are attempting to do.
So are you using MSDN media and an MSDN product key?Is this a single machine or do you have a number of machines to setup and activate.
Do you have a KMS host key and do you wish to use that key?
Do you have sufficient Volume License clientsmachines to achieve the count needed to use a KMS host key?
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
November 20th, 2008 9:59pm
Darrel, I understand it. I post for other people myself (in C# General primarily, you can see my four stars) but I am guilty of the same typical error. It is hard to catch other people's disposition. I do it all the time. I went to my post in question and highlighted what I said. Now I understand that it was drowned because it was so inconspicuos.I will follow what you've said and check on it. But I think I've changed. I got a message that it was chenged. If you could reread my post with the red highlight youwill see it.My server is on another location. I will be there in 4 hours.Thanks.
AlexB
Free Windows Admin Tool Kit Click here and download it now
November 20th, 2008 10:37pm
Darrel, I ran the command you suggested and inspite of what you've told me the product key (PK) has been changed. The last 5 characers of the new PK noware BFGM2. The command I ran is as per Darrel:slmgr /dlv.This command gives me many lines of info. I wish I could copy the whole thing and post it here. There is no way to easily copy it to Clipboard. You are aMSFT employee. You should pass it to the top decision makers as a suggestion that this MessageBox should be changed or a "Copy to Clip" button should be made available. I hate to write a routine for screen capture but if you want me to do it, I will do it. Perhaps I should do it anyway for other reasons as well. But please don't forget my request for "Copy to Clip" button, OK. It is a typical problem with many APIs. I don't know why they did it this way.Anyhow, that MessageBox also tells me that my License status: "Initial Grace Period" and the Time Remaining is 3060 minutes (2 days).There is an option in slmgr command: -rearm which stand for reset the licensing status of the machine. Shall I use it?Now I am quite confused about the issue of MSDN media and the Standard Windows Server PK. Yes, it is definitely MSDN media (DVD) (I got it in the mail from MSDN, I quoted the DVD # before in this thread), but when I initially (meaning first time around) put in MSDN PK it rejected it. I calledTechnical Professional Support: @ 800-936-4900 as well asTerminal Server Product Activation @ 888-517-2148 (I was directed to the latter by Technical Professional Support) they both could not figure out why the DVD did not accept MSDN PK. I gave them theMSDN PKand they marvelled at it. They said thePK was correct but the machine demanded Standard PK.
> Do you have a KMS host key and do you wish to use that key?I defined KMS host name. It is ksm1108server.alexb***.net. the ***** masks my real domain name registered with discountaps.net.KMS host key? What is it? How can I define it? As I told you, it is all most likely in the manuals. It is just too overwhelming for me to read all mass of this material at once and figure it out.
Do you have sufficient Volume License clientsmachines to achieve the count needed to use a KMS host key?Again, i need explanations. I am running this WinSer2008 half-heartedlyso to spek to gain experience before I set up a more formidable server on a real Intel server motherboard withraid arrays of SATA drives on my 4U Rackmount Chassis. It is just a partition at this point on my home development machine where I installed the server. I do dev work when I come home from my office at night. I intend to runthe WinSer2008 during my office hours when I use a different dev machine and during nighttime when this machine is currentlyidle.In any case scenario it will be only ONE machine at a time physically and logically.What do you mean by count? A count of what? A count of machines? My count is just ONE. Is it not enough to run a server?I feel like a kindergarten kid asking his mom: Mom, what is this? :)I thinks I've exhausted all possible issues at this moment and nothing is left in the lurch, although there are sill many in the dark. :)Darrel, I need some meaningful input. I am sorry.Many thanks for trying to help a mentally retarded:)
AlexB
November 21st, 2008 6:38pm
Hello Alex,Sorry I missed the post where you stated that you changed the product key.The indications are that the product key was not changed.In fact the last five digits that are displayed are from the generic product key, they should be part of your product key that you entered.Is the product key you are using? this should not be your MSDN key.TM24T-X9RMF-VWXK6-X8JC9-BFGM2That is the generic key documented inVolume Actgivation product guide, which should not be the key that you are using.http://technet.microsoft.com/en-us/library/cc303280.aspxFrom your responses, you should not be using KMS, you do not need to setup a KMS host machine. You do not have enough machines to warrent this and since you only have MSDN media, a KMS host key is not available to you. I was just trying to make sure when I asked about KMS.
Slmgr - rearm will reset the activation grace period back to 60 days ( 60 days for Server, 30 days for Vista), this can only be done three times, but it does give you an additional 60 days to resolve any issues.The problem is that the product key that is showing does not appear to be the one you changed it to, the product key in display should show the last 5 digits of your MSDN product key.To capture the output from the dialog box, with the dialog box in focus, use Ctrl-C to copy the text, then Ctrl-V to paste the text. I tested that with that dialog box and it worked fine for me. Can you try to install the product key from an elevated cmd prompt rather than from the GUI?slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxxDo you get any errors? does this change the output where the last five digits of the product key are displayed to your product key's last 5 digits?Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2008 11:25pm
Darrel hi,I tried to change the initial product tkey to MSDN product key long time ago and I did it three times, every time with the GUI. Every time it was rejected. The only PK that'sbeen accepted is the one you just showed. It gave me a message that the product key was OK.I always copy everything with Ctrl+C. BTW when I said that the key was rejected it means that the message was:This Product Key is for a different version of the server. DFFERENT VERSION! It did not say that it was invalid or something. Then the message went: insert the proper product key or talk to your system administrator.......How do you like it?We are still talking two different languages:) I understand it is hard for you to comprehend all this since it is so absurd. When I called Product Support, they just marvelled.I will reread your post later tonight and take some action.Thanks.AlexB
November 22nd, 2008 12:06am
Hello Alex,The output dialog box for slmgr will either use cscript or wscript as the default handler,If cscript is the default handler in the elevated cmd pompt it outputs txt rather than the gui display.It it outputs the gui dialog box, it is probably using wscript as the handler. When I use wscript to see the gui display the gui, if I use Crtl-C I can copy output from the slmgr screen.
but that is not the issue, we are trying to address. If the key is not valid, they need to ship you a need key, was MSDN asked if you could get a different key?
Could you send me the key so I could check it? Use my first name and last intialand microsoft.com of course.Send me an email that I can reply to first, before you send the keyThanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2008 2:22am
Darrell hi,I just reset the server for another grace period with slmgr -rearm. I also sent you the key, I hope you received it if not, let me know. I also went down my memory lane and discovered why all this mess happened in the first place.When I put the Dvd in the drive and ran the install it presented me with a few options. I remember three of them. There were more but I don't recall what they were. The ones I recall were: Windows Server Standard, Windows Web Server and Windows Server Enterprise I believe. After some hesitation I chose Standard.Was I supposed to make a different choice? If so, how can I extricate myself from this mess?Do you consider it a realistic explanation?Thanks.AlexB
November 22nd, 2008 10:48pm
Darrell, thank you. I am happy to report that the new key worked and I got a message: "Activation was successful." An emblem of true Windows showed up and the message said that I was eligible for all upgrades, etc.I swear, I saw two Editions having the same PK when I first tapped the site. I think they made a mistake then and it has since been corrected. This is my suspicion. I will try to remember this experience and next time if a similar situation arose I will know what to do.Many thanks.AlexB
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2008 7:26pm
Hello Alex,Thanks for the followup and I am happy that you were sucessfully activated.
It certainly is possible that the same product key was listed under multiple editions.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
November 25th, 2008 9:26pm


