TPM issue resolutions (4374732)

TPM issue resolutions

When a computer is migrated between domains, the Azure Workplace Join gets partially destroyed but not fully cleaned up.  After migration, when users launch O365 applications such as Outlook, they are asked to register with their organization.  When they attempt to do this a TPM error occurs and this error can be difficult to get around.

 

It's common for users to switch devices or for an enterprise to add or change M365 or O365 tenants. 

The way Microsoft explained it is that there are registration, identity, and tokens set for each user profile under Office 365 that are exclusive to that user’s profile. When another domain binds to that user profile it acts as a security measure because the system thinks of it as an impersonation attempt. If the profile is built new the tokens and registrations are rebuilt or this script can be ran under our scenario to reset what a new profile would do by stripping all the remnants out. 

Solution 1:

Reset Microsoft 365 Apps for enterprise activation state - Office

RUN AT YOUR OWN RISK.  
It would be best to contact Microsoft, to ensure you have the latest version of the Script.

Solution 2:

Workaround for this issue is to rename the corresponding folder for the affected user:

"C:\users\$dir\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy"

"C:\users\$dir\AppData\Roaming\Microsoft\SystemCertificates"

This needs to be done with the affected user logged off. Do not use a switch user, logon as a different administrative user or access the file from a network share. The folder will get recreated when the user logs on next. Launch Outlook, and you will need to enter your password again