After running HCW, do we need to add other servers to O365 send connector / scoping / source servers

%3CLINGO-SUB%20id%3D%22lingo-sub-356971%22%20slang%3D%22en-US%22%3EAfter%20running%20HCW%2C%20do%20we%20need%20to%20add%20other%20servers%20to%20O365%20send%20connector%20%2F%20scoping%20%2F%20source%20servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356971%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20two%20Exchange%202010%20servers%20(SP3%20RU26)%20but%20decided%20to%20add%20a%20Exchange%202016%20(now%20CU12)%20server%20as%20our%20%22hybrid%20server%22%2C%20in%20other%20words%2C%20the%20server%20that%20will%20be%20retained%20as%20the%20still%20necessary%20on-premises%20server%20(Exchange%202010%20will%20soon%20be%20EOL).%20I%20ran%20the%20HCW%20(hybrid%20configuration%20wizard)%20on%20the%20Exchange%202016%20server%20and%20noticed%20that%20the%20Exchange%202010%20servers%20were%20not%20selected%20or%20apparently%20selectable%20as%20source%20servers%20for%20the%20new%20%22%20Outbound%20to%20Office%20365%22%20send%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20migrated%20some%20test%20mailboxes%20to%20Exchange%20Online%20and%20those%20mailboxes%20can%20send%20test%20messages%20to%20recipients%20whose%20mailbox%20is%20located%20on%20the%20Exchange%202010%20servers.%20However%2C%20we%20cannot%20send%20test%20messages%20to%20the%20mailboxes%20migrated%20to%20Exchange%20Online.%20I%20created%20a%20test%20mailbox%20on%20the%20Exchange%202016%20on-premises%20%22hybrid%20server%22%20and%20I%20can%20send%20to%20Exchange%20Online%20mailboxes%20from%20THAT%20server.%20But%20still%20not%20from%20mailboxes%20on%20the%20Exchange%202010%20servers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShould%20the%20Exchange%202010%20servers%20be%20added%20to%20the%20%22%20Outbound%20to%20Office%20365%22%20send%20connector%20as%20%22%20source%20servers%22%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20many%20things%20could%20be%20causing%20this%20problem%20(firewall%20rules%20and%20the%20fact%20that%20the%201%20to%201%20NAT%20only%20includes%2C%20by%20definition%2C%20the%20Exchange%202016%20server)%20but%20I%20want%20to%20rule%20out%20the%20absence%20of%20the%20Exchange%202010%20servers%20as%20source%20servers%20in%20the%20%22Outbound%20to%20Office%20365%22%20send%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-356971%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

We have two Exchange 2010 servers (SP3 RU26) but decided to add a Exchange 2016 (now CU12) server as our "hybrid server", in other words, the server that will be retained as the still necessary on-premises server (Exchange 2010 will soon be EOL). I ran the HCW (hybrid configuration wizard) on the Exchange 2016 server and noticed that the Exchange 2010 servers were not selected or apparently selectable as source servers for the new " Outbound to Office 365" send connector.

 

We migrated some test mailboxes to Exchange Online and those mailboxes can send test messages to recipients whose mailbox is located on the Exchange 2010 servers. However, we cannot send test messages to the mailboxes migrated to Exchange Online. I created a test mailbox on the Exchange 2016 on-premises "hybrid server" and I can send to Exchange Online mailboxes from THAT server. But still not from mailboxes on the Exchange 2010 servers.

 

Should the Exchange 2010 servers be added to the " Outbound to Office 365" send connector as " source servers" ?

 

I understand many things could be causing this problem (firewall rules and the fact that the 1 to 1 NAT only includes, by definition, the Exchange 2016 server) but I want to rule out the absence of the Exchange 2010 servers as source servers in the "Outbound to Office 365" send connector.

 

Thank you in advance!

0 Replies