Ms Office Serial Key With Vbscript

Posted : admin On 16.12.2020
Ms Office Serial Key With Vbscript 6,7/10 6981 reviews
  1. Ms Office Serial Key With Vbscript
  2. Vbscript Office 2016 Product Key
  3. Microsoft Office 2016 Product Key Vbscript
  4. Ms Office Serial Key With Vbscript

For help with finding your product key, select your version of Office below: Office product keys. Microsoft HUP product keys. Office 2010 product keys. Office 2007 product keys. Office for Mac 2011 product keys. My product key isn't working. First, make sure that you're entering the key correctly on the right site. The serial keys are encrypted on registry, you can’t read it normally, however, you can retrieve it with product key tool or VBScript. To check on your Office product key with VBAcript: Step 1: Type the code to some notepad. Cscript “C: Program Files Microsoft Office Office15 OSPP.VBS” /dstatus For 64 bit Windows: cscript “C: Program Files (x86) Microsoft Office Office15 OSPP.VBS” /dstatus. The command prompt box will show you the last five digits of the product key associated with the installation on that PC. For more detail information. MS 'improved' the way it stores the product key on the computer. You can now only see the last 5 char. So you can use existing Key extractors or the technique listed in the link that Sushma provided. But, either way, all you will see is the last 5 characters of the key. If you are lucky that should be enough to make unique matches.

I’ve got several licenses for Office and Outlook but I’m not sure which one which ones I’ve used and which ones are free.

How can I find out which license I’ve used for which computer and how can I change the key if needed?

Check

While you could simply try one of your Product/License Keys and see if it gets accepted, it’s not a very sophisticated approach.

The proper method to determine or change the Product Key depends on your version of Office or Outlook. However, for either version there is no need to completely reinstall Office.

Note: Office 365 installations don’t require a license key as they activate automatically when you log on to Office with your Microsoft Account. The same applies to Office 2016 and Office 2019 licenses that are linked to your Microsoft Account.

Find license keys for Office 2010, Office 2013, Office 2016 and Office 2019 via a script

Office 2010 and later include a vbs-script which will reveal the last 5 characters of your Product Key. It’s pretty safe to state that these 5 characters would already be more than enough to find out which Product Key you have used (as you should already have safely stored the full Product Key code somewhere else together with your other license information).

You can run the vbs-file in the following way;

  1. Open a command prompt. For instance via:
    • Start-> type: cmd
  2. In the command prompt, type the following:
    • Office 2016/2019 (32-bit) on a 32-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice16OSPP.VBS' /dstatus
    • Office 2016/2019 (32-bit) on a 64-bit version of Windows
      cscript 'C:Program Files (x86)Microsoft OfficeOffice16OSPP.VBS' /dstatus
    • Office 2016/2019 (64-bit) on a 64-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice16OSPP.VBS' /dstatus
    • Office 2013 (32-bit) on a 32-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice15OSPP.VBS' /dstatus
    • Office 2013 (32-bit) on a 64-bit version of Windows
      cscript 'C:Program Files (x86)Microsoft OfficeOffice15OSPP.VBS' /dstatus
    • Office 2013 (64-bit) on a 64-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice15OSPP.VBS' /dstatus
    • Office 2010 (32-bit) on a 32-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice14OSPP.VBS' /dstatus
    • Office 2010 (32-bit) on a 64-bit version of Windows
      cscript 'C:Program Files (x86)Microsoft OfficeOffice14OSPP.VBS' /dstatus
    • Office 2010 (64-bit) on a 64-bit version of Windows
      cscript 'C:Program FilesMicrosoft OfficeOffice14OSPP.VBS' /dstatus
  3. You should now get a screen with some license details such as the license name, type and the last 5 characters of the Product Key.


Office offers a scripted method to lookup your Product Key.

Changing the Product Key for Office 2010 / 2013 / 2016 / 2019

Changing the Product Key for msi-based installations of Office can be done directly from the Control Panel/Apps & Features or via a command line.

Product Keys for Click-to-Run based installations of Office can only be modified via the command line.

  • Windows 10
    Start-> Settings-> Apps & Features
  • Windows 7 and Windows 8
    Start-> Control Panel-> Uninstall a Program

Here, locate your Office application and press Modify or Change. Setup will now start with the option “Enter a Product Key” which allows you to enter a different product key.

To change the Product Key via a command line, you can use the same OSPP.VBS script as mentioned before. Instead of using the /dstatus switch, you must use the /inpkey:value switch where you should replace value for your Product Key.

