<div>
You need to change MAK key to KMS key on client computer to be able to successfully activate against KMS server. <br />
So you need to issue 'slmgr.vbs /ipk kms_key' on each client computer with MAK key.
</div>


<div>
I am getting this suggestion as well .. is it correct ??<br />
<br />
By default, Windows Vista and Windows Server 2008 are KMS clients. You can convert a KMS client to a MAK client and back again to a KMS client at anytime. Your computer must have access to a KMS host on your organization's network to complete this procedure.<br />
&nbsp;<br />
To convert a MAK activation client to a KMS client:<br />
&nbsp;<br />
1. Log on to the MAK client.<br />
&nbsp;<br />
2. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click command prompt, and then click Run as administrator.<br />
&nbsp;<br />
3. To install the KMS key, at the command prompt type the following, and then press Enter:<br />
cscript \windows\system32\slmgr.vb<wbr />s /ipk &lt;KmsSetupKey&gt;<br />
&nbsp;<br />
Be sure to include the dash between each set of five characters.<br />
&nbsp;<br />
4. To activate the computer as a KMS client, type the following at the command prompt, and then press Enter:<br />
cscript \windows\system32\slmgr.vb<wbr />s /ato<br />
&nbsp;<br />
This script reports the success or failure of the procedure, along with a result code.<br />
&nbsp;<br />
Additional information: KMS Client Setup Keys:<br />
<a href="https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx</a>
</div>


<div>
@Dariusz Tyka<br />
<br />
as you suggested :<br />
need to issue 'slmgr.vbs /ipk kms_key' on each client computer with MAK key.<br />
<br />
IPK will be KMS clent set up key ??<br />
<br />
KMS Client Setup Keys:<br />
<a href="https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx</a>
</div>


<div>
Yes IPK, will be client kms key. Have done it several times and it works as described.
</div>


<div>
Thanks a lot @Dariusz Tyka<br />
<br />
One more thing ..Do i need to unable to auto discovery from windows regedit key ?
</div>


<div>
What registry key are you referring to? Client computers should be able to find KMS host via dns or active directory depending on your configuration.
</div>


<div>
@Dariusz Tyka : I got it &nbsp;.. Thanks for your clarification..<br />
<br />
I have few clients which cann't talk to DNS for those shall i use this method , please confirm .<br />
<br />
slmgr.vbs /skms &lt;value&gt;:&lt;port&gt;<br />
where value is either the KMS_FQDN, IPv4Address, or NetbiosName of the KMS host and port is TCP port on the KMS host.
</div>


<div>
@Dariusz Tyka<br />
<br />
Thanks for your valuable suggestion :)
</div>


<div>
@Dariusz Tyka<br />
<br />
In reference to Manually Specifying a KMS Host.<br />
<br />
1st i need to point the KMS using below command &nbsp;&amp; then 'slmgr.vbs /ipk kms_key' on each client computer with &nbsp;KmsSetupKey. ??<br />
<br />
slmgr.vbs /skms &lt;value&gt;:&lt;port&gt;<br />
where value is either the KMS_FQDN, IPv4Address, or NetbiosName of the KMS host and port is TCP port on the KMS host.<br />
<br />
Thanks
</div>


<div>
It doesn't matter if you first change MAK 2 KMS key or point &nbsp;your clients to KMS host. You simply need to do both changes in either order for clients to successfully activate against KMS host.
</div>


<div>
Hi Johnny<br />
<br />
do you require any further assistance? If not pls close the question and distribute points.<br />
<br />
Dariusz
</div>


<div>
<div class="content wysiwyg-content">
Hello All,<br />
<br />
I have Windows server 2008 R2/2012 R2/2016 images which is installed with MAK key now i want to convert to KMS Key .<br />
<br />
I &nbsp;am little confused , How to convert MAK client to KMS client , I have gone through many MS article &amp;&nbsp;blog which says<br />
++++++++++++++++++++++++++<wbr />++++++++++<wbr />++++++++<br />
You do not need to run slmgr /upk to uninstall the product key.<br />
You should only need to run slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xx<wbr />xxx-xxxxx.<wbr /><br />
Use the KMS client keys from the Volume Activation Deployment document:<br />
<a href="http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en" rel="ugc">http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en</a><br />
+++++++++++++++++++<br />
<br />
My question here is KMS client key will be provided by the KMS host or this will be available to MS above mentioned link also <br />
few of the articles saying &nbsp;:<br />
slmgr.vbs /ipk &lt;KmsSetupKey&gt;<br />
<br />
Which &nbsp;is correct method , please suggest ,its confusing !<br />
<br />
Thanks
</div>
</div>


Hello All,

I have Windows server 2008 R2/2012 R2/2016 images which is installed with MAK key now i want to convert to KMS Key .

I  am little confused , How to convert MAK client to KMS client , I have gone through many MS article & blog which says
++++++++++++++++++++++++++++++++++++++++++++
You do not need to run slmgr /upk to uninstall the product key.
You should only need to run slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.
Use the KMS client keys from the Volume Activation Deployment document:
http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en
+++++++++++++++++++

My question here is KMS client key will be provided by the KMS host or this will be available to MS above mentioned link also 
few of the articles saying  :
slmgr.vbs /ipk <KmsSetupKey>

Which  is correct method , please suggest ,its confusing !

Thanks

conversation MAK client to KMS client .

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.