Trying to Migrate a Mailbox to O365

Question

Hello.  I don't know much about scripting or PowerShell but I'm having troubles getting something to work and I'm hoping that someone might help me out.  I am running O365 in a hybrid config with my on premise Exchange 2010 server.  Because I'd
like to keep my on premise Exchange server and my local domain controllers, I was told elsewhere that, to create new accounts, I have to create them locally, migrate them up to Office 365 and then assign an O365 license to them.  That is how I have been
creating all of my new users and shared mailboxes in the 6 months or so that we have been using O365.  I have begun dabbling with PowerShell and I'd like to find a way to automate the mailbox creation a bit.  I have figured out how to create a new
local mailbox and set all necessary properties on it but I would also like to be able to migrate it up to O365 via PowerShell and that's the part that I'm having trouble with.  Here's what I have so far:
New-Mailbox -Name JustaTest -Alias JustaTest -OrganizationalUnit "mydomain.com/My OU" -Database "Mailboxes" -UserPrincipalName [email protected] -Shared
Add-MailboxPermission JustaTest -User "MyDomain\Me" -AccessRights FullAccess
Add-ADPermission JustaTest -User "MyDomain\Me" -ExtendedRights Send-As
Set-Mailbox "JustaTest" -EmailAddresses SMTP:[email protected],[email protected]
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session
New-MoveRequest -Identity “JustaTest” -Remote -RemoteHostName “localmailserver.mydomain.com” -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
The first 4 lines work great but the problems begin when I get to the move request.  I'm getting this when it gets to that part:
C:\Windows\system32>New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
Cannot process argument transformation on parameter 'RemoteCredential'. Cannot convert the "System.Management.Automation.Runspaces.PSSession" value of type "Deserialized.System.Management.Automation.Runspaces.PSSession" to type "System.Management.Automation.PSCredential".
    + CategoryInfo          : InvalidData: (:) [New-MoveRequest], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,New-MoveRequest
    + PSComputerName        : localmailserver.mydomain.com
Any assistance that can be provided would be very much appreciated.
Thanks in advance.
-Chris

Answer 1

Hi Chris,
You passing the PSSession object ($Session ) to -RemoteCredential.
Aren't you suppose to Pass the Admin credential object here ($UserCredential )
Incorrect:New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
Corrected:
New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $UserCredentialorGet-Mailbox -Identity "JustaTest" | New-MoveRequest -Remote -RemoteHostName localmailserver.mydomain.com -RemoteCredential $UserCredential -TargetDeliveryDomain "mydomain.mail.onmicrosoft.com"
How about we validate the below points as well. Like is Get-Mailbox working on remote or not.
After Step 4, the
Exchange Online cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don’t receive any errors, you connected successfully.
A quick test is to run an Exchange Online cmdlet—for example, Get-Mailbox—and see the results.
If you receive errors, check the following requirements:
A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization.
Windows PowerShell needs to be configured to run scripts. You only need to configure this setting once on your computer, not every time you connect. To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell
window (a Windows PowerShell window you opened by selecting Run as administrator).
Set-ExecutionPolicy RemoteSigned
The account you use to connect to Exchange Online must be enabled for remote Shell. For more information, see
Manage remote PowerShell access in Exchange Online.
TCP port 80 traffic needs to be open between your local computer and Exchange Online. It's probably open, but it’s something to consider if your organization has a restrictive Internet access policy.
Best way to learn PowerShell is to track the PS cmdlets used while doing it in EAC. Check out this wiki which should be applicable for O365 as well
Exchange Admin Center Cmdlet Logging In Exchange Server 2013 SP1
References:
Hybrid Mailbox moves and EMC changes
Error in Moving Mailboxes to O365
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.