Do you have to wait till the user has completed migration until you can assign them a license? Or with this tool can you assign them the license as a they finish migrating?

BRAVO.  Do you take donations in beer, paypal, or interesting souvenirs?

This is absolutely brilliant.

Michael,

Recommendation for the mailbox move script after using it a while..   If there is not a matching proxy address, it would be awesome if it prompted you to go ahead and add one.  Now granted, that would require the local change to occur as well as a dirsync, so I understand why it might not be plausible...  but it would be awesome if it did.

Thanks again for this tool.

Michael, I think I love you :)

Don't get me wrong Michael, still love you buddy, but can this tool in some way add a 'largeitemlimit' to each mailbox move command as well as the baditemlimit? I don't mind adding it in myself, but I'm a little unsure of the VB structure behind the scenes :)

Aside from that, I'd like to report that I've managed my first batch using your tool successfully (apart from the users with large items of course). It's a very nice piece of kit. This might seem like a security threat, but is there any way we could embed the tenancy and on premises credentials somewhere. Just for temporary use?

Yours very gratefully - Gavin

Sure could use large item limit options, unless I missed it.

Looks awesome though, going to test a batch in a few minutes

I'm digging around in the VB Macro that does the mailbox migrations, trying to remember how to form a command call with references to variables so I can add -LargeItemLimit into it. Can anyone help?

Michael has the variable "BadItemLimit" set at the top of his 'Migrate_Mailboxes' macro:

BadItemLimit = wsPlanned.Range("L18").Value

It gets it's value from the cell on the Planned Batch sheet L18. I've added another variable into the declarations, anjd I've prepared a call for this config on the spreadsheet. I'm using L24:

LargeItemLimit = wsPlanned.Range("L24").Value

I now need to alter the Call Shell Line in the macro to include the -LargeItemLimit switch and input the number from the variable. Sound easy right? ;)

There is a bit of 'If Then' logic to choose the right command, dependent on what O/S you are using, and whether or not you've selected 'suspendmoves' but in short, this is the command. I'm focusing on the one tailored for 'suspendmoves':

Call Shell("C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -noexit -file " & FileName & " -exportpath " & ExportPath & " -SuspendMovesWhenReady 1 -baditemlimit " & BadItemLimit, vbMaximizedFocus)

Help!!

Another tab I would love.. domain add/verify. Usually not a problem, but have recently had 150+ domains project and I made an XLS to build all the cmdlets. Im trying to reverse engineer the XLS marco's/script building you did here, but might be easier for you to add it :)

Michael, you're a gent and a scholar. Right in time for my next department's migration too :)
Thanks heaps :)

This is fantastic!...bless you :-)