nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatically created Send Connectors

rjbarlow

Hello all,

I limit myself to one question, hoping to grab the consequences by myself, otherwise I know where to ask.
After an Edge subscription, I am sitting in front of the console of the Hub Server. It is the "EdgeSync - Default First Site to Internet" and even the "EdgeSync - Inbound to Default First Site" connector, exactly the same I see even on the Edge Serverr, replicated by the EdgeSync service to ADAM?

Thank You

Find more posts tagged with

SAVE $250 on Your Microsoft Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Microsoft Boot Camps

Comments

undomiel

If you look closely at the connectors you will see that they are assigned only to your Edge Transport. All management of these send connectors is done from your Hub Transport since you are using an edge subscription.

rjbarlow

undomiel wrote: »

If you look closely at the connectors you will see that they are assigned only to your Edge Transport. All management of these send connectors is done from your Hub Transport since you are using an edge subscription.

Wow, that's Exchange time for You Jeffrey?

Thanks for the hint man.

undomiel

I just did a migration the other week so I got to experience it all first hand.

rjbarlow

undomiel wrote: »

I just did a migration the other week so I got to experience it all first hand.

*Great*.