Trace Id is missing

Maximize the everyday with Microsoft 365

Get online protection, secure cloud storage, and innovative apps designed to fit your needs—all in one plan.
For 1 personFor up to 6 people
A young woman works on a Surface laptop while Microsoft 365 App icons whirl around her head.

Office Licensing Diagnostic Tool

Office Licensing Diagnostic Tool

Important! Selecting a language below will dynamically change the complete page content to that language.

Download

  • Version:

    2016

    Date Published:

    10/15/2021

    File Name:

    OfficeLicenseDiagnostic.zip

    File Size:

    110.9 KB

    OfficeLicenseDiagnostic can be run by an admin to collect Office licensing related data for the Microsoft Office licensing team to analyze to help determine root cause of licensing related issues on customer devices.

    Collecting licensing logs are an integral part of the debugging process and by running the licensing diagnostic tool we will be able to get the necessary information to facilitate the debugging process. In case of centennial this isn’t included and is necessary to run this to understand the licenses installed on the machine.

    Using this tool you can:
    • Understand all the licenses (including both legacy ones and modern ones) that were installed on the machine
    • Install licenses if you have a product key in hand
    • Uninstall a product key from a machine
    • Activate the product key that has already been installed on the machine
    • Collect all the logs that are necessary to get the debugging process started

  • Supported Operating Systems

    Windows 10, Windows Server 2012 R2, Windows Server 2008 R2, Windows Server 2012, Windows 7, Windows 8, Windows 8.1


  • Install Instructions:
    • Download the tool and extract the contents
    • Open a command prompt as a normal user
    • Browse to the location of the extracted files
    • Run ‘licenseInfo.cmd’
    • Exit any running Office application
    • Press a key to continue
    • Boot an application and reproduce the issue (You should go through the same steps as you did when you saw the issue for the logs to make sense)
    • Press any key to continue. The script will start collection logs
    • The file name and location will be in the cmd windows output
    • Talk with your support agent to help get your logs to the right people

Follow Microsoft
Back To Top