#Slmgr for kms client install#

KMS clients on the Contoso network query DNS and receive the SRV records for both KMS hosts. The Key Management Service firewall exception needs to be enabled. The host KMS_2 is now activated against Microsoft via the Internet: Slmgr.vbs /ato.ДЇinally, the administrator confirms that the KMS host exclusion is enabled in Windows Firewall. The IT administrator accesses the DNS server, locates the RR for _vlmcs._, and changes its permissions to give KMS_Hosts Read, Write, and Delete permission to the record. KMS_1 automatically publishes its SRV resource records (RRs) to DNS. The host KMS_1 is activated against Microsoft via the Internet: Slmgr.vbs /ato. The administrator adds the servers KMS_1 and KMS_2 to the KMS_Hosts membership. The IT administrator then creates a Security Group in Active DirectoryВ® Domain Services (ADВ DS) named KMS_Hosts. Then you can activate the windows with KMS server: Slmgr /ato You can also specify the TCP port on which the activation service listens (by default 1688): slmgr /skms :1688 If the client does not find the KMS server automatically, then you can specify the address of the KMS server manually using the slmgr with the option /skms. You can check this DNS entry using the nslookup command: nslookup -q=SRV _VLMCS._

You can skip this step if your DNS has a valid SRV record that allows clients to find the KMS server. After KMS server discovery, the client performs the OS activation.

#Slmgr for kms client install#

After you specify the GVLK key, the KMS client tries to connect to the previously configured KMS server or find a special SRV (_VLMCS) record in the DNS that is created when you install a new KMS server in the domain and pointing to your KMS server.