Edge Transport role in Exchange Server 2010 is the mail routing server that typically sits at the perimeter of the topology and routes mail in to and out of the Exchange organization
What are the changes are improvements in Edge Transport Server when compared with Exchange 2007?
What are the prerequisites to install an Edge Transport Server?
- Edge has to be installed Perimeter Network without joining the server to Domain Server
- ADLDS role to be intalled
- Other prerequisites like framework 3.5 sp1 and Windows Powershell 2.0 to be installed
How high availability can be achieved for Edge Transport Server?
To Achieve High Availability for Edge Transport Server, we can install more than one Edge Transport server in the perimeter network. Deploying more than one Edge Transport server provides redundancy and failover capabilities for inbound message flow. We can load-balance SMTP traffic to Exchange organization between Edge Transport servers by defining more than one mail exchange (MX) resource record with the same priority in the Domain Name System (DNS) database for your mail domain. We can achieve consistency in configuration between multiple Edge Transport servers by using cloned configuration scripts.
What’s new when compared with Hub Transport server?
When comparing with Hub Transport Server, Edge Server is different with the below details
- Edge Server is deployed at the perimeter to provided more security to Exchange Organization
- Anti-Spam and Anti-Virus components are installed by default, were we have to configure manually in Hub Transport Server
- Address rewriting option is only available in Edge Transport Server
- Edge Transport rules can be created to control the mail flow that are sent to or received from internet
When you will go for address rewriting and how it works?
Address rewriting option in Edge Transport Server roles is to present a consistent appearance to external recipients of messages from your Exchange 2010 organization. We have to configure the Address Rewriting agent on the Edge Transport server role to enable the modification of the SMTP addresses on inbound and outbound messages.
Address rewriting is especially useful when a newly merged organization that has several domains wants to present a consistent appearance of e-mail addresses to external recipients.
What is a backup pressure? What will happen when back pressure occurs? What is the event id?
Back pressure is a system resource monitoring feature of the Microsoft Exchange Transport service that exists on Microsoft Exchange Server 2010 Hub Transport and Edge Transport servers. Exchange Transport check for system resource like available hard disk space and memory, are under pressure, and take action in an attempt to prevent service unavailability.
When backpressure is applied on a Transport Server, it will act based on these 3 resource utilization
Normal - The resource isn't overused. The server accepts new connections and messages
Medium - The resource is slightly overused. Back pressure is applied to the server in a limited manner. Mail from senders in the authoritative domain can flow.
High - The resource is severely overused. Full back pressure is applied. All message flow stops, and the server rejects all new incoming MAIL FROM commands
15005, 15006, 15007 are the event ids related to back pressure
What is an Edge Subscription? When it will occur?
How recipient lookup happening with Edge Server and the Active Directory?
Edge Transport server role is a Standalone Server and doesn't have access to Active Directory. All configuration and recipient information is stored in Active Directory Lightweight Directory Services (AD LDS). To perform recipient lookup tasks, the Edge Transport server requires data that resides in Active Directory. This data is synchronized to the Edge Transport server using EdgeSync.
What is EdgeSync?
EdgeSync is a collection of processes that are run on a computer that has the Hub Transport server role installed to establish one-way replication of recipient and configuration information from Active Directory to the AD LDS instance on an Edge Transport server.
What information is shared while Edge Sync occurs?
EdgeSync service copies only the information that's required for the Edge Transport server to perform anti-spam configuration tasks and the information about the connector configuration that's required to enable end-to-end mail flow. The Microsoft Exchange EdgeSync service performs scheduled updates so that the information in AD LDS remains current.
Explain Pickup and Replay directories in Edge Transport server?
What is a send connector and receive connector in Edge Transport Server?
Explain the Transport Logs and Transport Database in Exchange server 2010?
Exchange 2010 Hub or Edge Transport server has a database for transport feature, below two databases are available in Edge Transport Server
Message queue database - A queue is a temporary holding location for messages waiting to enter the next stage of processing. Each queue represents a logical set of messages that a transport server processes in a specific order
IP filter database - The IP filter database stores the IP Allow lists and IP Block lists that are part of connection filtering
Transport log function will function same as the transaction log file mechanism in Mailbox Database
What is a shadow redundancy?
Shadow redundancy is a new feature in Exchange 2010 to provide redundancy for messages for the entire time they're in transit and this technique is similar to the transport dumpster. With shadow redundancy, the deletion of a message from the transport databases is delayed until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop
What are the ports to be opened at the firewall to HUB and Edge to communicate while edge synchronization?
What are the post installation tasks after completing Edge Transport Server installation?
What is pipeline tracing? When you will go for pipe line tracing?
What is an accepted domain and remote domain?
What are the queues available in Edge Transport server?
What you will do, if no one able to send emails to external domain? While there is no problem in sending and receiving email?
User mentioned that they are not able to send email to particular domain? How you will troubleshoot it?
You are assigned with the task to configure mail flow between Edge and Hub Transport Server? What are steps you will follow?
You are asked to customize a DSN Message, how you will perform the customization?
Can you explain the connectors that are available in Exchange server 2010?
What is a foreign connector in Exchange server 2010?
How you will install Anti Spam Agents in Edge Transport Server? What are the Anti Spam agents available?
How to configure an edge transport server using a cloned configuration?
Explain how the mail flow occurs externally, if Edge Transport Server present in the Exchange organization?
It appears like the Transport Database is corrupted and you have to perform the correction, what you will do?
You install and edge transport server and create an send connector to send emails externally, there is no problem in sending emails externally, but you are not receiving external emails, what needs to be done?
Is that edge transport server really needed? What can be done if you don’t have an edge transport server
No comments:
Post a Comment