Microsoft/KMS - Revision history

Kenneth: /* Test Access to MS Activation Servers */

2025-04-21T15:47:46Z

Test Access to MS Activation Servers

← Older revision		Revision as of 15:47, 21 April 2025
Line 64:		Line 64:

	Check if your firewall is blocking access		Check if your firewall is blocking access
	curl -v https://activation-v2.sls.microsoft.com		C:\> curl -v https://activation-v2.sls.microsoft.com

	== Specify the Domain to find KMS settings ==		== Specify the Domain to find KMS settings ==

Kenneth: /* Clear KMS Activation */

2025-04-21T15:47:22Z

Clear KMS Activation

← Older revision		Revision as of 15:47, 21 April 2025
Line 60:		Line 60:
	# Clear Domain		# Clear Domain
	slmgr /ckms-domain		slmgr /ckms-domain

			== Test Access to MS Activation Servers ==

			Check if your firewall is blocking access
			curl -v https://activation-v2.sls.microsoft.com

	== Specify the Domain to find KMS settings ==		== Specify the Domain to find KMS settings ==

Kenneth: /* Temporary Workaround */

2025-04-19T19:37:07Z

Temporary Workaround

@@ Line 49: / Line 49: @@
 To clear later:
   slmgr /ckms
 == Usage ==

Kenneth: /* Registry Settings */

2025-03-21T05:57:48Z

Registry Settings

← Older revision		Revision as of 05:57, 21 March 2025
Line 109:		Line 109:
	== Registry Settings ==		== Registry Settings ==

	Registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform		Registry subkey:
			HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform

			Registration key in:
			HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\
			BackupProductKeyDefault (string)

	ref:		ref:
	Registry Settings for Volume Activation		Registry Settings for Volume Activation
	https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn502532(v=ws.11)		https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn502532(v=ws.11)


			Registry example:
			<pre>
			Windows Registry Editor Version 5.00

			[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform]
			"BackupProductKeyDefault"="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
			"KeyManagementServiceName"="kms.aznot.com"
			"KeyManagementServicePort"="1688"
			</pre>

	== Notes ==		== Notes ==

Kenneth: /* Notes */

2025-03-13T23:00:43Z

Notes

← Older revision		Revision as of 23:00, 13 March 2025
Line 106:		Line 106:
	Activate client:		Activate client:
	slmgr /ato		slmgr /ato

			== Registry Settings ==

			Registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform

			ref:
			Registry Settings for Volume Activation
			https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn502532(v=ws.11)

	== Notes ==		== Notes ==

Kenneth: /* Notes */

2024-08-03T05:45:12Z

Notes

← Older revision		Revision as of 05:45, 3 August 2024
Line 110:		Line 110:

	See [[Microsoft/KMS/Notes]]		See [[Microsoft/KMS/Notes]]

			Guidelines for troubleshooting DNS-related activation issues \| Microsoft Learn
			https://learn.microsoft.com/en-us/windows-server/get-started/common-troubleshooting-procedures-kms-dns

	== keywords ==		== keywords ==

Kenneth: /* KMS Server */

2024-07-15T21:23:28Z

KMS Server

← Older revision		Revision as of 21:23, 15 July 2024
Line 5:		Line 5:
	Generic Volume License Key (GVLK)		Generic Volume License Key (GVLK)

	:"To use KMS, you need to have a KMS host available on your local network. Computers that activate with a KMS host need to have a specific product key. This key is sometimes referred to as the KMS client key, but it's formally known as a Microsoft Generic Volume License Key (GVLK). Computers that are running volume licensing editions of Windows Server and Windows client are, by default, KMS clients with no extra configuration needed as the relevant GVLK is already there."<ref>https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys</ref>		:"To use KMS, you need to have a KMS host available on your local network. Computers that activate with a KMS host need to have a specific product key. This key is sometimes referred to as the KMS client key, but it's formally known as a Microsoft Generic Volume License Key (GVLK). Computers that are running volume licensing editions of Windows Server and Windows client are, by default, KMS clients with no extra configuration needed as the relevant GVLK is already there." <ref>https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys</ref>

	== Installation ==		== Installation ==

Kenneth: /* KMS Server */

2024-07-15T21:23:18Z

KMS Server

