Microsoft Edge Probeer Microsoft Edge een snelle en veilige browser die is ontworpen voor Windows 10 Aan de slag

Deze site maakt gebruik van cookies om analyses te kunnen uitvoeren en persoonlijke inhoud en reclame te kunnen weergeven. Door verder te bladeren op deze site, gaat u akkoord met dit gebruik. Meer informatie
Overslaan naar hoofdinhoud
Microsoft
Microsoft-ondersteuning
  • Office
  • Windows
  • Surface
  • Xbox
  • Speciale aanbiedingen
  • Ondersteuning
      • Windows-apps
      • OneDrive
      • Outlook
      • Skype
      • OneNote
      • PCs & tablets
      • Accessoires
      • Xbox & games
      • Games
      • Windows-games
      • Films
      • Microsoft Azure
      • Microsoft Dynamics 365
      • Microsoft 365
      • Cloudplatform
      • Zakelijke oplossingen
      • Gegevensplatform
      • .NET
      • Windows-ontwikkelaarscentrum
      • Documenten
      • Gratis downloads & beveiliging
      • Onderwijs
      • Cadeaubonnen
    • Bekijk alles
    0
    Aanmelden
    Microsoft-ondersteuning

    Error 0x8007232b or 0x8007007B occurs when you try to activate Windows

    Inhoud van Microsoft

    Inhoud van Microsoft

    Van toepassing: Windows 10 Pro released in July 2015Windows 10 Enterprise released in July 2015Windows 8 Enterprise NWindows 8 EnterpriseWindows 8 ProWindows 8 Pro NWindows 8.1 EnterpriseWindows 8.1 ProWindows 8.1 Pro NWindows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 FoundationWindows Server 2012 FoundationHyper-V Server 2012 R2Windows Server 2012 StandardWindows Server 2012 StandardWindows 7 EnterpriseWindows 7 Enterprise NWindows 7 ProfessionalWindows 7 Professional NWindows Server 2008 R2 DatacenterWindows Server 2008 R2 EnterpriseWindows Server 2008 R2 FoundationWindows Server 2008 R2 StandardWindows Vista BusinessWindows Vista EnterpriseWindows Vista Business 64-bit EditionWindows Vista Enterprise 64-bit EditionWindows Server 2008 StandardWindows Server 2008 EnterpriseWindows Server 2008 Standard without Hyper-VWindows Server 2008 for Itanium-Based SystemsWindows Server 2008 Enterprise without Hyper-V Meer


    Home users: This article is intended for use by support agents and IT professionals. If you're looking for more information about Windows 10 activation error messages, see the following Windows website:

    Get help with Windows 10 activation errors

    Symptoms


    When you try to activate a Windows installation (client or server), you receive one or more error messages that resembles the following.

    Error message 1
    Activation Error: Code 0x8007232b
    DNS Name does not exist

    Error message 2
    Windows could not be activated.
    Key management services (KMS) host could not be located in domain name system (DNS), please have your system administrator verify that a KMS is published correctly in DNS.

    Error: 0x8007232b
    Description: DNS name does not exist.

    Error message 3
    Error: 0x8007007B
    The file name, directory name, or volume label syntax is incorrect

    Resolution


    To resolve this problem, use one or more of the following methods, as appropriate for your situation.
     

    Method 1: Change the product key to an MAK

    If KMS activation will not be used, and if there is no KMS server, the product key should be changed to an MAK. For Microsoft Developer Network (MSDN), or for TechNet, the stock-keeping units (SKUs) that are listed below the media are generally volume licensed-media, and the product key that's provided is an MAK key.

    To change the product key to an MAK, follow these steps:
    1. Open an elevated command prompt. To do this, use one of the following methods, as appropriate for your OS.
      Windows 7 or Vista (Windows Server 2003)

      Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.

      Windows 8.1, Windows 10, Windows Server 2012, and Windows Server 2012 R2

      Press the Windows logo key+X, and then click Command Prompt (Admin). Or, right-click the Start button and then click Command Prompt(Admin). If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.

    2. At the command prompt, type the following command, and then press Enter:
      slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx 
      Note The xxxxx-xxxxx-xxxxx-xxxxx-xxxxx placeholder represents your MAK product key.

    Method 2: Configure a KMS host server for the clients to activate against

    KMS activation requires that a KMS host server be configured for the clients to activate against. If there are no KMS host servers configured in your environment, install and activate one by using an appropriate KMS host server key. After you configure a computer on the network to host the KMS software, publish the Domain Name System (DNS) settings. For information about the KMS host server configuration process, see Set up a KMS host on a Windows Server 2008 R2 machine.

    For more information about how to set up a KMS server and how to publish the DNS settings, go to the following Microsoft websites:
     
    • Install a KMS host on a Windows Vista-based or Windows Server 2008-based computer
    • Install KMS Hosts
    • Deploy KMS Activation
    • Volume activation in Windows Vista or Windows Server 2008, see the Volume Activation 2.0 Technical Guidance
    • Planning for Volume Activation in Windows 7 or Windows Server 2008 R2

    Method 3: Manually create a KMS SRV record in a Microsoft DNS server

    If your network has a KMS host computer set up, and if the client cannot locate a KMS host on the network for activation, follow these steps:
     
    1. Verify that the computer that has the KMS host installed and is activated by using a KMS key that's registered in DNS. To do this, follow these steps:
       
      1. Open an elevated command prompt.

        Windows 7 or Windows Vista (Windows Server 2003)

        Select Start > All Programs > Accessories, right-click Command Prompt, and then select Run as administrator. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.

        Windows 8.1 and Windows 10 (Windows Server 2012, Windows Server 2012 R2)

        Press Windows logo key+X, and then select Command Prompt(Admin), or right-click the Start button, and then select Command Prompt(Admin). If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
      2. At the command prompt, type the following command, and then press Enter:
        nslookup -type=all _vlmcs._tcp>kms.txt 
      3. Open the KMS.txt file that's generated by the command. This file should contain one or more entries that resemble the following entry:
        _vlmcs._tcp.contoso.com                            SRV service location:                  priority       = 0                  weight         = 0                  port           = 1688                  svr hostname   = kms-server.contoso.com 
      4. If these "_vlmcs" entries are present, and if they contain the expected KMS host names, go to Method 4.
    2. Check the registry to determine whether the KMS host server is registering with DNS. By default, a KMS host server dynamically registers a DNS SRV record one time every 24 hours. To check this setting, follow these steps:
       
      1. Start Registry Editor.

        Windows 7 or Windows Vista

        Click Start, type regedit, and then press Enter.

        Windows 8.1 and Windows 10

        Right-click Start, select Run, type regedit, and then press Enter.
      2. Locate and then click the following subkey:

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SLIf the DisableDnsPublishing subkey is present and has a value of 1, the KMS service does not register in DNS.

        a If the DisableDnsPublishing subkey is missing, create a new DWORD value named DisableDnsPublishing. If dynamic registration is acceptable, change the subkey value to 0. To do this, right-click DisableDnsPublishing, click Modify, type 0 in the Value data box, and then click OK.
      Note By default, this registry key has an undefined value that results in the dynamic registration every 24 hours.

    If the DNS Server service does not support dynamic updates, or if dynamic updates are not occurring, the "VLMCS._TCP, SRV" record can be manually registered.

    To manually create a KMS SRV record in a Microsoft DNS server, follow these steps:

    1. On the DNS server, open DNS Manager. To open DNS Manager, click Start, click Administrative Tools, and then click DNS.
    2. Click the DNS server where you have to create the SRV resource record.
    3. In the console tree, expand Forward Lookup Zones, right-click the domain, and then click Other New Records.
    4. Scroll down the list, click Service Location (SRV), and then click Create Record.
    5. Type the following information:
       
      Service: _VLMCS

      Protocol: _TCP

      Port number: 1688

      Host offering the service: <FQDN_of_KMS_Host>
    6. When you are finished, click OK, and then click Done.
    To manually create SRV records in a BIND 9.x Compliant DNS server include the following information when you create the record.

    Note If your organization uses a non-Microsoft DNS server, you can create the required SRV records as long as the DNS server is BIND 9.x compliant.
     
    • Name=_vlmcs._TCP
    • Type=SRV
    • Priority = 0
    • Weight = 0
    • Port = 1688
    • Hostname = <FQDN or A-Name of the KMS host>
    Note The Priority and Weight fields are not used by KMS and are ignored by the KMS client. However, they must be included in the zone file.

    To configure a BIND 9.x DNS server to support KMS auto-publishing, configure the BIND server to enable resource record updates from KMS hosts. For example, add the following line to the zone definition in Named.conf or in Named.conf.local:
    allow-update { any; };

    Method 4: Manually assign a KMS server


    By default, the KMS clients use the automatic discovery feature and query DNS for a list of servers that have published the _VLMCS record within the membership zone of the client. DNS returns the list of KMS hosts in a random order. The client picks a KMS host and tries to establish a session on it. If this attempt works, the client caches the server and tries to use it for the next renewal attempt. If the session setup fails, the client picks another server randomly. We highly recommend that you use the automatic discovery feature. However, you can manually assign a KMS server. To do this, open an elevated command prompt on the KMS client.
     
    1. Open an elevated command prompt.

      Windows 7 or Vista (Windows Server 2003)

      Click Start, type cmd in the Start Search box, right-click cmd.exe in the results list, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.

      Windows 10 and Windows 8.1 (Windows Server 2012 R2, Windows Server 2012)

      Press the Windows logo key+X, and then select Command Prompt(Admin), or right-click Start, and then select Command Prompt(Admin). If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
    2. Use the following commands at an elevated command prompt:
       
      • To assign a KMS host by using the FQDN of the host, type the following command:
        cscript \windows\system32\slmgr.vbs -skms <KMS_FQDN>:<port> 
      • To assign a KMS host by using the version 4 IP address of the host, type the following command:
        cscript \windows\system32\slmgr.vbs -skms <IPv4Address><:port> 
      • To assign a KMS host by using the version 6 IP address of the host, type the following command:
        cscript \windows\system32\slmgr.vbs -skms <IPv6Address><:port> 
      • To assign a KMS host by using the NETBIOS name of the host, type the following command:
        cscript \windows\system32\slmgr.vbs -skms <NetbiosName><:port> 
      • To revert to automatic discovery on a KMS client, type the following command:
        cscript \windows\system32\slmgr.vbs –ckms 

    Method 5: Automatically publish KMS in multiple DNS domains

    If the previous methods have not resolved this problem, the problem may be related to the ability of the client to resolve the DNS name of the KMS server or to connect to the KMS server. If this is the problem, follow these steps:

    Note Unless otherwsie stated, do the following steps on a KMS client that has experienced the error that is mentioned in the "Symptoms" section:
     
    1. At a command prompt, type the following command, and then press Enter:
      IPCONFIG /all 
    2. From the command results, note the assigned IP address, the DNS server address, and the default gateway address.
    3. Verify basic IP connectivity to the DNS server by using the ping command. To do this, run the following command.
      ping <DNS_Server_IP_address> 
      Note If this command does not ping the server, this problem must be resolved first.

      For more information about how to troubleshoot TCP/IP issues if you cannot ping the DNS server, see the Microsoft TechNet topic Troubleshooting TCP/IP.
    4. Verify that the search list of the primary DNS suffix contains the DNS domain suffix that the KMS host registered.

      For the computers that have joined the domain, the DNS automatic discovery of KMS requires that the DNS zone contains the SRV resource record for the KMS host. This DNS zone is the DNS zone that corresponds to either the primary DNS suffix of the computer or to the domain of the Active Directory DNS.

      For workgroup computers, the DNS automatic discovery of KMS requires that the DNS zone contains the SRV resource record for the KMS host. This DNS zone is the DNS zone that corresponds to either the primary DNS suffix of the computer or to the DNS domain name that is assigned by the Dynamic Host Configuration Protocol (DHCP). This domain name is defined by the option that has the code value of 15 as defined in Request for Comments (RFC) 2132.
    5. Verify that the KMS host SRV records are registered in DNS. At an elevated command prompt, type the following command, and then press Enter:
      nslookup -type=all _vlmcs._tcp>kms.txt 
    6. Open the Kms.txt file that was generated by this command. This file should contain one or more entries that resemble the following:
       
      _vlmcs._tcp.contoso.com SRV service location:priority = 0weight = 0port = 1688 svr hostname = kms-server.contoso.com 

      Verify the IP address, host name, and port of the KMS host.

      Note If the nslookup command finds the KMS host, it does not mean that the DNS client can find the KMS host. If the nslookup command finds the KMS host, and if you still cannot activate the KMS host server, check the other settings, such as the primary DNS suffix and the search list of the DNS suffix.

      The SRV records are registered in the DNS zone that corresponds to the KMS host domain membership. For example, assume that a KMS host joins the contoso.com domain. In this scenario, the KMS host registers its VLMCS._TCP SRV record under the contoso.com DNS zone. Therefore, the VLMCS._TCP.CONTOSO.COM record is created.

    If the clients are configured to use a different DNS zone, automatically publish KMS in multiple DNS domains. To do this, follow these steps:

    1. Log on to a KMS host.
    2. Open an elevated command prompt.

      Windows 7 or Vista (Windows Server 2003)

      Select Start, type cmd in the Start Search box, right-click cmd.exe in the results list, and then select Run as administrator. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.

      Windows 8.1 and Windows 10 (Windows Server 2012, Windows Server 2012 R2)

      Press the Windows logo key+X, and then select Command Prompt(Admin), or right-click Start, and then select Command Prompt(Admin). If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
    3. At the command prompt, type regedit.exe, and then press Enter.
    4. Locate and then click the following registry subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL
    5. In the navigation pane, select SL.
    6. Right-click a blank area in the details pane, point to New, and then select Multi-String Value.
    7. Type DnsDomainPublishList as the name for the new value, and then press Enter.
    8. Right-click the new DnsDomainPublishList value, and then select Modify.
    9. In the Edit Multi-String dialog box, type each DNS domain suffix that is published by KMS on a separate line, and then select OK.
    10. In the Edit Multi-String dialog box, type each DNS domain suffix that is published by KMS on a separate line, and then select OK.

      Note For Windows 7 and for Windows Server 2008 R2, the format for DnsDomainPublishList differs.

      For more information, see the Volume Activation Technical Reference Guide.
    11. Restart the Software Licensing service by using the Service administrative tool. This operation creates the SRV records.
    12. Verify that the host name that is returned in the last step can be resolved by using a typical method on the KMS client. When the name is resolved, also verify that the IP address that is returned is accurate. If either of these verifications fails, investigate this DNS client resolver issue.
    13. To use the KMS automatic discovery feature, run the following command at an elevated command prompt to clear any previously cached KMS host names:
       
      cscript C:\Windows\System32\slmgr.vbs –ckms 
    14. If you believe that you have an SRV record issue, you can troubleshoot it by using one of the commands that are documented in "Method 4" to statically specify a KMS host. The following commands can be used to determine whether this is a name resolution issue or an SRV record issue. If none of these commands resolves the problem, you may be encountering a blocked port or an inaccessible host (see the "More Information" section).

      Run the following commands:
       
      cscript \windows\system32\slmgr.vbs -skms <KMS_FQDN>:<port>cscript \windows\system32\slmgr.vbs –ato 


      If these commands resolve the problem, this is an SRV record issue. To fix it, you must troubleshoot the SRV record.

      If these commands do not resolve the problem, run the following commands:
       
      cscript \windows\system32\slmgr.vbs -skms <IP Address>:<port>cscript \windows\system32\slmgr.vbs –ato 

      If these commands resolve the problem, this is most likely a name resolution issue.
    The 1688 TCP port is used for the activation communication between the KMS client and the KMS host. If the communication seems to be blocked, check the firewall configurations or anything else that may block the 1688 TCP port.

    More Information


    This problem may occur if one or more of the following conditions are true:
     

    • You use volume-licensed media with a Volume License generic product key to install one of the following operating systems:
      • Windows Server 2012 R2
      • Windows Server 2012
      • Windows Server 2008 R2
      • Windows Server 2008
      • Windows 10
      • Windows 8.1
      • Windows 8
      • Windows 7
      • Windows Vista Enterprise
      • Windows Vista Business
    • The activation wizard cannot connect to a Key Management Service (KMS) host computer.

    When you try to activate the system, the activation wizard uses DNS to locate a corresponding computer that's running the KMS software. If the wizard queries DNS and does not find the DNS entry for the KMS host computer, the wizard reports an error. If you have a KMS host computer set up, the correct DNS entries are not seen by the client computer. If you do not have a KMS host computer set up, you must either set up a KMS host computer or switch to an MAK product key method to activate your volume license installation.

    Microsoft Developer Network (MSDN) and Microsoft TechNet provide volume-licensed media for the following operating system stock-keeping units (SKUs):
     

    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows 10 Enterprise
    • Windows 8.1 Enterprise
    • Windows 8 Enterprise
    • Windows 7 Enterprise
    • Windows Vista Enterprise
    The volume-licensed media does not prompt you for a product key during installation. If you do not change the product key to the MSDN key, you receive an error message when you try to activate the operating system. If you use MSDN or TechNet media, you must change the product key to the MSDN product key. Use the "Method 1" procedure in the "Resolution" section to change the product key.

    Note The MSDN or TechNet product key is the MAK product key.

    References


    For more information about Volume Activation, see the following Microsoft Knowledge Base article:

    929712 Volume Activation information for Windows Vista, Windows Server 2008, Windows Server 2008 R2 and Windows 7
    For more information about volume licensing, go to the Microsoft Volume Licensing website.

    For more information about how to activate copies of Windows Vista or Windows Server 2008 that were installed by using volume-licensed media, go to the Product Activation and Key Information webpage.

    Laatst bijgewerkt: 6 apr. 2017
    • E-mail
    • Afdrukken
    Bedankt! Met uw feedback kunnen we de ondersteuning verbeteren.

    Nieuw

    • Surface Book 2
    • Surface Pro
    • Xbox One X
    • Xbox One S
    • Windows 10-apps
    • Office-apps

    Store en ondersteuning

    • Accountprofiel
    • Downloadcentrum
    • Verkoop en ondersteuning
    • Terugzendingen
    • Bestelling traceren
    • Recyclage
    • Commerciële garanties

    Onderwijs

    • Microsoft in het onderwijs
    • Office voor studenten
    • Office 365 voor scholen
    • Aanbiedingen voor studenten en docenten
    • Microsoft Azure in het onderwijs

    Onderneming

    • Microsoft Azure
    • Onderneming
    • Gegevensplatform

    Ontwikkelaar

    • Microsoft Visual Studio
    • Windows-ontwikkelaarscentrum
    • Developer Network
    • TechNet
    • Microsoft Virtual Academy
    • Microsoft-ontwikkelaarsprogramma
    • Channel 9

    Bedrijf

    • Vacatures
    • Privacy bij Microsoft
    • Investeerders
    • Beveiliging
    Nederlands (Nederland)
    • Gebruiksvoorwaarden
    • Privacy en cookies
    • Handelsmerken
    • © Microsoft 2018
    Deze site in andere landen/regio 's
    Algérie - Français
    Argentina - Español
    Australia - English
    Belgique - Français
    België - Nederlands
    Bolivia - Español
    Bosna i Hercegovina - Hrvatski
    Brasil - Português
    Canada - English
    Canada - Français
    Chile - Español
    Colombia - Español
    Costa Rica - Español
    Crna Gora - Srpski
    Danmark - Dansk
    Deutschland - Deutsch
    Dominican Republic - Español
    Ecuador - Español
    Eesti - Eesti
    El Salvador - Español
    España - Español
    Estados Unidos - Español
    France - Français
    Guatemala - Español
    Hong Kong SAR - English
    Hrvatska - Hrvatski
    India - English
    Indonesia (Bahasa) - Bahasa
    Ireland - English
    Italia - Italiano
    Latvija - Latviešu
    Lietuva - Lietuvių
    Luxembourg - Français
    Magyarország - Magyar
    Malaysia - English
    Maroc - Français
    México - Español
    Nederland - Nederlands
    New Zealand - English
    Norge - Bokmål
    Panamá - Español
    Paraguay - Español
    Perú - Español
    Philippines - English
    Polska - Polski
    Portugal - Português
    Puerto Rico - Español
    România - Română
    Schweiz - Deutsch
    Singapore - English
    Slovenija - Slovenščina
    Slovensko - Slovenčina
    South Africa - English
    Srbija - Srpski
    Suisse - Français
    Suomi - Suomi
    Sverige - Svenska
    Tunisie - Français
    Türkiye - Türkçe
    United Kingdom - English
    United States - English
    Uruguay - Español
    Venezuela - Español
    Việt Nam - Tiếng việt
    Ísland - Íslenska
    Österreich - Deutsch
    Česká Republika - Čeština
    Ελλάδα - Ελληνικά
    България - Български
    Казахстан - Русский
    Россия - Русский
    Україна - Українська
    ישראל - עברית
    الإمارات العربية المتحدة - العربية
    المملكة العربية السعودية - العربية
    مصر - العربية
    भारत - हिंदी
    ไทย - ไทย
    中国 - 简体中文
    台灣 - 繁體中文
    日本 - 日本語
    香港特別行政區 - 繁體中文
    대한민국 - 한국어