365 Hybrid deployment

[denzal2k4]

So we already had our domains verified, all users syncing with 365 and ADFS configured and working, yesterday we ran the hybrid config wizard on our exchange 2016 server, all went fine once the dns txt records were added. Now a user created on site as a 365 account does pull through to 365 Outlook. All fine so far.

 

The issue is when I migrate a mailbox to Online the only option it gives for target delivery domain is OURDOMAIN.mail.onmicrosoft.com, it doesn't list our normal domain name, the wizard has added the .mail.onmicrosoft.com email address as an alias in AD, so does this mean that it doesn't matter that is showing in 365 as it will get routed through anyway or does it need to be showing our FQDN?? Looking online seems to suggest that you cant have it set to your FQDN if it is running ADFS, which it is. We obviously haven't yet switched our MX record over, as we want to know everything else is correct. Anyone been through this that can maybe shed some light??

[bicky]

Have you tried doing via PowerShell, I have always used PowerShell and migrated about 1700 users.

 

Import-Module MSOnline

$TenantUserName = "[email protected]"
$TenantPassword = "password here or use encrypted key"
$TenantCredentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $TenantUserName, $TenantPassword

$exchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -Credential $Tenantcredentials -Authentication "Basic" -AllowRedirection

$exchangeSession1 = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://ps.compliance.protection.outlook.com/powershell-liveid/" -Credential $Tenantcredentials -Authentication "Basic" -AllowRedirection


Import-PSSession $exchangeSession –AllowClobber

Import-PSSession $exchangeSession1 –AllowClobber

Connect-MsolService -Credential $TenantCredentials

$Company = Get-MsolCompanyInformation | select -exp DisplayName
$InitialDomain = Get-MsolCompanyInformation | select -exp InitialDomain
$host.ui.RawUI.WindowTitle = "You are connected to: " + $Company + " (" + $InitialDomain + ") "

#########################################################################
#########################################################################

## Forest administrator credential for New-MoveRequest

$ONPREMUserName = "mydomain\administrator"
$ONPREMPassword = "password here or use encrypted key"
$ONPREMCREDS = new-object -typename System.Management.Automation.PSCredential -argumentlist $ONPREMUserName, $ONPREMPassword



New-MoveRequest -Identity mydomain\username2 -Remote -RemoteHostName myOnPremExchnageBox.mydomain.com -TargetDeliveryDomain mydomain.com -RemoteCredential $ONPREMCREDS -BadItemLimit 1000

[chaplic]

You are confusing some things

 

The ourdomain.mail.onmicrosoft.com is used ‘under the skin’ to aide mail routing and auto discover resolution as is the ourdomain.onmicrosoft.com

 

If you have the domains verified and have a mailbox setup as you want it, move mailbox, all will be well

 

- - - Updated - - -

 

You are confusing some things

 

The ourdomain.mail.onmicrosoft.com is used ‘under the skin’ to aide mail routing and auto discover resolution as is the ourdomain.onmicrosoft.com

 

If you have the domains verified and have a mailbox setup as you want it, move mailbox, all will be well