In this case, give the KMS host Write access to the DNS database, or create the service (SRV) resource record (RR) manually. KMS hosts are unable to create SRV recordsĭomain Name System (DNS) may restrict Write access or may not support dynamic DNS (DDNS). Otherwise, each client computer looks identical, and the KMS host does not count them as separate KMS clients. To reset the client computer ID (CMID) and other product-activation information, run sysprep /generalize or slmgr /rearm. The general syntax for this command is as follows: slui.exe 0x2a ErrorCodeįor example, if event ID 12293 contains error code 0x8007267C, you can display a description of that error by running the following command: slui.exe 0x2a 0x8007267Cįor more information about specific error codes and how to address them, see Resolving common activation error codes. IT pros can run Slui.exe to display a description of most activation-related error codes. Windows logs KMS events to the Key Management Service log in the Applications and Services folder. Make sure that routers do not block traffic using TCP port 1688 (if the default port is used) and that stateful traffic to the KMS client is allowed.Įxcept for KMS events that have event ID 12290, Windows logs all activation events to the Application event log under the event provider name Microsoft-Windows-Security-SPP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |