14.12.2020

Exchange 2013 Serial Key Location

64

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.

  • If you have a perpetual license disk of Microsoft Office 2013, you can find the product key on the disk. It is a 25 alpha numeric characters. If you have a digital license or if you're subscribed to Office 365, the product key is associated to your Microsoft account. You need to sign-in to your account to get the product key.
  • Unlike Exchange 2010, Exchange 2013 does not require the client namespaces to move with the DAG during an activation event – a CAS2013 in one Active Directory site can proxy a session to a Mailbox server that is located in another Active Directory site.

In this article. Applies to: Exchange Server 2013 A product key tells Exchange Server 2013 that you've purchased a Standard or Enterprise Edition license. If the product key you purchased is for an Enterprise Edition license, it lets you mount more than five databases per server in addition to everything that's available with a Standard Edition license.

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

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.

Several reasons may cause Exchange not mounting issue in MS Exchange 2007, 2010, 2013, 2016 or 2019. In this guide, you will learn a few methods to fix the problem where the Exchange database doesn’t mount after database restore.

After restoring Exchange Server 2019/2016/2013/2010/2007 database from offline backup, you need to mount it to resume the email flow and client access. However, sometimes you may come across ‘unable to mount database’ error while mounting the restored Exchange database.

Reasons for ‘Database is Not Mounting’ Issue

There could be various reasons that can cause Exchange database not mounting problem, such as:

  • Exchange database is in dirty shutdown state
  • Transaction log files are corrupt, missing, or deleted
  • Database is corrupt
  • Not enough free disk space on the server

You can resolve this issue by following the steps given below. However, if this doe not help or fails, you can always rely on a Exchange repair software, such as Stellar Repair for Exchange. Unlike Eseutil, the software is GUI based and does not require additional permissions, roles or storage space on the server. You can install the software on any system, scan and extract mailboxes from EDB and then save them to Outlook importable PST format. You can also export the mailboxes to a new or existing database on your live server in a few clicks.

How to Resolve ‘Database is Not Mounting’ Issue?

Exchange not mounting is usually caused by database corruption. If log files are damaged, missing, deleted, or there is some discrepancy between the transaction logs and database files, the Exchange database enters into Dirty Shutdown state. And when the database is in a dirty shutdown state, you cannot mount it. In case you try, it will fail to mount the Exchange database.

So, the first thing you need to do is to ensure there’s enough storage space and then verify whether the Exchange database is in a clean shutdown state or not.

For this, you can use the Eseutil command-line tool to examine the current state of the database and perform soft recovery and hard repair commands to repair the damaged or corrupt database.

But before following the below steps, create a backup of Exchange EDB file.

Step 1: Check Database

To check and verify the database’s current state, use the following Eseutil command,

The command will return the result of database’s current state. If you find the database is in a dirty shutdown state, fix the dirty shutdown by using Eseutil command for Soft Recovery or Hard Recovery.Download mac os x yosemite mouse driver.

Step 2: Perform Soft Recovery by using Eseutil

Exchange 2013 Serial Key Location Key

To execute the soft recovery, it is mandatory to run the ESEUTIL /r command from the folder in which the transaction log files exist. Also, use it only when the databases to be recovered are in their original path locations. The complete command is as follows,

  • E00 specifies the log prefix of the transaction log file E00.log.
  • /l and /d specifies the log file and database location path. The log and the database location is – Drive:Exchange ServerFirstStorageGroup
  • /i switch in the command is used to resolve the streaming error that may occur during command execution.

Once the command is executed successfully, run eseutil /mh again to verify if the database is in a clean state now. If it is, restart Exchange System Manager (ESM) and mount the database.

In most cases, this solution works fine. But in case it fails, you can perform hard recovery on the database using Eseutil command

2013

Step 3: Perform Hard Repair using Eseutil

This process requires a lot of free storage space, almost two or three-times the size of the database. This is due to the temporary database that Eseutil creates before performing hard repair. So make sure you have enough space before executing hard repair command.

The command is as follows,

Press ‘Enter’ to execute the command and start the hard repair. Once the process is completed, run the eseutil /mh command to check the database state. It should be clean.

IMPORTANT NOTE: The worst thing about hard repair is that if it finds any damaged pages in the database, it will delete them. So make sure the database or data is not so important if you’re going for a hard repair method because it may lead to additional data loss situations.

But there is a good alternative available of ESEUTIL.

Exchange 2013 Key

To overcome the limitations of ESEUTIL and avoid hard recovery, it is always recommended to go for a professional Exchange database recovery tool such as Stellar Repair for Exchange. This Exchange database repair and recovery software fixes database (EDB) without any data loss.

Exchange 2013 Serial Key Location Codes

Whether the database is corrupted, facing dirty shutdown issues, or even unable to mount, Stellar Repair for Exchange software is the permanent solution to fix all problems related to the Exchange server database.

Exchange 2013 Serial Key Location Finder

Exchange 2013 Serial Key Location

Exchange 2013 Serial Key Location Code

This software doesn’t make any changes in the original format of the database and repairs the severely corrupted Exchange EDB file while maintaining the data integrity. Also, it supports Exchange server 2007, 2010, 2013, 2016, and the latest version released in 2019.

Exchange Server 2013 Key

To know more, visit the official page to download the Stellar Repair for Exchange software. In case you’ve any query related to Exchange database, post your query in the comments section below.

1mpress.netlify.app – 2018