Kms on server 2012

Hi All,
i install server 2012 with 2012 kms host license.
now i know if i enter the kms of 2012 license it valid all the way down for win 2012,2008,8... to activated
but i only want to activate with that kms is win 7 and 8 and no servers.
i want to activate the licenses on the servers manually.
how can i do that?

Hi DonPick,
Can you show me step-by-step how to configure KMS server 2012 to active windows 2012 and windows 8 ?
My email is [email protected]
or [email protected]
Best thank !
Hi,
there are many guides on the web, here is one:
http://technet.microsoft.com/en-us/library/hh831794.aspx
The steps will depend upon the OS of your intended KMShost machine.
Video: Set Up a KMS Host on a Windows Server 2008 R2 Machine
http://technet.microsoft.com/en-au/windows/ff716620.aspx
http://blogs.technet.com/b/askcore/archive/2013/03/14/installing-volume-activation-services-role-in-windows-server-2012-to-setup-a-kms-host.aspx
http://didyourestart.blogspot.com.au/2013/01/installing-upgrading-windows-server.html
http://myitknowledgebase.wordpress.com/2012/10/29/setup-kms-step-by-step-windows-2008-r2/
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

KMS Host server 2012 R2

I recently migrated our KMS server to a 2012 R2 box and I cannot get the count to budge now.According to this article our KMS key should now activate 2008 r2, 7 Ent, 2012 R2.7. Enter your KMS Host Key (CSVLK). Note: You can only install a Windows Server 2012 CSVLK at this point. A Windows Server 2012 CSVLK can activate Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 KMS clients.http://blogs.technet.com/b/askcore/archive/2013/03/14/installing-volume-activation-services-role-in-...Am I mistaken because my count is only at 4 which are Server 2012 R2 servers. None of the others are even making the count go up. A little help here.
This topic first appeared in the Spiceworks Community

as long as you have more than 25 Machines both client and server os:es will be activated.
It's all explained here:
http://technet.microsoft.com/en-us/library/ff793434.aspx

KMS On server 2012: Scope

hi,
If we add role of KMS server in server 2012 R2, can it cover KSM activation of products below?
- Office 2010
- Office 2013
- SERVER 2012 R2
- Server 2012
- Server 2008 R2
- Windows 8.1
- Windows 7
thanks

Yes, but only if you install the necessary Windows updates/patches, and the corresponding KMShost product keys.
This article I wrote, should be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx
If you have questions, or suggestions, on how the article could be improved, please let me know :)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Migrating KMS Services from Server 2003 Servers to Server 2012 R2

We have two Windows Server 2003 boxes that a previous administrator had setup as our KMS Servers.
These servers appear to be activating Office 2010, Windows 7, and Windows Server 2008R2 and 2003
I can see these activations taking place in the KMS logs on each server.
The question is what are the steps that we need to take to get the KMS Services migrated to Server 2012 without causing any activation issues in the current environment? I've be unable to come up with the proper order of operations from researching
blogs and I'm just not sure how to get where I need to go, what keys to use etc.
Since this was setup by a previous administrator, there is no documentation on what was done, what keys were used etc.
KMS Server 1:
slmgr /dlv
Name: Office(TM) 14, ProPlusKMSHost edition (Partial Product Key C6PWX)
Description: Office(TM) 14 KMS, VOLUME_KMS channel
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key VX348)
KMS Server 2:
slmgr /dlv
Name: Office(TM) 14, ProPlusKMSHost edition (Partial Product Key 3T9QW)
Description: Office(TM) 14 KMS, VOLUME_KMS channel
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key TT78P)
Of Note, we are a Microsoft Software Assurance customer and have Volume Licensing
In Summary, I would like to understand how to move my KMS Services to a new 2012 Server(s) and decommission the old 2003 boxes running KMS without disruption. As a final step I'd also like to be able to activate Windows 8, Server 2012, and Office 2013.

Hi,
If you wanted to slowly transition and verify... you could stand up new KMS host and make the priority of the SRV record lower so that clients will always connect to new server first and fall back to original box second.
Steps to migrating the KMS:
1. Uninstall the KMS host key first by running the following command:
slmgr -upk
2. Then, install the default kms key by running the following command:
slmgr /ipk [KMS Client Setup Key]
The default KMS client setup keys can be found here:
http://technet.microsoft.com/en-us/library/cc303280.aspx
3. Delete the record from the DNS:
Open DNS console:
Expand _tcp node under the domain.com. There will be a record _VLMCS. Delete this record.
4. The KMS server is uninstalled.
5. To install KMS on a new server, enter:
cscript C:\windows\system32\slmgr.vbs /ipk <KmsKey>
then to activate the KMS host, enter:
cscript C:\windows\system32\slmgr.vbs /ato
6. After activation is complete, restart the Software Licensing Service.
7. Verify that the record is created for the new server in the DNS.
To verify that the KMS host is configured correctly, you can check the KMS count to see if it is increasing. Run slmgr.vbs /dli on the KMS host to obtain the current KMS count. You can also check the Key Management Service log in the Applications and Services
Logs folder for 12290 events, which records activation requests from KMS clients. Each event displays the name of the computer and the time-stamp of an individual activation request.
https://social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows Server 2012 R2 KMS - STATUS_SUCCESS

