Exchange 2013 External User Access Scenarios
Hi Team,
I'v got 2 Exchange 2013 CAS/Mailbox (same server virtualized) sitting on my head office. I need to look into providing external user access. Since there's no Edge in 2013, I would like to know what are the best practices and Microsofts recommended approach
for this.
1. How to address Edge replacement
2. Do I need to have TMG or any proxy server for OWA publishing or can i directly do that from the CAS? If so is it recommended.
3. Also, some of my user mailboxes will be hosted in Zimbra so Exchange 2013 will be internet facing and Zimbra will be side by side for the same (domain.com). Zimbra and Exchange will be using a single DC where all users are placed. So If i need to route
the mails to zimbra users, what is the best approach.
TIA...
April 4th, 2013 12:37am
You can continue to use existing Exchange Server 2007 or Exchange Server 2010 Edge Transport servers that you have deployed in your perimeter network.
Or, you can install a new Exchange 2007 or Exchange 2010 Edge Transport server in your perimeter network for a new or upgraded Exchange 2013 organization.
Please go through the below Microsoft link to know how to use Edge server for Exchange 2013
http://technet.microsoft.com/en-in/library/jj150569(v=exchg.150).aspx
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2013 1:36am
Hi
1. You don't need an Edge server and I wouldn't recommend installing one if you have a SMTP gateway or other spam filtering service already.
2. This depends on your security policy - I would always use a TMG (when they were still available) but now you would need to look at UAG or an appliance from Kemp, F5 or the other providers.
3. You should configure your domain.com as an Internal Relay domain (under Accepted Domains) and create a send connector for domain.com pointing to your Zimbra server. You would also need to create Mail Users or contacts for all of your Zimbra
mailboxes so that they appear in the 2013 GAL. Don't create mailboxes for them on 2013.
This is the 2010 article but the idea is the same in 2013:
Configure Exchange 2010 to Route Messages for a Shared Address Space
Cheers, Steve
April 4th, 2013 4:14am
Thanks Prakash and Steve.
@Steve,
1. This is a fresh implementation and there's no other gateway. Seems like it's better and recommended to have Edge 2010 deployed.
3. Now in this kind of a scenario, My exchange server would be having 2 Send connectors; 1 for Internet with SMTP
Address Space = '*' and 2nd Connector for Zimbra with SMTP
Address Space =
'domain.com'(which
is the same as my Exchange).
Wouldn't there be a conflict in deciding which send connector to use?
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2013 5:47am
No worries
1. The choice is yours but remember an Edge server adds complexity to your environment and it is an extra step to troubleshoot when you have mail flow issues
3. I answered this in your other thread.
Cheers, Steve
April 4th, 2013 5:54am
Hello Mr Steve
Hope Everything is good!
With SMTP gateway or other spam filtering service, Can I use Mdaemon?
are there any good guides for Exchange 2013 and services like Mdaeomon?
I tried to figure out the installation of Edge 2010 and Exchange 2013 and can't figure this out.
Thanks for your help Mr Steve!
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 5:07am