Changing the Product Key for Office XP/2002 / 2003 / 2007

Changing the Product Key for Office 2007 or previous requires you to go into the Registry.

  1. Browse to the following key:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice<version>Registration
  2. Now is a good point to make a backup of that key;
    Right click on the key, choose Export… and save the file to for instance your Desktop.
  3. Expand the Registration key in the Registry and you’ll see one or more sub keys which contain a lot of characters between curly brackets: { and }
    Each sub key stands for an installed Office application.
    The proper name for this identifier string is called a “GUID”.
  4. Click on the sub key to reveal its contents in the right pane.
    The SuitName key will reveal the name of the package that you have installed. If you have multiple GUID sub keys listed, you can use this key name to determine for which installation you’ll be changing the Product Key.
  5. In the pane on the right, delete the following keys:
    • DigitalProductID
    • ProductID
  6. Close the Registry and start Outlook (or any other Office application); you’ll now be prompted to fill in your Product Key and activate Office again.


Delete the DigitalProductID and ProductID key to reset your Product Key.

Determine the Product Key with a 3rd party tool

Determining the used Product Key when using Office 2007 or previous isn’t directly supported by Microsoft. However, you can use a little program called Magic Jelly Bean Keyfinder to find out your used Product Key. Simply install and run the application to find out the Product Key (note: during the installation, there will be a prompt to also install a sponsored application which you can choose not to install).

Another free application which you can use is Belarc Advisor. This application does a bit more thorough scan of your computer for which it generates a report that also includes license keys for several of your installed applications. If you are in a large corporate network, you might want to disconnect your network connection as it will also try to build a network map which may cause the application to appear to hang at the “checking the local network of this computer” stage.

-->

Applies to:Volume licensed versions of Office 2019 and Office 2016, including Project and Visio

The Office Software Protection Platform script (ospp.vbs), the Software License Manager script (slmgr.vbs), and the Volume Activation Management Tool (VAMT) can help you configure and test volume licensed versions of Office, including Project and Visio. Before you read this article, we recommend that you read Overview of volume activation of Office, Activate volume licensed versions of Office by using MAK, and Activate volume licensed versions of Office by using Active Directory.

The ospp.vbs script

The Office Software Protection Platform script (ospp.vbs) enables you to configure volume licensed versions of Office products, including Project and Visio. The ospp.vbs script is located in the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, go to the Program Files (x86)Microsoft OfficeOffice16 folder.

Running ospp.vbs requires the cscript.exe script engine. To see the Help file, type the following command, and then press ENTER:

cscript ospp.vbs /?

The general syntax is as follows:

cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]

Option Specifies the option and value to use to activate a product, install or uninstall a product key, install and display license information, set KMS host name and port, and remove KMS host name and port. The options and values are listed in the tables in this section.

ComputerName Name of the remote computer. If a computer name is not provided, the local computer is used.

User Account that has the required permission on the remote computer.

Password Password for the account. If a user account and password are not provided, the current credentials are used.

Important

Before you run the ospp.vbs, ensure that:

  • If you want to run the script on a remote computer, the Windows firewall allows Windows Management Instrumentation (WMI) traffic on the remote computer.
  • The user account you will use is a member of the Administrators group on the computer on which you run the script.
  • You run ospp.vbs script from an elevated command prompt.

Global options for ospp.vbs

Global optionDescription
/act
Activates installed Office product keys.
/inpkey:value
Installs a product key (replaces existing key) with a user-provided product key. Value option is required.
/unpkey:value
Uninstalls an installed product key with the last five digits of the product key to uninstall (as displayed by the /dstatus option). Value parameter is required.
/inslic:value
Installs a license with user-provided path of the .xrm-ms license. Value parameter is required.
/dstatus
Displays license information for installed product keys.
/dstatusall
Displays license information for all installed licenses.
/dhistoryacterr
Displays the failure history for MAK/retail activation.
/dinstid
Displays Installation ID for offline activation.
/actcid:value
Activates product with user-provided Confirmation ID. Value parameter is required.
/rearm
Resets the licensing status for all installed Office product keys.
/rearm:value
Resets the licensing status for an Office license with a user-provided SKUID value. Value parameter is required.
Use this option with the SKUID value specified by using the /dstatus option if you have run out of rearms and have activated Office through KMS or Active Directory-based activation to gain an additional rearm.
/ddescr:value
Displays the description for a user-provided error code. Value parameter is required.