We are in the process of setting up a Windows Server 2012 R2 KMS server to replace our Windows Server 2008 R2 machine.
After installing the Volume Activation role and going through the volume activation tools 'wizard' i'm running into a problem.
When i try to commit the settings (like firewall exceptions, custom dns zones) i get an error stating the following:
The following error has occurred. Please resolve the error and try again.
Description:
STATUS_SUCCESS
And none of the settings have been aplied, and there are no eventlog entries stating whats wrong.
When i deploy a Windows Server 2012 (non R2) machine and go through the same process commiting the same settings works fine.
Anybody know what might be wrong here?

Man, i've been checking things for days, and THIS is the solution? :)
Thanks for the help man, this fixed it for me too!
... why something like this doesn't generate a real error code or something is beyond me.....

Server 2012 Kms Host and Server 2008 r2 client.

I have deployed a Server 2012 Kms host.
Windows 7, and 8 are activating just fine, and Office 2010 is working.
The issue I'm having is activating Server 2008 and Server 2008 r2.
It seems I have missed a step that would allow me to activate those clients.
Can someone please guide me as to what possibly needs to be done to allow these clients to activate?

Hi,
The following steps are needed to set up Volume Activation Services in a Windows Server 2012 test lab:
1. Step 1: Set up the base test lab configuration
2. Step 2: Install the Volume Activation Services server role
3. Step 3: Configure Active Directory-based Activation
4. Step 4: Verify that Active Directory-based Activation works
5. Step 5: Configure Key Management Services (KMS)
6. Step 6: Verify that KMS volume activation works
At same time KMS volume activation requires
a minimum threshold of 25 computers before activation quests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host. However, unless the activation threshold
is reached, the verification will take the form of an error message rather than a confirmation message.
The related KB:
Test Lab Guide: Demonstrate Volume Activation Services
http://technet.microsoft.com/en-us/library/hh831794.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

KMS Host activation in Server 2012 R2 and Client Win7

Hi We are planing to Activate the windows 7 with Server 2012 R2 , Do we need 25 Win7 Machine minimum to activate the Key,? or we can have sround 10 servers 2012 r2 machine + 19 win7 machine to active the key for both Win7 and server 2012 r2..?

as long as you have more than 25 Machines both client and server os:es will be activated.
It's all explained here:
http://technet.microsoft.com/en-us/library/ff793434.aspx

Upgrading a DC in place from Server 2008 R2 to Server 2012 R2

This is not a question but more of an information post. I've found lots of posts regarding the upgrade of a DC and most say that you should do a clean install and migrate services and then decommission the old server. But I was more interested in an in-place
upgrade of a DC. I only found one post on here that said it was possible, so I gave it a try and it worked perfectly.
Here's what I've got and what I did:
Server 2008 R2 Std (Virtual Server using VMWare)
AD, DHCP, DNS, Certificate Services, Office KMS Host
I did the whole adprep /forestprep /domainprep routine and then installed Server 2012 R2. I selected the upgrade option and then sat back and watched the process. It took about 30 minutes to complete. Once it had installed, I logged in and the only issue
I noticed was that one service hadn't started, and this was just due to the OS waiting to be activated. Once I had done that there were no more errors/issues.
For the Office KMS server I then had to install the new version of KMS host as this has changed for 2012, and this is quite a simple task too. The only issue I have is waiting for the minimum of 5 PC's to activate...

