Run cscript slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx, where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is Windows product key (there should be 25 numbers). To resolve this issue, follow these steps on the computer(s) in question, replace the KMS product key and convert it to a KMS or MAK client: In many cases, Windows KMS hosts may be unintentionally set up by users who mistakenly entered a KMS host product key, instead of a Windows client product key. Running this nslookup command frequently reveals _vlmcs SRV entries that are tied to unauthorized Windows or Office KMS hosts. Review the kms.txt file, and it should contain one or more entries similar to the following: _vlmcs._ SRV service location: Nslookup -type=srv _vlmcs._tcp >%temp%\kms.txt To determine whether a KMS client can locate a KMS host or whether unwanted KMS hosts exist on the network, run a command similar to the following: Discover Office and Windows KMS hosts through DNSīy default, Windows and Office clients discover KMS hosts through DNS and a related _vlmcs SRV record. The following steps are similar in Office KMS 2010, 2013, 2016, and 2019.
0 kommentar(er)