The following table describes the ospp.vbs options for configuring the KMS client.

KMS client options for ospp.vbs

KMS client optionDescription
/dhistorykms
Displays KMS client activation history.
/dcmid
Displays KMS client computer ID (CMID).
/sethst:value
Sets a KMS host name with a user-provided host name. Value parameter is required.
This sets HKLMSoftwareMicrosoftOfficeSoftwareProtectionPlatformKeyManagementServiceName (REG_SZ).
/setprt:value
Sets a KMS port with a user-provided port number. The default port number is 1688. Value parameter is required.
This sets HKLMSoftwareMicrosoftOfficeSoftwareProtectionPlatformKeyManagementServicePort (REG_SZ).
/remhst
Removes KMS host name and sets port to default. The default port is 1688.
/cachst:value
Allows or denies KMS host caching. Value parameter is required (TRUE or FALSE).
/actype:value
(Windows 8.1 and later versions only) Sets volume activation type. Value parameter is required.
Values: 1 (for Active Directory-based), 2 (for KMS), 0 (for both).
/skms-domain:value
(Windows 8.1 and later versions only) Sets the specific DNS domain in which all KMS SRV records can be found. This setting has no effect if the specific single KMS host name is set by the /sethst option. Value parameter is the Fully Qualified Domain Name (FQDN) and is required.
/ckms-domain
(Windows 8.1 and later versions only) Clears the specific DNS domain in which all KMS SRV records can be found. The specific KMS host is used if it is set by the /sethst option. Otherwise, auto-discovery of the KMS host is used.

Scenarios that use ospp.vbs

The following scenarios assume that you are running ospp.vbs in an elevated command prompt.

Note

Any changes that you make affect only the Office client products. You have to configure the Windows client separately by using the slmgr.vbs script described in The slmgr.vbs script later in this article.

To change the product key to a MAK key on a remote computer

Ms Office Serial Key With Vbscript

  1. If the remote computer is named contoso1, run the following command to enter the product key. This assumes that you have administrator credentials on the remote computer. If your credentials on the remote computer differ from your logon name and password, you must type your logon name and password at the command line, and then press ENTER:

    cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx contoso1

  2. To activate the remote computer, type the following command, and then press ENTER:

    cscript ospp.vbs /act contoso1

To diagnose KMS activation errors

  1. If the computer has the KMS client key installed, check the licensing status. To do this, type the following command, and then press ENTER:

    cscript ospp.vbs /dstatusall

  2. To check the KMS activation history, type the following command, and then press ENTER:

    cscript ospp.vbs /dhistorykms

  3. To trigger activation, type the following command, and then press ENTER:

    cscript ospp.vbs /act

  4. Check the error message for error code 0xC004F042. If in the notification dialog boxes you see an error code that is shown to users, you can also use that code to check the error message. To do this, type the following command, and then press ENTER:

    cscript ospp.vbs /ddescr:0xC004F042

To turn on or off KMS host caching on the KMS client

  1. On the KMS client computer, to turn caching on, type the following command, and then press ENTER:

    cscript ospp.vbs /cachst:TRUE

  2. On the KMS client computer, to turn caching off, type the following command, and then press ENTER:

    cscript ospp.vbs /cachst:FALSE

To test KMS host name, and then set to auto-discovery

  1. If you are testing a KMS host named kmstest.contoso.com, and you want to specify it in the KMS client, type the following command, and then press ENTER:

    cscript ospp.vbs /sethst:kmstest.contoso.com

    Note

    If you change the default port on the KMS host computer, you must run ospp.vbs with the /setprt option. > For example: cscript ospp.vbs /setprt:1750

  2. To trigger activation, type the following command, and then press ENTER:

    cscript ospp.vbs /act

  3. To check the KMS activation history to see whether the host was successfully contacted, type the following command, and then press ENTER:

    cscript ospp.vbs /dhistorykms

  4. Now you want this KMS client to use Domain Name System (DNS) for auto-discovery of the production KMS host. To remove the KMS host name, type the following command, and then press ENTER:

    cscript ospp.vbs /remhst

The slmgr.vbs script

The Software License Manager (slmgr.vbs) script is used to configure and retrieve volume activation information for the Office KMS host and the Windows host. For more information, see Configuring KMS Hosts for Windows.

You can run the script locally on the target computer or remotely from another computer. You have to be an administrator to use the script. If a standard user runs slmgr.vbs, some license data might be missing or incorrect, and many operations are prohibited.

