You are evaluating the implementation of a second Edge Transport server named EDGE2 in the Amsterdam office.
You need to recommend which tasks must be performed to ensure that email messages can be sent by the organization if a single Edge Transport server fails.
Which three actions should you include in the recommendation?
To answer, move the three appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Correct Answer:
Explanation/Reference:
Configure Edge Transport Server Using Cloned Configuration
You can use the provided Shell scripts to duplicate the configuration of a computer that has the Microsoft Exchange Server 2010 Edge Transport server role installed.
This process is referred to as cloned configuration. Cloned configuration is the practice of deploying new Edge Transport servers based on the configuration information from a previously configured source server.
The configuration information from the previously configured source server is copied and exported to an XML file, which is then imported to the target server.
Edge Transport server configuration information is stored in Active Directory Lightweight Directory Services (AD LDS) and isn’t replicated among multiple Edge
Transport servers. By using cloned configuration, you can make sure that every Edge Transport server that’s deployed in the perimeter network is operating by using the same configuration.
These scripts are located in the scripts folder in your Exchange installation folder. The default location for this folder is C:Program FilesMicrosoftExchange ServerScripts. exportedgeconfig.ps1
This script exports all user-configured settings and data from an Edge Transport server and stores that data in an XML file. importedgeconfig.ps1
During the validate configuration step, the ImportEdgeConfig.ps1 script checks the XML file to see whether the server-specific export settings are valid for the target server.
If settings have to be modified, the script writes the invalid settings to an answer file that you modify to specify the target server information that’s used during the import configuration step.
During the import configuration step, the script imports all user-configured settings and data that’s stored in the intermediate XML file that was created by the ExportEdgeConfig.ps1 script.
Send Connectors In Microsoft Exchange Server 2013, a Send connector controls the flow of outbound messages to the receiving server.
They are configured on Mailbox servers running the Transport service.
Most commonly, you configure a Send connector to send outbound email messages to a smart host or directly to their recipient, using DNS.
Exchange 2013 Mailbox servers running the Transport service require Send connectors to deliver messages to the next hop on the way to their destination.
Send connectors that are created on Mailbox servers are stored in Active Directory and are available to all Mailbox servers running the Transport service in the organization.
Edge Subscription
The Edge Subscriptions management role enables administrators to manage edge synchronization and subscription configuration between Microsoft Exchange Server 2010 Edge
Transport servers and Microsoft Exchange Server 2013 Mailbox servers in an organization.
Edge Transport servers deployed with Microsoft Exchange are deployed in an organization’s on-premises perimeter network The Edge Subscription file is used in the EdgeSync process, and it contains information about the credentials that are used during the LDAP communication process. These credentials are used to authenticate and authorize the connection between Active Directory Lightweight Directory Service (AD LDS) and Active Directory during replication.
Although creating an Edge Subscription is optional, subscribing an Edge Transport server to the Exchange organization provides a simpler management experience for the administrator and enhances the available antispam features. You must create an Edge Subscription if you plan to use recipient lookup or safelist aggregation, or if you plan to help secure SMTP communications with partner domains by using mutual Transport Layer Security (TLS).
Edge2 is the new edge transport server therefore have to create a new edge subscription for Edge2.
Cloned configuration doesn’t duplicate the Edge Subscription settings of a server. The certificates used by the Microsoft Exchange EdgeSync service aren’t cloned.
You must run the EdgeSync process separately for each Edge Transport server. The Microsoft Exchange EdgeSync service overwrites any settings included in both cloned configuration information and in EdgeSync replication information.
After an Edge Transport server has been subscribed to the Exchange organization, the Microsoft Exchange EdgeSync service replicates data from the Active
Directory directory service to the Active Directory Application Mode (ADAM) directory service instance on the Edge Transport server. The replicated data lets you implement a wider range of anti-spam features and enables domain security functionality. The EdgeSync synchronization process also lets you configure Send connectors and configuration objects that are common to both the Exchange organization and the Edge Transport server on a Hub Transport server and then have that data automatically populated to ADAM. The EdgeSync synchronization process keeps this data up to date by performing scheduled synchronization.
However should it be created 1st or last in the answer selection.
The Microsoft Exchange EdgeSync service overwrites any settings included in both cloned configuration information and in EdgeSync replication information
Therefore it should be last on the answer list.
http://technet.microsoft.com/en-us/library/aa996008(v=exchg.150).aspx#_blank
Explanation/Reference:
Configure Edge Transport Server Using Cloned Configuration
You can use the provided Shell scripts to duplicate the configuration of a computer that has the Microsoft Exchange Server 2010 Edge Transport server role installed.
This process is referred to as cloned configuration. Cloned configuration is the practice of deploying new Edge Transport servers based on the configuration information from a previously configured source server.
The configuration information from the previously configured source server is copied and exported to an XML file, which is then imported to the target server.
Edge Transport server configuration information is stored in Active Directory Lightweight Directory Services (AD LDS) and isn’t replicated among multiple Edge
Transport servers. By using cloned configuration, you can make sure that every Edge Transport server that’s deployed in the perimeter network is operating by using the same configuration.
These scripts are located in the scripts folder in your Exchange installation folder. The default location for this folder is C:Program FilesMicrosoftExchange ServerScripts. exportedgeconfig.ps1
This script exports all user-configured settings and data from an Edge Transport server and stores that data in an XML file. importedgeconfig.ps1
During the validate configuration step, the ImportEdgeConfig.ps1 script checks the XML file to see whether the server-specific export settings are valid for the target server.
If settings have to be modified, the script writes the invalid settings to an answer file that you modify to specify the target server information that’s used during the import configuration step.
During the import configuration step, the script imports all user-configured settings and data that’s stored in the intermediate XML file that was created by the ExportEdgeConfig.ps1 script.
Send Connectors In Microsoft Exchange Server 2013, a Send connector controls the flow of outbound messages to the receiving server.
They are configured on Mailbox servers running the Transport service.
Most commonly, you configure a Send connector to send outbound email messages to a smart host or directly to their recipient, using DNS.
Exchange 2013 Mailbox servers running the Transport service require Send connectors to deliver messages to the next hop on the way to their destination.
Send connectors that are created on Mailbox servers are stored in Active Directory and are available to all Mailbox servers running the Transport service in the organization.
Edge Subscription
The Edge Subscriptions management role enables administrators to manage edge synchronization and subscription configuration between Microsoft Exchange Server 2010 Edge
Transport servers and Microsoft Exchange Server 2013 Mailbox servers in an organization.
Edge Transport servers deployed with Microsoft Exchange are deployed in an organization’s on-premises perimeter network The Edge Subscription file is used in the EdgeSync process, and it contains information about the credentials that are used during the LDAP communication process. These credentials are used to authenticate and authorize the connection between Active Directory Lightweight Directory Service (AD LDS) and Active Directory during replication.
Although creating an Edge Subscription is optional, subscribing an Edge Transport server to the Exchange organization provides a simpler management experience for the administrator and enhances the available antispam features. You must create an Edge Subscription if you plan to use recipient lookup or safelist aggregation, or if you plan to help secure SMTP communications with partner domains by using mutual Transport Layer Security (TLS).
Edge2 is the new edge transport server therefore have to create a new edge subscription for Edge2.
Cloned configuration doesn’t duplicate the Edge Subscription settings of a server. The certificates used by the Microsoft Exchange EdgeSync service aren’t cloned.
You must run the EdgeSync process separately for each Edge Transport server. The Microsoft Exchange EdgeSync service overwrites any settings included in both cloned configuration information and in EdgeSync replication information.
After an Edge Transport server has been subscribed to the Exchange organization, the Microsoft Exchange EdgeSync service replicates data from the Active
Directory directory service to the Active Directory Application Mode (ADAM) directory service instance on the Edge Transport server. The replicated data lets you implement a wider range of anti-spam features and enables domain security functionality. The EdgeSync synchronization process also lets you configure Send connectors and configuration objects that are common to both the Exchange organization and the Edge Transport server on a Hub Transport server and then have that data automatically populated to ADAM. The EdgeSync synchronization process keeps this data up to date by performing scheduled synchronization.
However should it be created 1st or last in the answer selection.
The Microsoft Exchange EdgeSync service overwrites any settings included in both cloned configuration information and in EdgeSync replication information
Therefore it should be last on the answer list.
http://technet.microsoft.com/en-us/library/aa996008(v=exchg.150).aspx#_blank
