Transfer KMS from 2012 server to a 2008 server

Does anyone have the steps for transferring KMS to another server, that activates Office and Windows 7?
It's currently on a Windows 2012 server, but I need to transfer it to another server that's 2008 temporarily, so I can rebuild the 2012 server then transfer it back.

This is due to other issues not related to KMS but I need KMS up while the 2012 server is down and being rebuilt.

I'm assuming I'd have to make some manual DNS adjustments as well if I recall but I could be wrong?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Install key on new server, change DNS. That's it. Of course KMS clients can go for over a month without a KMS server, so unless you expect this rebuild to take an exceptionally long time, I'd usually not move it if it is only temporary.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
garryshapeAuthor Commented:
Ah ok, so if I'm keeping the same hostname and IP, then that would work?
Would I need to uninstall KMS first before wiping the server and re-deploying a new VM with the same Name/IP?
Cliff GaliherCommented:
No need to uninstall first.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

garryshapeAuthor Commented:
Honestly I'm not sure how KMS was setup on the server or who set itup, but it does appear to be running.
Is there a way I can export its configuration and then re-import after the re-image?
Cliff GaliherCommented:
There is almost no configuration to KMS.

There is a key, which you can't simply export and import because each time the key is used it'll want to phone home.

And there are DNS entries, which may not be on the KMS server at all, but on the DNS servers of your environment. And there are a whole three records.

It isn't a complex service.
garryshapeAuthor Commented:
Ok well we may have a system backup in place and I may be able to get KMS backed up first just in case. If all hell brakes loose during the switch over migration I could do a restore. Only forseable issue would be restore time due to a slow circuit.
But sound simple so ill give it a shot after hours and hopefully be successful. Ty
garryshapeAuthor Commented:
When I run "slmgr.vbs /dli" on my client system, it shows the product "Name: Windows(R) 7, Professional edition" with partial key and KMS server.

But then on the KMS server I run "slmgr.vbs /dli all" and I don't see the Windows 7 Professional product listed.
Is another command I can run on the KMS server to ensure I have every product that it's servicing licensing for?

i also tried the local VAMT tool and and it's only showing 3 products, office 2010, 2013 and Windows Server standard edition.

VAMT also has no product keys installed within the GUI, but I guess that's not reflective of what KMS keys are installed..?
Cliff GaliherCommented:
Server KMS key also activate client automatically. You don't need a separate client key if you have a server key. So that report is accurate.
garryshapeAuthor Commented:
I think I understand. But I'm still confused that the Partial Product Key I show for the server product on KMS is different than the Partial Product Key I show on my local client for Windows 7
Cliff GaliherCommented:
Normal. Windowsninstalls bu default with  GVLK and that tells find and activate against a KMS server. So the key actually *is* different.
garryshapeAuthor Commented:
Yeah my Windows 7 Professional client check shows partial key is GPDD4, which is the pre-configured KMS key it appears.

But I thought there would need to be a volume license key for Windows 7 Pro on the KMS server for activation to work properly... ?
Cliff GaliherCommented:
Keys and activation are two different concepts.  A KMS key is for a KMS server.  Client OSes use generic keys and activate by talking to a KMS server that has an active key.  Don't confuse the two concepts.  And no, there does not need to be a Win7 KMS key on the server if the server has a key to activate other servers. This is covered in TechNet:

So if you have a group A key, that'll activate servers in Group A *and* clients.  And installing a client key is redundant (and in fact wouldn't work.)   If you install a group B key, the KMS server can now activate all OSes in Group B, Group A, and the client VL group.  Group C can activate Group C, B, A, and client.  So you install *one* key.  The highest key for the group of OSes you plan on activating via KMS.  And one oddity, while there are win7 KMS keys, they can't be installed on a server. Because the key not only activates the KMS service, but activates the machine it is installed on, a client KMS key can't activate a server OS. So installing a win7 KMS key on a server fails. The only time you'd use a client KMS key is if you were setting up a client OS to act as a KMS server.  Which sounds odd, but is not uncommon when only the client OSes are bought via VL and server OSes are bought by other means, or the server count is low enough that KMS doesn't make sense.
Cliff GaliherCommented:
I should note that the above discussion of installing a key on a server OS is true throughout the hierarchy, but is most often seen with client key on a server. But technically it could happen with any key where the OS is not in the same or lower group. You couldn't install a datacenter KMS key on a standard version of server because the group key (datacenter) attempting to activate is higher than the OS. It'd be just like trying to install a win7 key on a server. So the logic is the same.
garryshapeAuthor Commented:
Oh wow ok, didn't realize that. I was making an assumption based on how Office is licensed via KMS as well, figured each individual product would need it.
I'm just getting around to getting my access to the Licensing website, so I'm curious as to whether the number of Windows 7 Pro activations will be reflected accurately, or if all Windows 7 activations on the network will be shown in the number of server activations in the report.
Cliff GaliherCommented:
Neither. KMS does not report back to Microsoft on number of OSes activated against a KMS server. You'll need to use VAMT if you want to track that data.
garryshapeAuthor Commented:
Ok but they are verifying licensing at Microsoft right? This isn't some piracy loophole or anything
Cliff GaliherCommented:
They verify the KMS key is valid when you first install it.  That's it.  Yes, you *could* activate 1,000 machines and only have 25 licenses.  KMS won't phone home and report you, or stop you, or block activations.

Regarding piracy, Microsoft regularly audits VL customers, so realistically you would get caught in an audit. They'll get the local report of activated machines and if the count is way off, they'll know during the audit.  KMS is much like RDS User CALs.  It is mostly honor system except during an audit.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.