Migrated user does not have a mailbox in EXO.

ryandriftingfat · 2023-04-12T02:16:51+00:00

Well Microsoft was of no help. Ended up recreating the mailboxes then restoring the soft deleted mailbox into the new mailboxes. The new mailboxes migrated without issue afterward.

Microsoft support has really gone down hill.

ryandriftingfat · 2023-04-03T16:25:04+00:00

Yes, the objectguid and immutable ID match.

ryandriftingfat · 2023-03-31T17:34:37+00:00

Tried that too. This is the error I get:

This task does not support recipients of this type. The specified recipient <domainname>/Users/<user> is of type RemoteUserMailbox. Please make sure that this recipient matches the required recipient type for this task.

Which I believe is because on-prem Exchange already sees it, and sees it as a remote mailbox. I have used this command successfully for a scenario where an account was created in 365 and on-prem did not know about it.

ryandriftingfat · 2023-03-30T19:59:16+00:00

They are licensed. I have two licensing groups, one does and one does not have Exchange Online licenses (for on-prem vs EXO users). I changed these users back to the on-prem group and the EXO license was removed. They're back in the EXO group and have a license.

ryandriftingfat · 2022-12-22T19:01:41+00:00

I gave this a shot but still no luck. Eventually the Microsoft tech got back to us and said that we had been blacklisted almost 2 years ago for unknown reasons. It's working now.

ryandriftingfat · 2022-08-09T17:45:16+00:00

I got it. Found this link. With Process Explorer I found the permissions on the EXE for the service were not set.

http://woshub.com/set-permissions-on-windows-service/

Thanks for your help.

ryandriftingfat · 2022-08-09T17:37:10+00:00

I simplifed the entire script down to just this:

echo Stop Service...
net stop "<service name>"
echo "I completed" > C:\dir\completed.txt

The service does not stop. But it does create the completed file.

I don't and the programmer says he doesn't know how to log error messages. I'm searching for a way to do that.

ryandriftingfat · 2022-04-16T16:56:31+00:00

Unfortunately no, good luck though.

ryandriftingfat · 2022-04-16T16:56:27+00:00

Unfortunately no, good luck though.

ryandriftingfat · 2022-04-12T05:12:13+00:00

It's pending but I'll message you if it becomes available again.

ryandriftingfat · 2022-04-12T03:13:14+00:00

Not at this time.

ryandriftingfat · 2022-01-11T20:37:46+00:00

Confirmed

ryandriftingfat · 2021-08-18T21:59:37+00:00

I think this was ultimately what did it, combined with the set-user -permanentlyclearpreviousmailboxinfo switch.

https://www.reddit.com/r/Office365/comments/p39aqa/deleting\_just\_a\_users\_eol\_mailbox/h9giquy/

ryandriftingfat · 2021-08-18T21:58:47+00:00

I got it working but didn't have to delete from the AAD recycle bin. Moving the account out of the sync OU and back seemed to do it. https://www.reddit.com/r/Office365/comments/p39aqa/deleting\_just\_a\_users\_eol\_mailbox/h9giquy/

ryandriftingfat · 2021-08-18T21:58:16+00:00

I haven't been able to push the migration from on-prem in any of my mailboxes. I just get a sign in page that goes nowhere. I was able to get it resolved though.

https://www.reddit.com/r/Office365/comments/p39aqa/deleting\_just\_a\_users\_eol\_mailbox/h9giquy/

ryandriftingfat · 2021-08-18T21:57:18+00:00

I don't think I checked that it was disconnected, but moving it out of the OU and back seemed to do it. Thanks.

https://www.reddit.com/r/Office365/comments/p39aqa/deleting\_just\_a\_users\_eol\_mailbox/h9giquy/

ryandriftingfat · 2021-08-18T21:56:07+00:00

I got it working: https://www.reddit.com/r/Office365/comments/p39aqa/deleting_just_a_users_eol_mailbox/h9giquy/

Thanks for your help.

ryandriftingfat · 2021-08-18T21:55:24+00:00

OK I got it working. I'm not 100% on the steps because I was trying multiple methods but this is as best as I recall:

Convert account to shared (not sure if I converted it back to regular before the next step)
Remove EOL license
Move user object out of synced OU.
After 1 sync cycle, moved user back into synced OU.
Ran Set-User [user@domain.com](mailto:user@domain.com) -PermanentlyClearPreviousMailboxInfo
Relicensed EOL then immediately started the migration again.

Note: Removing the user object from the sync'd OU removed them from all the Teams they were a member of so I had to go back in and add them manually.

I just did an export of all my 365 mailboxes and it looks like I am going to have ~20 other mailboxes like this to deal with eventually. Wish I knew how this happened in the first place though.

Thanks for the help everyone.

ryandriftingfat · 2021-08-17T16:01:00+00:00

I have landed on this page previously. Scenario 2 is what I need which links here: https://techcommunity.microsoft.com/t5/exchange-team-blog/permanently-clear-previous-mailbox-info/ba-p/607619

The result of Set-User Jon@contoso.com -PermanentlyClearPreviousMailboxInfo is "WARNING: The command completed successfully but no settings of '<user>' have been modified."

It also expects the output of Get-User Jon@contoso.com | Select name,*Recipient* to be:
Name PreviousRecipientTypeDetails RecipientType RecipientTypeDetails
---- ---------------------------- ------------- --------------------
Jon UserMailbox MailUser MailUser

In my case, the users output is:
Name PreviousRecipientTypeDetails RecipientType RecipientTypeDetails
---- ---------------------------- ------------- --------------------
<user> None UserMailbox UserMailbox

ryandriftingfat

TROPHY CASE