Yes. That is of course a different situation. however, I would still not do it for acouple of reasons, which may or may not apply to you.
I work in a controlled environment (regulatory requirements) and for any change we need QA approval. Allowed downtime is very low. preparing a new DC and then swapping it out means far less downtime and much easier to manage from a QA perspective. Especially
since you can do a lot of acceptance testing up front.
Upgrades always carry the risk of certain things being reset, or changed unknowningly. Scratch installs are always the same. The possibility that after the QA release something may not work as expected can create a huge problem for me. We always prepare
and test installation procedures up front.
That's why we always try to follow best practices and procedures that allow as much pre-configuration as possible, and which allows us to fall back to existing configuration. Timeslots for downtime come around only once per year. And if it causes more than
a couple of hours downtime, only once every couple of years. the amount of sitewide effort involved and the financial risks are massive.
Basically it all boils down to this: is it a problem for you if somethign unexpected happens, do you have the possibility (time) to do much troubleshooting or the time needed to restore backups, and how acceptable is the risk of not being able to finalize
the proposed changes.
When there are millions of $$ on the line and a schedule slip could cost further hundreds of thousands of dollars ... , and aborting the site upgrade would be a huge failure for the site ... you want stability, predictability, and as few changes
as possible where you don't know the success in advance.

Error 0x80072ee7 when activating Windows Server 2012 Standard ROK

I am installing windows server 2012 standard ROK onto a HP Proliant micorsever. I installed the product key using elevated command prompt (found instructions on hp site), but when I get to the point to activate the operating system using the following
command cscript C:\windows\system32\slmgr.vbs -ato, I get an error message --> 0x80072ee7 On a computer running Microsoft windows non-core edition. Why is this happening? From prior research that I've done do I need to install a KMS Client
key and if so what is the proper key for the OS that I am using?

Hi,
The 0x80072EE7 error code may occur if the client computer cannot find the correct IP address when it tries to resolve a URL for the Windows Update Web site or for the Microsoft Update Web site. This error may occur if the Hosts file contains a static IP
address also might occur due to one of the following reason.
• Programs or processes that interfere with Internet communications
• Resource issues on the computer
• High Internet activity
To resolve the error examine the Host file (under System32\driver\etc folder) and check that Make sure that the file does not list any static IP entries for the Windows Update Web site or for the Microsoft Update Web site. Mean time sharing the article with
you.
1. 0x80072EE7 error code
2. KB 836941
Hope it helps!
Thanks.

Inplace upgrade of KMS host server

Hi all
I am running a KMS server which is windows server 2012. I am planning to do an in-place upgrade of this server to 2012 R2. Kindly provide me necessary steps to achieve this goal. I am not sure what will happen to KMS, if i do an inplace upgrade.
Regards.

