How do I determine what server is hosting KMS?

1. The KMS server's SRV DNS entry is missing or misconfigured.
2. There is a network or DNS issue preventing the query from succeeding.
3. You're querying the wrong DNS server.

Step 1: Verify the SRV Record Manually​

1. Use PowerShell:
   Run the following command to query DNS for the KMS SRV record:
   
   Code:

   powershell
   Resolve-DnsName -Type SRV _vlmcs._tcp

   • This will query your default DNS server to find if the KMS server SRV entry is registered.
2. Nslookup with Default DNS Server:
   If Resolve-DnsName doesn't work, double-check it with nslookup manually:
   
   Code:

   bash
   nslookup
   set type=srv
   _vlmcs._tcp

3. Manually Check Your DNS Zone:
   • Open DNS Manager on your DNS server.
   • Navigate to your forward lookup zone (e.g., example.com).
   • Look for _vlmcs._tcp under _tcp in the zone.

Step 2: Manually Register the SRV Record (If Missing)​

1. Steps to Add SRV Record:
   • Open DNS Manager.
   • Locate your domain zone, then expand _tcp.
   • Right-click > Other New Records... > Select Service Location (SRV).
   • Fill in the details:
     • Service: _vlmcs
     • Protocol: _tcp
     • Port Number: 1688 (default for KMS)
     • Host Offering This Service: Your KMS server’s FQDN (e.g., kms.example.com).
2. Refresh Your DNS Settings:
   After manual configuration, refresh DNS propagation:
   
   Code:

   bash
   ipconfig /flushdns

   • Test the query again to confirm the record is visible.

Step 3: Check KMS Server Settings​

1. Verify KMS Host Activation:
   Run this command on the suspected KMS server:
   
   Code:

   bash
   slmgr /dlv

   • This will display the KMS host machine details, including its DNS publishing status.
2. Enable DNS Publishing:
   If it states that DNS publishing is disabled, enable it:
   
   Code:

   bash
   slmgr /cdns

   This re-enables DNS record publishing for the KMS server.
3. Force Registration:
   You can also forcefully register the DNS SRV record:
   
   Code:

   bash
   net stop sppsvc
   net start sppsvc

4. Client-Side Debugging:
   On a KMS client, test and view the current KMS configuration:
   
   Code:

   bash
   slmgr /skms <kms-server>
   slmgr /ato

Step 4: Manually Locate the Host​

1. Logging into potential KMS hosts and verifying their slmgr /dlv output.
2. Check your organization’s documentation and AD records for KMS information.

Additional Notes​

• Ensure that your network firewall allows traffic over port 1688, which is required for KMS functionality.
• If the SRV query and KMS server DNS publishing still fail, consider manually configuring the KMS server hostname on the clients using:
  
  Code:

  bash
  slmgr /skms <kms-server-fqdn>:1688

Why might nslookup fail?​

1. No SRV Record Exists: The _vlmcs._tcp SRV record might not be configured in DNS.
2. Permission or Access Denied: The network or DNS server may restrict service record lookups.
3. Incorrect Command: Syntax or spelling mistakes in the nslookup query.
4. DNS Issues: Network or DNS server issues might prevent a proper response.

Alternatives to Find the KMS Host​

1. Use PowerShell to Query for KMS​

Resolve-DnsName -Type SRV _vlmcs._tcp

2. Check KMS Configuration on a Client​

slmgr /dlv

3. Manually Search DNS Records​

4. Check the KMS Server Directly​

• Run slmgr /dli or slmgr /dlv on the machine to confirm it's set up as the KMS server.
• Look for the Software Licensing Service role in Server Manager, which supports KMS hosting.

5. Use Network Monitoring Tools​

Troubleshooting DNS Issues​

• Verify the _vlmcs._tcp SRV record exists and is published correctly.
• Confirm that DNS zones are propagating properly across your network.
• Check network firewall and routing settings to ensure connectivity between your client and the DNS server.

Have More Details?​

• Any error messages you're seeing.
• The environment (e.g., domain-joined or standalone clients).
• Steps you've already tried.

Step 1: Confirm KMS Host Role on the Domain Controller​

1. Run the Command to Check Activation Details:
   • On the domain controller, run the following:
     
     Code:

     bash
     slmgr /dlv

   • This will display detailed information about the KMS host, including:
     • Whether the KMS service is enabled.
     • The number of requests processed.
     • Whether it is actively publishing to DNS.
2. Look for KMS Details:
   • If the server is the KMS host, you should see information like:
     • KMS Machine Name: The server’s name or FQDN.
     • License Status: KMS active.
     • Key Management Service is enabled on this machine.

Step 2: Verify the SRV Record in DNS​

1. Query the SRV Record:
   • Use PowerShell or nslookup to confirm the SRV record exists for _vlmcs._tcp:
     
     Code:

     powershell
     Resolve-DnsName -Type SRV _vlmcs._tcp

     Or:
     
     Code:

     bash
     nslookup -type=srv _vlmcs._tcp

2. Check DNS Manager:
   • If Resolve-DnsName fails, open DNS Manager and look in your forward lookup zone under _tcp. for the _vlmcs._tcp SRV record. It should point to your domain controller.
3. Fix if Missing:
   • If the record is missing, you can enable DNS publishing on the KMS server (your domain controller):
     
     Code:

     bash
     slmgr /cdns

4. Restart the Service:
   • Restart the Software Protection Service to force DNS registration:
     
     Code:

     bash
     net stop sppsvc
     net start sppsvc

   • Wait a few minutes for DNS replication, and check again.

Step 3: Test Activation Requests​

