Automatically created Send Connectors
rjbarlow
Member Posts: 411
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
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
Comments
-
undomiel
Member Posts: 2,818
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.Jumping on the IT blogging band wagon -- http://www.jefferyland.com/ -
rjbarlow
Member Posts: 411
Wow, that's Exchange time for You Jeffrey?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.
Thanks for the hint man.
-
undomiel
Member Posts: 2,818
I just did a migration the other week so I got to experience it all first hand. Jumping on the IT blogging band wagon -- http://www.jefferyland.com/
-
rjbarlow
Member Posts: 411
*Great*.I just did a migration the other week so I got to experience it all first hand.