Hi,
Thanks for your post.
I think you need a new KMS host key if you want to upgrade from windows server 2012 to 2012r2.
http://woshub.com/kms-server-installation-on-windows-server-2012-r2/
Meanwhile, for licensing related issue, you’d better contact Microsoft licensing team. In the United States and Canada, you may call the licensing team directly at 1-800-426-9400 (select option 4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak
directly to a Microsoft licensing specialist. In this way, you will know the detailed information about license.
Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/worldwide.aspx to find contact information in their locations.
Thank you for your understanding!
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Upgrading Windows Server 2012 Essential Eval to Windows Server 2012 R2 Retail

I need to upgrade from Windows Server 2012 Essential Eval version to Windows Server 2012 R2 Retail. What would be the easiest way to upgrade if license $$ is not an issue? The Server is a DC. Would the following works:
1. Upgrade from Windows Server 2012 Essential Eval to Windows Server 2012 Essential Retail
2. Do a conversion from Windows Server 2012 Essential Retail to Windows Server 2012 Standard Retail (I suppose this just require several command line to enable the 2012 Standard)
3. Do an in-place upgrade from Windows Server 2012 Standard to Windows Server 2012 R2 Standard (there is no need to do migration, am I right?)
Thanks.

I just did a simulation using Hyper V. It seems that I'm able to do the upgrade sequence as described but I'm not sure whether there are any side effect that not yet surface out. Here is the details steps that I took:
1. Under Windows Server 2012 Essential Eval
convert the Windows Server Essential 2012 Eval to Windows Server Standard 2012 using the following command in an elevated command prompot
dism /online /set-edition:ServerStandard /productkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /accepteula
press "y" and return to restart as prompted
the productkey could be retail key or the KMS client keys (just for installation not for activiation)
2. After reboot, the system become Windows Server 2012 Standard
using admin account to login
add admin account to the Enterprise Admins group and Schema Admins group if not already done so, logout and login again
mount the Windows Server 2012 R2 Standard disk in, say, drive d:
in an elevated command prompt, go the following:
cd d:\support\adprep
.\adprep.exe /forestprep
.\adprep.exe /domainprep
double click on d: in explore to run the Windows Server 2012 R2 Standard setup
follow the instruction to complete the in-place upgrade from Windos Server 2012 to Windows Server 2012 R2
3. After reboot into Windows Server 2012 R2 Standard, go to the charms bar, select setting -> server info, it will mention the server is not activated, click on Activate Windows and key in the Windows Server 2012 R2 Standard retail key

Windows Server 2012 Standard License and VMs

Hi,
With one Window server 2012 Standard activated license, I will get 2 VMs. So is there a limit with Windows Server 2012 standard license I can stack and the the number of VMs I can create on one server or across servers (virtual environment). Consider that
all Windows server 2012 standard licenses are activated. If there is no limit on VM creation by add Standard license then why did Microsoft come with Data center licenses with unlimited VMs.
How does the standard license work on Vmware environment. Is there a limit on the number for VMs that we can create.
Please advise me.
Thanks.

If i had one server 2012 standard with its key, i could run it as a vm but not as a virtual host without having the license right?
a single WS2012STD license, allows you to run a server machine (hardware), if that hardware has no more than 2 processors. In this case, you can run 2 VMs, each VM is running WS2012STD. You can also run WS2012STD as the host hypervisor via Hyper-V.
So, that's really 3 OS installations, on the same 2proc machine. The limitation is that the host hypervisor OS is only permitted to do Hyper-V stuff, it's not permitted to use that OS for anything other than hypervisor functions.
If you implement in this way, you would only have purchased a single license for WS2012STD, so you would only have a single key, so you would use that key for the 3 OS installations.
If i bought the single server 2012 standard license, i'd be able to install it as a Host and activate with the key and it'd give me rights to run 2vms on it and for those vms i would have to have 2 keys to activate after installing server 2012 standart
software on them right?
see above.
if you buy via Volume Licensing, things change a little bit due to MAK/KMS keys (it gets a whole lot simpler :)
Sorry for being unclear on the clusters part, i meant HA/failover. we have 2 2008R2 enterprise servers in cluster with shared storage and i was trying to clarify how could i add more vms there.
assuming your failover solution involves traditional server hardware, each failover node is just another hardware machine, so, for each node you have to count up the procs and VMs, just as you would do for non-failover implementations.
if a server is installed and running/executing, it needs to be licensed.
with current configuration, each server is hosting 2vms and if anything happens single host can accommodate all four. I am assuming we have 2 enterprise licenses for them, but if i wanted to run 4vms on each host, we have to buy 2 more enterprise licenses
and install vm togerther with their keys?
There is no Enterprise for WS2012? (WS2012 has STD and DCE)
do you mean as in WS2008R2ENT ?
You can re-assign licenses from one machine to another machine (under the Volume Licensing terms. I'm not sure about Retail terms, you should check that). There are limitations on how often you can reassign licenses (no more than every 90days)
If hardware "fails", you are allowed to reassign the license in a shorter period than 90days.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Set up VAT on server 2012 R2 now WIn7 computers won't activate?

I recently install the Volume activation tools onto a server 2012 box to activate the new servers we are bringing on line to retire some older ones. Now i know this key will do win 8 and '12 boxes, and thats the KMS key I installed. But today one
of our helpdesk guys was trying to deploy some windows 7 computers and got an error when trying to activate them "software licensing service reported that the computer could not be activated.
The count reported by your key management service (kms) is insufficient ". This windows 7 image already has the
MAK in the image we deploy, and we've never had a KMS set up for windows 7and none was entered into the server when it was set up. I tried to put in the KMS key for win 7 into the server 2012 box but it just errors out. So I"m a little
confused as to why all of the sudden it's trying to authenticate against this server, and how do I get a windows 7 key in that server 2012 box?

Hi ,
"KMS can activate both physical computers and virtual machines. To qualify for KMS activation, a network must meet the activation threshold: KMS hosts activate client computers only after meeting this threshold. To ensure that the activation threshold
is met, a KMS host counts the number of computers that are requesting activation on the network. For computers running Windows Server 2008 or Windows Server 2008 R2, the activation threshold is five. For computers running Windows Vista or Windows 7, the activation
threshold is 25. The thresholds include client computers and servers that are running on physical computers or virtual machines."
For details please refer to following link:
http://technet.microsoft.com/en-us/library/ff793434.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Office on RDS on Server 2012 licensing

I have a client using RDS on Server 2012 to run proprietary software. They would like to begin allowing their sales force to connect to the server via iPads and run Office, which isn't yet installed on the server.
Thus far I've come to the understanding that what that will take is a volume license for Office installed on the server and an RDS license (they already have several) for every concurrent connection.
My questions are -
1) Am I right about installing the Office volume license on the server?
2) Do they need Office installed on the client device as well? (I wouldn't think so, but some things I'm reading say otherwise)
3) One of the reasons they want to switch to iPads (or Android devices or whatever) is to limit cost if their salesperson looses or breaks their device. So my question is, does the volume license count concurrent connections like the RDS license does or
is it somehow "tied" to the remote devices? For example -- If a salesperson does lose their device is it possible just to get another one and have them start using it without any additional licenses or is the license that was "tied" to
the old device just gone forever and we have to purchase another one to connect the new device? If the salesperson wants to RDS into the server from their home computer while their iPad is off and connect to their RD session would that require another license?
Or, if one of the people who connects to RDS who doesn't need to use Office accidentally opens "Word," will that license be then "tied" to their computer and wasted?
Thank you for any help,
Jeff Minch