1. Test from a Client Machine:
   • On a client machine trying to activate with the KMS host, run:
     
     Code:

     bash
     slmgr /skms <FQDN>:1688
     slmgr /ato

   • Replace <FQDN> with the domain controller’s fully qualified name.
2. Verify Activation:
   • success messages indicate that your client can communicate with the KMS host.
   • Run:
     
     Code:

     bash
     slmgr /dli

   • This shows details about activation and confirms it was using the domain controller as the source.

Step 4: Monitor Logs​

• On the KMS Server (DC):
  • Check the key management service logs in Event Viewer under:
    
    Code:

     Applications and Services Logs -> Key Management Service

  • Look for activation requests from clients to ensure everything is working.

Optional: Confirm Licensing Status​

slmgr /ipk <KMSHostKey>

Conclusion​

Steps to Create the _vlmcs._tcp SRV Record in DNS​

1. Open DNS Manager​

• On your DNS server, open the DNS Manager.
  • You can do this by running dnsmgmt.msc or accessing it through Server Manager > Tools > DNS.

2. Navigate to Your DNS Zone​

• Expand your Forward Lookup Zones.
• Locate your domain name (e.g., example.com).

3. Add the SRV Record​

1. Right-Click on _tcp Folder:
   • If there is a _tcp folder under your zone, right-click on it. If _tcp doesn’t exist, create it:
     • Right-click your domain > New Domain > Enter _tcp.
2. Create the New SRV Record:
   • Right-click _tcp > Other New Records > Select Service Location (SRV).
3. Fill in the SRV Record Details:
   • Service: _vlmcs
   • Protocol: _tcp
   • Priority: 0 (default priority, adjust if needed for multiple KMS servers).
   • Weight: 0 (default weight, adjust for load balancing multiple hosts).
   • Port Number: 1688 (this is the KMS default port).
   • Host Offering This Service: <FQDN of your KMS host> (e.g., kms.example.com or yourdomaincontroller.example.com).
4. Click OK to save the record.

4. Verify the Record​

• Use nslookup or PowerShell to query the SRV record and ensure it is discoverable:
  
  Code:

  bash
  nslookup -type=srv _vlmcs._tcp.<yourdomain>

5. Flush DNS Cache and Restart Services​

• On the KMS server, restart the Software Protection Service:
  
  Code:

  bash
  net stop sppsvc
  net start sppsvc

• On a client machine, flush the DNS cache to ensure the new SRV record is queried:
  
  Code:

  bash
  ipconfig /flushdns

Test KMS Functionality​

1. Verify Client Activation:
   • From a client machine attempting activation:
     
     Code:

     bash
     slmgr /ato

   • This will attempt to activate the machine using the discovered KMS host.
2. Force Client to Use the KMS Server:
   • If needed, specify the KMS host manually (to confirm its functionality):
     
     Code:

     bash
     slmgr /skms <kms-server>.example.com:1688
     slmgr /ato

3. Check Activation Status:
   • Run:
     
     Code:

     bash
     slmgr /dli

   • This will provide details about the activation status and the connecting KMS server.

Additional Notes​

• The _vlmcs._tcp SRV record enables automatic discovery, but manual activation using the slmgr /skms command will also work without DNS if you configure clients directly with the KMS host.
• If you actively use KMS in a larger setup or have clients across domains, ensure that the SRV record propagates properly and that there are no issues with DNS replication across your infrastructure.

Step 1: Verify if KMS is Installed and Configured on This Server​

Run the Following Commands:​

1. Check if the KMS Host Key is Installed:
   
   Code:

   bash
   slmgr /dli

   • Look for a line indicating a "KMS host key". If you don’t see it, this server is not a KMS Host.
   • If the server says KMSCLIENT, it means the generic volume license key is being used, which means this server is a client and not currently set up as a KMS Host.
2. Check if Volume Activation Services is Functional:
   • Open Server Manager > Check the Volume Activation Tools under Roles.
   • Attempt to run through the configuration wizard. If this server has no valid KMS Host Key, it cannot act as the host.

Option to Promote to KMS Host:​

1. Install the KMS Host Key for your licensing scenario:
   
   Code:

   bash
   slmgr /ipk <Your_KMS_Host_Key>

   Replace <Your_KMS_Host_Key> with a valid key from Microsoft.
2. Activate the KMS host:
   
   Code:

   bash
   slmgr /ato

3. Publish the DNS SRV Record:
   
   Code:

   bash
   slmgr /cdns

Step 2: Locate the Active KMS Host​

Using DNS to Find the KMS SRV Record​

1. On a machine connected to the domain, run:
   
   Code:

   bash
   nslookup -type=srv _vlmcs._tcp

   • This will query the SRV record for the KMS Host.
   • If successful, the FQDN of the KMS Host server will be returned.

Check Other Domain Controllers or Infrastructure Servers​

1. If your DNS lacks a proper _vlmcs._tcp SRV record, manually investigate the other servers that might host KMS.
   • Look for Volume Activation Tools in the Server Manager Roles and Features pane.
   • Log into potential infrastructure servers and run:
     
     Code:

     bash
     slmgr /dlv

     This should return the necessary information for any machine configured as a KMS Host.
2. Ask Your Licensing Administrator:
   If no records or information can be found, consult whoever handles licensing to determine if the KMS is hosted externally or if it may need to be newly configured.

Step 3: Temporarily Configure This Server as KMS Host​

1. Install the KMS Host Key:
   
   Code:

   bash
   slmgr /ipk <Your_KMS_Host_Key>

2. Activate the KMS Host:
   
   Code:

   bash
   slmgr /ato

3. Verify via slmgr /dlv:
   • Ensure it now reports Key Management Service enabled.

Troubleshooting Summary​