As for MX records, these can be pointing to Office 365 or your On Premise Exchange environment, depending on your needs. As long as the Hybrid Configuration Wizard worked correctly, mail flow should be seamless between the two systems.
[PS] C:\Windows\system32>get-hybridconfiguration | fl
RunspaceId : de34fead-a695-444b-44e7-44cc4444becb
ClientAccessServers : {}
TransportServers : {VSVR-EXCH2010}
SecureMailCertificateThumbprint : 4491AE94D3444C229CBCE4439CDF1444CCB44C244
OnPremisesSmartHost : mail.<domain-0>.com
Domains : {domain-a.com, domain-b.com, domain-b.com, autod:domain-0.com}
Features : {FreeBusy, MoveMailbox, Mailtips, MessageTracking, OwaRedirection, OnlineArchive, SecureMail}
ExternalIPAddresses : {<pub IP Address>}
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : Hybrid Configuration
DistinguishedName : CN=Hybrid Configuration,CN=Hybrid Configuration,CN=myenm,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain-0,DC=com
Identity : Hybrid Configuration
Guid : 3d96cf44-6f44-4744-a044-dd83e946c344
ObjectCategory : domain-0.com/Configuration/Schema/ms-Exch-Coexistence-Relationship
ObjectClass : {top, msExchCoexistenceRelationship}
WhenChanged : 1/5/2018 5:17:03 PM
WhenCreated : 12/7/2017 12:12:37 PM
WhenChangedUTC : 1/6/2018 1:17:03 AM
WhenCreatedUTC : 12/7/2017 8:12:37 PM
OrganizationId :
OriginatingServer : ADDC.domain-o.COM
IsValid : True
ASKER
he send connector on-premises should indeed only feature the tenant.mail.onmicrosoft.com domain
ASKER
ASKER
ASKER
ASKER
ASKER
ASKER
ASKER
[PS] C:\Windows\system32>$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
WARNING: Your connection has been redirected to the following URI: "https://ps.outlook.com/PowerShell-LiveID?PSVersion=2.0 "
[... lots of stuff...]
ModuleType Name ExportedCommands
---------- ---- ----------------
Script tmp_e4c285dd-498c-4f94... {Get-DeviceComplianceDetailsReportFilter, Get-PublicFolderMigrationReque...
[PS] C:\Windows\system32>New-MoveRequest -identity <user> -Remote -RemoteHostName 'on-premise.server.com' -TargetDeliveryDomain 'tenant.mail.onmicrosoft.com' -Remotecredential $OnPremisesCreds -Bad
VERBOSE: [23:30:25.651 GMT] New-MoveRequest : Active Directory session settings for 'New-MoveRequest' are: View Entire Forest: 'False', Default Scope: '<AD-Domain>', Configuration Domain Controller:
'ADDC.<AD-Domainn>', Preferred Global Catalog: 'addc2.<AD-Domainn>', Preferred Domain Controllers: '{ addc2.<AD-Domainn> }'
VERBOSE: [23:30:25.653 GMT] New-MoveRequest : Runspace context: Executing user: <AD-Domainn>/myOU/Scott, Executing user organization: , Current organization: ,
RBAC-enabled: Enabled.
VERBOSE: [23:30:25.655 GMT] New-MoveRequest : Beginning processing &
VERBOSE: [23:30:25.657 GMT] New-MoveRequest : Instantiating handler with index 0 for cmdlet extension agent "Admin Audit Log Agent".
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that
Exchange not copy such items to the destination mailbox. At move completion, these corrupted items won't be available in the destination mailbox.
VERBOSE: [23:30:25.711 GMT] New-MoveRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclu
Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [23:30:25.738 GMT] New-MoveRequest : Searching objects "<user>" of type "ADUser" under the root "$null".
VERBOSE: [23:30:25.786 GMT] New-MoveRequest : Previous operation run on domain controller 'addc2.<AD-Domainn>'.
VERBOSE: [23:30:25.790 GMT] New-MoveRequest : Processing object "$null".
VERBOSE: [23:30:25.805 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
Target user '<user name>' already has a primary mailbox.
+ CategoryInfo : InvalidArgument: (<user>:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskException
+ FullyQualifiedErrorId : 35586141,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
VERBOSE: [23:30:25.835 GMT] New-MoveRequest : Ending processing &
ASKER
Cannot convert the "Microsoft.Exchange.MailboxReplicati onService. TargetDeli veryDomain MismatchPe rmanentExc eption" value of type "System.String" to type "System.Type".
ASKER
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
TRUSTED BY
ASKER
I have made the domains I'm working with along with the onmicrosoft.com domains 'Internal Relay' under accepted Domains.
The mail that is trying to be sent to domain-0.com is being sent to the Public IP address for the on-premise mail server. The on-premise mail server's default send connector does have the 'Use the External DNS lookup on the transport server' set and it is set to google's DNS.
I'm not sure why the email sent to domain-a.com is in the Queue for domain-0.com and not tenant.mail.onmicrosoft.co
Look like my External DNS for domain-0.com was set to the on-premise server. I changed the MX record to <domain-0.com>.mail.protec
I have yet to Migrate a user for a Domain that would have both on-premise and O365 users.