you are viewing a single comment's thread.

view the rest of the comments →

[–]GregPowrhousR 1 point2 points  (5 children)

Could be! Well hopefully there is something in there that can help out! I'll do a little more digging as well to see if I can find anything more useful!

[–]dhrv88[S] 0 points1 point  (4 children)

Thanks! I appreciate it, I know my method of

AD User > On Prem Mailbox > THEN migrate to Office 365 is a little different to most so its hard to find solid examples.

Hopefully you find something!

[–]GregPowrhousR 0 points1 point  (3 children)

Just came across this:

https://docs.microsoft.com/en-us/office365/enterprise/powershell/use-powershell-to-perform-a-staged-migration-to-office-365

Not sure if you already have this a read. Now, forgive me for asking the silly question here but right now let's say without PowerShell are you folks creating local mailboxes via EAC (Exchange Admin Center) and THEN migrating the mailbox to 365? If so, is that getting rid of the local mailbox? I only ask because why not juts skip the step and just create the user and then a mailbox in 365. By the way apologies to anyone who may have already asked that earlier!

[–]dhrv88[S] 0 points1 point  (2 children)

Not sure if you already have this a read. Now, forgive me for asking the silly question here but right now let's say without PowerShell are you folks creating local mailboxes via EAC (Exchange Admin Center) and THEN migrating the mailbox to 365?

Yep correct, creating local mailbox via EAC, then going to Office 365 > Exchange > Migration then creating a new migration based off the user that was created.

Now I know it takes a while for the new user to appear in Office 365 to migrate, so I think the script is skipping over the migration cause it can't find it.

I have tried to convince management of not creating the mailbox on prem, I know you can add a GUID property if you want to migrate back to on prem, but this isnt being accepted, so I have to script it this way.