![]() If your operating system isn't compatible, you'll see the notification "Unsupported Windows 10 version!". The script can only be run on Windows 10 version 1803 and later. On AADJ and HAADJ devices, it will not affect the Single Sign-On (SSO) state of the applications and the device state. ![]() The signoutofwamaccounts.ps1 script will remove the tokens and accounts associated with Office and is safe to run. There are no steps that you can run manually to clear WAM accounts associated with Office on the device for AADJ and HAADJ devices.ĭownload the signoutofwamaccounts.zip file, extract, and run the signoutofwamaccounts.ps1 script as administrator. These configurations use Web Account Management (WAM), which stores credentials in different locations. Devices are considered managed if they're Azure AD Joined (AADJ), Hybrid Azure AD Joined (HAADJ), or Workplace Joined (WPJ). Section B: Clear cached Office credentials for managed devicesįor managed devices, there are additional locations from which you need to remove cached Office credentials. HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Licensing.Repeat the cscript ospp.vbs /unpkey command as needed to remove the licenses for the applications listed in the output from step 3. You should see the message “Product key uninstall successful” when the license is removed. Run the following command to remove the license for an application by using the associated partial product key: If a partial product key is returned for the applications whose licenses you want to remove, note the value displayed for Last 5 characters of the installed product key to use in step 4, below. If it displays No installed product keys detected, skip steps 4 and 5 and go to step 6, "Delete the following registry entry", below. NOTE The output could include licenses for multiple applications. Run the following command to get a list of the licenses currently in use: cd "C:\Program Files (x86)\Microsoft Office\Office16".For a 32-bit Office installation on a 64-bit operating system:.cd "C:\Program Files\Microsoft Office\Office16".For a 64-bit Office installation on a 64-bit operating system:.Run one of the following commands from an elevated command prompt, as appropriate for your Office installation: The user account you use is a member of the Administrators group on the computer on which you run the script.īefore you run the ospp.vbs script, you must set the correct directory. ![]() If you want to run the script on a remote computer, the Windows firewall allows Windows Management Instrumentation (WMI) traffic on the remote computer.%localappdata%\Microsoft\Office\16.0\LicensingĬheck for and remove legacy licensing by using the ospp.vbs script.For Shared Computer Activation license type:.%localappdata%\Microsoft\Office\Licenses (Microsoft 365 Apps for enterprise version 1909 or later).Remove all license token files and folders if found in the following locations: Make sure to check all the noted locations for potential license types, which include vNext, Shared Computer Activation, and legacy licenses. Part 1: Remove previous Office activationsĬheck for and remove existing licenses on the device. The process consists of the following sections. If you prefer to perform the steps for the cleanup process manually, use the information in this method. Method: Clear prior activation information manually To remove Workplace Joined accounts: download WPJCleanUp.zip, extract the WPJCleanUp folder, and run WPJCleanUp.cmd.If you save signoutofwamaccounts.ps1 in the same location as OLicenseCleanup.vbs, then it will be executed automatically when you run OLicenseCleanup.vbs. To clear the WAM accounts on the device that are associated with Office: download the signoutofwamaccounts.zip file, extract, and run the signoutofwamaccounts.ps1 script with elevated permissions.To remove previous licenses and cached account information: download the OLicenseCleanup.zip file, extract the OLicenseCleanup.vbs script, and run it using elevated permissions.Use the “Select if using automated scripts” link to navigate back to this method. For details about the specific steps that each script automates, select the associated Details link. We recommend that you run the OLicenseCleanup.vbs and signoutofwamaccounts.ps1 scripts listed below, while WPJCleanUp.cmd is required only if your device is Workplace Joined. Run the following scripts that automate each section of the process. Method: Use scripts to automate the cleanup process
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |