Cannot purge deleted mailbox Office 365



Problem.
User left last year, account was disabled and Office 365 mailbox deleted. She comes back 1 year later, her A.D account is enabled and moved to the correct O.U. But….. a new mailbox cannot be created for in O365: error in creating a mailbox.
Her old mailbox is still in the “deleted mailboxes” in Exchange Admin Center. Cannot delete the old mailbox.
Error: The user mailbox couldn't be permanently deleted. The user mailbox has at least one type of hold or hold policy applied to it. Please remove the holds before trying to delete. LitigationHoldEnabled: true, ComplianceTagHoldApplied: false,

Solution.
·         - Set-Mailbox xxxx@contoso.com -LitigationHoldEnabled $false -InactiveMailbox
·         - Remove-Mailbox -Identity "xxxx@contoso.com" -PermanentlyDelete -Confirm:$True
After that the old mailbox is permanently removed.
Re-create the license and let O365 create a new mailbox.

Comments

Post a Comment

Popular posts from this blog

Server Manager will not start, error .NET Framework: "This application requires one of the following versions of the .NET Framework:"

Server Manager will not start on Windows Server 2019 after installing ADConnect. Error ServerManager.exe: This application could not be started. .NET Framework: "This application requires one of the following versions of the .NET Framework:xxxxx Do you want to install .NET framework now?" Of course it's already installed automatically on the server, so if you try and install it again you can't, error "already installed". Try the .NET repair package, can't repair the install. Try dsim.exe to install the package, error "Microsoft .NET Framework is already part of this installation". .NET Runtime version : 4.0.30319.0 - This application could not be started.This application requires one of the following versions of the .NET Framework:  v4.0.30319 The answer is to re-create the registry entries deleted when you installed ADConnect:- [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "AspNetEnforceViewStateMac"=dw...
Read more

Start virtualised domain controller in DSRM (Active Directory Restore Mode).

If you have a totally virtualised Active Directory infrastructure in Hyper-V, you can't boot the VM into  Directory Services Restore Mode  using F8. The keypress is not recognised. To get around this, in a elevated command prompt, type: bcdedit /set {globalsettings} advancedoptions true Now when you reboot the DC, it will ask if you want to boot into restore mode, and you can restore A.D. After rebooting, type the command: bcdedit /set {globalsettings} advancedoptions false and it will boot normally again. Now you have to find the restore mode password....
Read more