Remove flag for awaiting migration

%3CLINGO-SUB%20id%3D%22lingo-sub-1550310%22%20slang%3D%22en-US%22%3ERemove%20flag%20for%20awaiting%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1550310%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%23m%20just%20supporting%20a%20customer%20who%20is%20trying%20to%20setup%20his%20full%20environment%20after%20a%20cyber%20attack.%20There%20was%20a%20hybrid%20deployment%20with%20some%20few%20migrated%20Exchange%20mailboxes%2C%20but%20all%20AD%20accounts%20synced%20to%20cloud.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20we%20already%20removed%20the%20AD%20Sync%20and%20the%20AAD%20accounts%20turned%20into%20cloud%20only%20accounts.%20But%20in%20Exchange%20for%20the%20majority%20all%20the%20users%20are%20still%20mail%20users%20although%20they%20have%20an%20assigned%20Exchange%20Online%20Plan%202.%20We%20already%20tried%20to%20remove%20the%20license%20and%20re-assign%20it%20again%2C%20but%20the%20object%20still%20remains%20as%20mail%20user.%3CBR%20%2F%3E%3CBR%20%2F%3EThere%20is%20a%20way%20how%20we%20can%20turn%20the%20user%20the%20mail%20user%20to%20mailbox%20user%2C%20but%20therefore%20we%20have%20to%20remove%20the%20mail%20user%20and%20restore%20the%20MSOLuser%20from%20the%20recycle%20bin.%20This%20is%20not%20the%20best%20approach%2C%20because%20we%20have%20to%20set%20a%20new%20password.%20What%20sounds%20pretty%20easy%20is%20a%20real%20pain%2C%20because%20we%20have%20to%20provide%20several%20thousand%20passwords%20to%20distributed%20users.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20would%20like%20to%20keep%20the%20passwords%20in%20the%20first%20steps%20and%20enforce%20the%20password%20change%20at%20logon.%3CBR%20%2F%3EI%20guess%20there%20must%20be%20a%20flag%20or%20an%20attribute%20which%20still%20keeps%20the%20information%20that%20the%20object%20is%20waiting%20for%20a%20mailbox%20migration%20from%20on-premises.%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20a%20possibility%20to%20clear%20this%20attribute%20so%20that%20we%20could%20enable%20the%20mailbox%20right%20away%20without%20setting%20a%20new%20password%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20in%20advance.%3CBR%20%2F%3E%3CBR%20%2F%3EKind%20regards%2C%3C%2FP%3E%3CP%3Ewoelki%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1550310%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1551004%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20flag%20for%20awaiting%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1551004%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F281233%22%20target%3D%22_blank%22%3E%40woelki%3C%2FA%3E%2C%3C%2FP%3E%3CP%3ECheck%20if%20you%20can%20run%20the%20following%20command%20%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESet-User%20Jon%40contoso.com%20-%3C%2FSPAN%3E%3CSPAN%3EPermanentlyClearPreviousMailboxInfo%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERef%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fpermanently-clear-previous-mailbox-info%2Fba-p%2F607619%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fpermanently-clear-previous-mailbox-info%2Fba-p%2F607619%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnother%20thing%20you%20can%20check%20is%20if%20the%20object%20still%20has%20immutable%20ID%20stamped%20(Get-Msoluser)%20you%20might%20have%20to%20clear%20that%20as%20well.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1551008%22%20slang%3D%22en-US%22%3ERe%3A%20Remove%20flag%20for%20awaiting%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1551008%22%20slang%3D%22en-US%22%3Ei%20know%20of%20below%2C%20that%20helps%20to%20clear%20previous%20mailbox%20info%20where%20mailbox%20has%20been%20provisioned%20earlier%20and%20this%20turn%20user%20back%20to%20a%20mail%20user%2C%20not%20sure%20if%20this%20can%20help%2C%20worth%20giving%20a%20try%2C%20test%20it%20with%20a%20test%20account%20and%20apply%20to%20everyone%20if%20this%20works%20%3A-%3CBR%20%2F%3ESet-User%20user%40domain.com%20-PermanentlyClearPreviousMailboxInfo%3CBR%20%2F%3Eyou%20can%20check%20the%20value%20of%20the%20property%20using%20below%20%3A-%3CBR%20%2F%3EGet-User%20user%40domain.com%20%7C%20Select%20name%2C*Recipient*%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi there,

 

I#m just supporting a customer who is trying to setup his full environment after a cyber attack. There was a hybrid deployment with some few migrated Exchange mailboxes, but all AD accounts synced to cloud.

So we already removed the AD Sync and the AAD accounts turned into cloud only accounts. But in Exchange for the majority all the users are still mail users although they have an assigned Exchange Online Plan 2. We already tried to remove the license and re-assign it again, but the object still remains as mail user.

There is a way how we can turn the user the mail user to mailbox user, but therefore we have to remove the mail user and restore the MSOLuser from the recycle bin. This is not the best approach, because we have to set a new password. What sounds pretty easy is a real pain, because we have to provide several thousand passwords to distributed users.

We would like to keep the passwords in the first steps and enforce the password change at logon.
I guess there must be a flag or an attribute which still keeps the information that the object is waiting for a mailbox migration from on-premises.

Is there a possibility to clear this attribute so that we could enable the mailbox right away without setting a new password?

Thanks in advance.

Kind regards,

woelki

 

 

2 Replies
Highlighted

Hey @woelki,

Check if you can run the following command : 

Set-User Jon@contoso.com -PermanentlyClearPreviousMailboxInfo

 

Ref: https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba...

 

Another thing you can check is if the object still has immutable ID stamped (Get-Msoluser) you might have to clear that as well.

 

 

Highlighted
i know of below, that helps to clear previous mailbox info where mailbox has been provisioned earlier and this turn user back to a mail user, not sure if this can help, worth giving a try, test it with a test account and apply to everyone if this works :-
Set-User user@domain.com -PermanentlyClearPreviousMailboxInfo
you can check the value of the property using below :-
Get-User user@domain.com | Select name,*Recipient*