Hi Pure,
Your friend of a friend is incorrect.
The statement you've made about licences being locked applies to the RDS CAL (specifically a per computer CAL), not Office. As I said before, an Office licence has nothing whatsoever to do with an RDS CAL.
There are three kinds of "common" Offices licences:
Retail.
MAK.
KMS.
Unless you're buying your copies of Office from a retail shop (or online shop) - and it doesn't sound like you are, then you can forget about retail keys.
MAK keys are accessed by one of the volume licencing agreement programs and are typically used by smaller businesses that don't have enough computers to be able to access the KMS approach to licencing or for clients that will not be able to talk to
a KMS server at least every 180 days.
MAK keys involve a once-off activation and then they never renew the activation again. This makes them ideal for things like non-Internet kiosks, field laptops and the like. The once-off activation can happen with the client being Internet-connected for
this once off activation or via an offline activation using the telephone or VAMT (Volume Activation Management Tool).
KMS keys come in two flavours:
KMS host activation key, which is used to create a KMS "server".
KMS client key, which is a standard key that can be applied to as many volume licencing copies of Windows/Office ad you like, and which "instructs" the client to activate against the KMS server above.
There are a number requirements to be met before you can successfully deploy a KMS host, but it's not worth going into depth here about it as the only point to be made is that yet again, it has nothing to do with RDS licencing. The closest it would get to
being relevant is if the copies of Office installed on the RDS Session Hosts were activated via a KMS host.
I think you need to have a read-up on RDS licencing and the expiration process:
http://technet.microsoft.com/en-us/library/cc732416.aspx
http://social.technet.microsoft.com/Forums/windowsserver/en-US/3efeee70-9d23-4477-8b94-23e2643dd5bf/controlling-rds-user-cal-expiry?forum=winserverTS
Going back to your iPad clients, you need to determine whether you're using per device or per user licencing before you can figure out a way forward as far as RDS licencing goes, but again, this has nothing to do with Office licences being retained
on the device, as that scenario is not possible as Office activation doesn't work like that.
Perhaps the easiest way to depict the difference for you is to understand that RDS licencing functions outside of the RDS session while Office licencing functions within it, which is why a device being removed/lost has nothing to do with Office at all.
So long as you remember that you need to buy as many Office licences as there are clients connecting to the RDS environment, you can activate Office any way you like.
Cheers,
Lain

Download the Evaluation: Windows Server 2012 R2 product key

Where do you obtain the product key information?
for the .iso download version to be functional

Hi Marz,
You can download Win2012 R2 from mentioned link
http://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspx#fbid=kyb2VoUOHw-
http://blogs.technet.com/b/firehose/archive/2013/06/25/system-center-2012-r2-now-available-for-download.aspx
and key is provided in mentioned link
http://technet.microsoft.com/en-us/library/jj612867.aspx
I have already downloaded it and checked it, it is working fine without issue.
If you have installed Evaulation version and unable to use KMS key then Try mentioned link, it is very helpful
http://www.doitfixit.com/index.php?option=com_content&view=article&id=192:upgrade-server-evaluation-version&catid=48:active-directory&Itemid=53
http://workinghardinit.wordpress.com/tag/windows-server-2012-r2/
Steps are
1. check Current Edition
DISM /online /Get-CurrentEdition
2. Check Target Edition
DISM /online /Get-TargetEditions
3.
DISM /online /Set-Edition:ServerStandard /ProductKey:D2N9P-3P6X9-2R39C-7RTCD-MDVJX /AcceptEula
or
DISM /online /Set-Edition:ServerDatacenter /ProductKey:W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9 /AcceptEula
Now you can install the new Windows 2012 R2 KMS key. If you run in to any issues here, restarting the KMS Service can help (("net stop sppsvc" and "net start sppsvc") . Try that first.
4.
slmgr.vbs /ipk D2N9P-3P6X9-2R39C-7RTCD-MDVJX
or
slmgr.vbs /ipk W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9
once it done, we can cross check the time period
5
slmgr.vbs /dlv
Kirpal Singh

Kms on server 2012

Similar Messages

Maybe you are looking for