← Older revision		Revision as of 21:23, 15 July 2024
Line 2:		Line 2:

	Key Management Service (KMS) allows organizations to activate systems within their own network, while MAK activates systems on a one-time basis, using Microsoft’s hosted activation services. [http://www.microsoft.com/licensing/existing-customers/product-activation.aspx]		Key Management Service (KMS) allows organizations to activate systems within their own network, while MAK activates systems on a one-time basis, using Microsoft’s hosted activation services. [http://www.microsoft.com/licensing/existing-customers/product-activation.aspx]

			Generic Volume License Key (GVLK)

			:"To use KMS, you need to have a KMS host available on your local network. Computers that activate with a KMS host need to have a specific product key. This key is sometimes referred to as the KMS client key, but it's formally known as a Microsoft Generic Volume License Key (GVLK). Computers that are running volume licensing editions of Windows Server and Windows client are, by default, KMS clients with no extra configuration needed as the relevant GVLK is already there."<ref>https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys</ref>

	== Installation ==		== Installation ==

Kenneth: /* Temporary Workaround */

2019-08-09T22:21:58Z

Temporary Workaround

New page

== KMS Server ==

Key Management Service (KMS) allows organizations to activate systems within their own network, while MAK activates systems on a one-time basis, using Microsoft’s hosted activation services. [http://www.microsoft.com/licensing/existing-customers/product-activation.aspx]

== Installation ==

# Install Server 2003 SP2 (or R2)
# Install [http://www.microsoft.com/downloads/details.aspx?FamilyId=81D1CB89-13BD-4250-B624-2F8C57A1AE7B&displaylang=en KMS 1.1]
# Install [http://support.microsoft.com/kb/968915 KMS 1.2 update]
# Install 'VOLUME_KMS_R2_C channel' host key license
#* slmgr /ipk [KEY]
# Activate host key license
#* slmgr /ato
# Modify DNS to have SRV record point to KMS server
#* kms IN A 10.10.10.100
#* _vlmcs._tcp IN SRV 0 100 1688 kms.oeey.com.
#* Microsoft: Forward Lookup Zones -> [domain] -> _tcp -> Other New Records... -> Service Location (SRV) -> Create Record...
#** Service: _vlmcs | Protocol: _tcp | Priority: 0 | Weight: 100 | Port number: 1688 | Host offering this service: kms.oeey.com. (note the ending period)
# Have clients get domain name from DHCP Server or set Host name DNS domain name manually
# Activate clients
#* slmgr /ato
#* or Through GUI activation
# Meet the 25 minimum requirement for activation to take affect (VMs do not count to minimum)

Check:
dig SRV _vlmcs._tcp.oeey.com
;; ANSWER SECTION:
_vlmcs._tcp.oeey.com. 3600 IN SRV 0 0 1688 kms.oeey.com.

== Temporary Workaround ==

KMS auto discovery is failing on oeey.com domain:

Temp workaroun:

Set kms server:
slmgr /skms 10.10.10.100:1688

Activate license:
slmgr /ato

Rearm temporary license if needed:
slmgr /rearm

To clear later:
slmgr /ckms

== Usage ==

=== KMS Server ===

Run commands from here:
cd C:\WINDOWS\System32\

Show license count:
cscript slmgr.vbs /dli

Key Management Service is enabled on this machine
Current count: 42

Show license count with additional details:
cscript slmgr.vbs /dlv

licensecount.bat:
<pre>
@echo off
REM Scripted by Kenneth Burgener <kenneth.burgener@oeey.com> 2010
echo.
echo.
echo Counting licenses, please wait...
echo.
echo.
cscript //Nologo slmgr.vbs -dli
echo.
pause
</pre>

=== KMS Client ===

WARNING: MAKE SURE YOUR TIME IS ACRUATE!

This is for Vista, Windows 7, Server 2008 and Server 2008 R2 clients

DNS: Modify DNS to have SRV record point to KMS server:
kms IN A 10.10.10.100
_vlmcs._tcp IN SRV 0 100 1688 kms.oeey.com.

nslookup:
set type=SRV
_vlmcs._tcp.oeey.com

_vlmcs._tcp.testhost.oeey.com SRV service location:
priority = 0
weight = 100
port = 1688
svr hostname = kms.oeey.com
kms.oeey.com internet address = 10.10.10.100

Manually point to KMS server:
slmgr /skms 10.10.10.100:1688

Activate client:
slmgr /ato

== Notes ==

See [[Microsoft/KMS/Notes]]

== keywords ==

Vista Windows Server 2008 W2K8 W2K8R2 License Server KMS MAK

[[Category:Microsoft]]
[[Category:Windows]]
[[Category:Windows Administration]]