Applies to:tekkenbasara.mobi 365 Apps for enterprise

In this article

This article is written & maintained by Eric Splichal, Support Escalation Engineer & Matt Philipenko, Sr Premier Field Engineer.

Bạn đang xem: Download microsoft office 2020 fully crack sinhvienit

It"s common for users to lớn switch devices or for an enterprise lớn add or change M365 or O365 tenants. Another scenario is when enterprise organizations roam licenses or credentials khổng lồ simplify the sign-in process. After a user is activated, multiple locations must be cleared khổng lồ remix the application lớn a clean state.


Note

To automatically perkhung all of the checks listed below & run the appropriate scripts needed khổng lồ rephối the activation state, you can download and run the tekkenbasara.mobi Support và Recovery Assistant.


Step 1: Remove sầu Office 365 license for subscription-based installations


Note

If Shared Computer Activation (SCA) is enabled và running, you shouldn"t see any sản phẩm keys installed during the procedure. If you"re trying lớn mix up SCA on a computer, make sure to lớn clean up existing keys first.


You can use the ospp.vbs script lớn remove sầu the Office 365 license. The ospp.vbs script is located in the Program Files ekkenbasara.mobi OfficeOffice16 thư mục. If you installed the 32-bit version of Office on a 64-bit operating system, go lớn the Program Files (x86) ekkenbasara.mobi OfficeOffice16 folder.


Important

Before you run the ospp.vbs, ensure that:

If you want to lớn run the script on a remote computer, the Windows firewall allows Windows Management Instrumentation (WMI) traffic on the remote computer.The user tài khoản you will use is a thành viên of the Administrators group on the computer on which you run the script.You run ospp.vbs script from an elevated comm& prompt.

In an elevated command prompt, set the correct directory by using one of these commands, based on your Office installation location:

cd "C:Program Files (x86) ekkenbasara.mobi OfficeOffice16"or

cd "C:Program Files ekkenbasara.mobi OfficeOffice16"If a partial hàng hóa key is returned from /dstatus, run the following command:

cscript ospp.vbs /unpkey:"Last 5 of installed sản phẩm key"For example:

cscript ospp.vbs /unpkey:WB222Repeat the comm& until all keys are removed.

*

If the output contains the message "sản phẩm key uninstall successful", cthua the Comm& Prompt window & go lớn Step 2.


Note

For Shared Computer Activation (SCA), remove the tokens listed here:%localappdata% ekkenbasara.mobiOffice16.0Licensing


Step 2: Remove sầu cached identities in HKCU registry


Warning

Follow this section"s steps carefully. Incorrect registry entries can cause serious system issues. As a precaution, baông xã up the registry for restoration.


In Registry Editor, locate the following registry:

HKEY_CURRENT_USERSoftware ekkenbasara.mobiOffice16.0CommonIdentityIdentities

Remove sầu all identities under the Identities registry entry.


Note

If you have Shared Computer Licensing enabled, remove the same identities from the registry HKEY_USERSThe user"s SID.


Step 3: Remove sầu the stored credentials in Credential Manager

Open Control Panel > Credential Manager.

Xem thêm: Tìm Hiểu Thư Mục Winsxs Là Gì ? Bạn Có Nên Xoá Winsxs Hay Không?

Remove all Windows credentials listed for Office16 by selecting the drop-down arrow & Remove.

*

Step 4: Clear persisted locations

Clear the following persisted locations if they exist:

Credential Manager

%appdata% ekkenbasara.mobiCredentials%localappdata% ekkenbasara.mobiCredentials%appdata% ekkenbasara.mobiProtectHKEY_CURRENT_USERSoftware ekkenbasara.mobiProtected Storage System Provider

Office 365 activation tokens & identities

%localappdata% ekkenbasara.mobiOffice16.0Licensing%localappdata% ekkenbasara.mobiOfficeLicenses (tekkenbasara.mobi 365 Apps for enterprise version 1909 or later)HKEY_CURRENT_USERSoftware ekkenbasara.mobiOffice16.0CommonIdentityHKEY_USERSThe user"s SIDSoftware ekkenbasara.mobiOffice16.0CommonIdentity

OLicenseCleanup.vbs

The four steps above can be automated using OLicenseCleanup.vbs. Simply tải về and run the script with elevated privileges.

Clear Office credentials and activation state for managed devices

The above steps reset the Office activation for unmanaged devices (Domain Joined aka DJ). In a managed environment, more locations store credentials.

Devices are considered managed if they"re Azure AD Joined (AADJ), Hybrid Azure AD Joined (HAADJ), or Workplace Joined (WPJ). These configurations use Web Account Management (WAM), which stores credentials in different locations.

Here"s how to lớn find out if a device is DJ, AADJ, HAADJ, or WPJ:

mở cửa a comm& prompt as an administrator.

Type dsregcmd /status.

Domain Joined (DJ):

*

Azure AD Joined (AADJ):

*

Hybrid Azure AD Joined (HAADJ):

*

Workplace Joined (WPJ):

*

In scenargame ios where all stored credentials (such as domain/tenant migration) must be cleared, clear the additional WAM locations.

To clear all WAM accounts associated with Office on the device, tải về and run the signoutofwamaccounts.ps1 script with elevated privileges.


Note

This script will remove tokens và accounts associated with Office, this is a safe operation. Single sign-on (SSO) of other applications will remain untouched, as well as the device state.This script is only compatible with Windows 10 version 1803 and later. If the OS isn"t compatible, you"ll receive a message saying the tool isn"t supported on that version of Windows.Signoutofwamaccounts.ps1 can be ran separately or in conjuction with OLicenseCleanup.vbs. If you place signoutofwamaccounts.ps1 in the same location as OLicenseCleanup.vbs, running only OLicenseCleanup.vbs will also exedễ thương Signoutofwamaccounts.ps1.

Clear credentials from Workplace Join

To manually clear Workplace Joined accounts, go khổng lồ Access Work or School on the device & select Disconnect khổng lồ remove the device from WPJ.

*

To automate WPJ removal, download WPJCleanUp.zip, extract the folder, và run WPJCleanUp.cmd.


Note

This tool removes all SSO accounts in the current Windows logon session. After this operation, all applications in the current logon session will thảm bại SSO state, và the device will be unenrolled from management tools (MDM) and unregistered from the cloud. The next time an application tries khổng lồ sign in, users will be asked to add the tài khoản again.


Additional Information: Plan your hybrid Azure Active sầu Directory join implementation

Bài viết liên quan

Trả lời

Email của bạn sẽ không được hiển thị công khai. Các trường bắt buộc được đánh dấu *