Jump to content

Setting up a KMS - getting close to rampaging...

localzuk

By localzuk
in Windows Server 2008 R2

 Share

Recommended Posts

localzuk

localzuk

Posted
Posted

I'm currently setting up the infrastructure to support Windows 7 when we roll it out this summer, and one of those tasks is setting up a KMS host.

 

I'm running slmgr.vbs /ipk and consistently am getting an error 0xC004F015. I don't understand... the instructions for it are pretty washy it seems.

 

What am I doing wrong. I've set up a blank 2k8 R2 server, updated it fully and it is running with a MAK key itself. I am then putting in the Windows 7 Pro KMS key we get through our EES license.

 

Am I using the wrong key somewhere?

Quackers

Quackers

Posted
Posted
What Server are you doing this on? Sounds like your not running it on a Server running KMS 1.2 , if your doing it in Server 2008 R2 it should just work out the box, if not you will need to download an updated version of the KMS Server to take the Windows 7 keys i believe.
sted

sted

Posted
Posted
if all else fails set up a win 7 vm and just feed it yor kms key istant kms server (jus give it a static/reserved )ip
sted

sted

Posted
Posted

yup if your server is activated with a 2008r2 kms key you shouldnt need to do aything other than allow kms trough the firewall

 

try running

 

cscript.exe C:\Windows\System32\slmgr.vbs /dlv > "c:\Users\whoever\Desktop\kms.txt"

 

and see what it says it possible its already done wihout you realising it

Jamo

Jamo

Posted
Posted

This threw me when i was trying to set it up.

 

On the MS Vol licence site

 

 

Licenses->Relationship Summary and then click the licence agreement and select the product key tab.

 

Install the Product key for your KMS version of Server 2008r2 using the command:

 

cscript C:\windows\system32\slmgr.vbs /ipk

 

 

then to activate the KMS host, enter:

 

 

cscript C:\windows\system32\slmgr.vbs /ato

 

 

That should be it, it will publish iteself in DNS and the clients should pick it up. You have to have 30 clients to get it going though, I just made 30 virtual hosts. If you run:

 

cscript c:\windows\system32\slmgr.vbs /dlv

 

You should see the client count increasing :)

 

 

 

See this for more KMS info, its so badly documented. Basically its setup with the right version of server OS ensuring that your version of MS Server can activate all your clients (usually that is ok with standard, we have a datacenter licence so have had to migrate the KMS role to a datacenter server to keep up!) then thats it!!

 

How to Choose the Right Volume License Key for Windows

  • Thanks 2
localzuk

localzuk

Posted
  • Author
Posted

Ok, so I will start again and set up 2k8 R2 datacentre instead of standard.

 

Stupid complex system. What happened to Windows having GUIs for everything?

SYNACK

SYNACK

Posted
Posted
It's ashame and weird that your agreement does not have access to a KMS_B key as that just works, you may be able to use the datacentre key on the standard server though as it should activate everything below it including standard.
Jamo

Jamo

Posted
Posted

You can't use the datacenter key on standard as such, but you can do an inplace upgrade. Requires restarts and things, I have done it to 3 servers here with no problem:

 

 



To do this you just need to use the DSIM tool which is included with Windows

Dism /online /Set-Edition:ServerEnterprise /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

 

Note that you can check which versions you can upgrade to by running: Dism /online /Get-TargetEditions

 

 

Note that for KMS client product keys (ie ones that you can use to ensure they contact the KMS server for activation) see this article.Note this is useful for upgrading clients from Standard to Datacenter

Example

 

The below example works for our servers. Remember that the command requires a restart and takes around 10 mins.





dism /online /Set-Edition:ServerDatacenter /ProductKey:xxxxxxxxx

localzuk

localzuk

Posted
  • Author
Posted
It's ashame and weird that your agreement does not have access to a KMS_B key as that just works, you may be able to use the datacentre key on the standard server though as it should activate everything below it including standard.

 

Standard doesn't accept a Datacentre key, it says you have to use a standard key...

 

Where would I find this KMS_B key. The licensing site doesn't list that anywhere from what I can see!

localzuk

localzuk

Posted
  • Author
Posted
Strange that your EES licence doesn't show one. Ours looks like this

 

[ATTACH=CONFIG]14518[/ATTACH]

 

Maybe an email to M$ would get it sorted?

 

That's what ours looks like, but only for datacentre. Standard and Enterprise both only list MAK keys. We only bought datacentre licenses though...

Jamo

Jamo

Posted
Posted

Goto Licenses->Relationship Summary and then click the licence agreement you bought then look down the list for KMS keys, we had ours in there, couldn't see the datacenter ones anywhere else.

Jamo

Jamo

Posted
Posted
Oh I see! Sorry, just set up datacenter using DISM it doesn't take long and will let you licence your Servers without entering licence keys :)
localzuk

localzuk

Posted
  • Author
Posted
Got it working now. Next issue, fixing the DNS server record, as this system is inherited from a wider area BSF system and has bits left over...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...