The slmgr.vbs script can use the Windows-based script host, wscript.exe, or the command-based script host, cscript.exe, and administrators can specify which script engine to use. If no script engine is specified, slmgr.vbs runs by using the default script engine, wscript.exe. We recommend the cscript.exe script engine.

You must restart the Software Licensing Service for any changes to take effect. To restart the Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in or run the following command:

Kbc download free. net stop sppsvc && net start sppsvc

The slmgr.vbs script requires at least one parameter. If you run the script without any parameters, it displays Help information. The following table lists slmgr.vbs command-line options, and a description of each. Most of the parameters in the table configure the KMS host computer. However, the parameters /sai and /sri are passed to KMS clients after the KMS clients contact the KMS host computer. The general syntax of slmgr.vbs is as follows (assuming you are using the cscript.exe as the script engine):

cscript slmgr.vbs /parameter

cscript slmgr.vbs [ComputerName] [User] [Password] [Option]

ComputerName Name of the remote computer. If you do not provide a computer name, the local computer is used.

User Account with required permission on the remote computer.

Password Password for the account. If you do not provide a user account and password, current credentials are used.

Option Options are shown in the following table.

Slmgr.vbs command options — standard

OptionDescription
/ ipk [ProductKey]
Installs the product key for Windows (default) or other application identified by the product key.
/ ato [ActivationID]
Activates the KMS host for Windows (default), or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7.
/ dti [ActivationID]
Displays the Installation ID that is used for telephone activation of the KMS host computer for Windows (default) or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7. You enter the Installation ID into the telephone to receive the Confirmation ID, which is used for activating the KMS host computer by using the /atp parameter.
/ atp [ConfirmationID][ActivationID]
After the Confirmation ID is received, activates the KMS host for Windows (default) or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7.
/ dlv [ActivationID]
Displays detailed license information for Windows (default), or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7.
For example, run the following command at the elevated command prompt, in the C:windowssystem32 folder to get the status of the Office KMS host:
cscript slmgr.vbs /dlv 70512334-47B4-44DB-A233-BE5EA33B914C
/ dli [ActivationID]
Displays license information for Windows (default), or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7.
/ upk [ActivationID]
Uninstalls the product key for Windows (default) or the application that is identified when its Activation ID is provided. The Office 2019 Activation ID is 70512334-47B4-44DB-A233-BE5EA33B914C, and the Office 2016 Activation ID is 98EBFE73-2084-4C97-932C-C0CD1643BEA7.
CAUTION: If you intend to uninstall the product key for Office, for example, and forget to enter the Activation ID, all installed product keys are uninstalled. This includes the product key for Windows.
/ xpr [ActivationID]
Displays the expiration date for the current license state.
/ sprt [PortNumber]
Sets the TCP communications port on a KMS host computer. It replaces PortNumber with the TCP port number to use. The default setting is 1688.
/ cdns
Disables automatic DNS publishing by a KMS host computer.
/ sdns
Enables automatic DNS publishing by the KMS host computer.
/ cpri
Lowers the priority of KMS host computer processes.
/ sai [ActivationInterval]
Changes how often a KMS client attempts to activate itself when it cannot find a KMS host computer. It replaces ActivationInterval with a value expressed in minutes. The default setting is 120 minutes.
/ sri [RenewalInterval]
Changes how often a KMS client attempts to renew its activation by contacting a KMS host computer. It replaces RenewalInterval with a value expressed in minutes. The default setting is 10080 minutes (7 days). This setting overrides the local KMS client settings.

The following table shows the command options for activating an AD DS forest by using Active Directory-based activation.

Slmgr.vbs command options — Active Directory-based activation

Vbscript Office 2016 Product Key

OptionDescription
/ ad-activation-online [ProductKey]
Activates an AD DS forest through the user-provided product key.
/ ad-activation-apply-get-iid [ProductKey]
Displays installation ID for AD DS forest.
/ ad-activation-apply-cid [ProductKey][ConfirmationID]
Activates an AD DS forest through the user-provided product key and the Confirmation ID.

Microsoft Office 2016 Product Key Vbscript

Volume Activation Management Tool (VAMT)

Volume Activation Management Tool (VAMT) provides a graphical user interface to manage volume activation. For more information about VAMT, see Volume Activation Management Tool (VAMT) Technical Reference.

Ms Office Serial Key With Vbscript

Related topics