![]() ![]() The data, synchronized one way - from the internal AD into the local instance of AD LDS (Active Directory Lightweight Directory Service), is hashed, which makes it of little use to an attacker. Here comes into play the Edge server as a lean, locked-down standalone version of Exchange server. In case of a security breach it might allow an attacker access to mailboxes and Active Directory data. ![]() ![]() However, a standard Exchange server is an attractive target. As we demonstrate in our Screencast Exchange Server 2010 Initial Configuration, you can configure an Exchange 2010 Hub Transport server to receive directly messages from the Internet. You cannot use the Edge server for OWA (Outlook Web Access), Outlook Anywhere, POP3, IMAP accessĪn organization can choose to not have an EDGE server and still have a fully functional messaging environment. The Edge server checks only SMTP traffic - all inbound and outbound e-mails for your organization should be flowing through it It is not installed on an Exchange server in your Exchange 2010 organization – you cannot combine the EDGE role with any other Exchange Server role It is not member of Active Directory – typically is deployed in a workgroup Handles incoming messages from the Internet - the MX record for your email domain(s) should be pointing to Edge Server's public IP It is designed to reside in the DMZ (Perimeter Network) What makes it quite different from the other Exchange 2010 Server roles is that: The Edge Server is one of the Exchange 2010 server roles. The Exchange 2013 Edge Server version of this Screencast is available here. ![]()
0 Comments
Leave a Reply. |