Server 2012 R2 Essentials and Exchange

I have a client (22 users) who is using SBS 2008. It is time to upgrade and I am planning on using Server 2012 R2 Essentials and Exchange 2013 SP1 on separate servers. I know we can add the Exchange server to the Essentials through the Essentials interface, but I have a question about OWA. The client has one static IP address. I want to point port 25 to the IP of the new Exchange server so incoming email is delivered there.  However, do I need a new static IP and a dedicated trusted certificate to do OWA or, by attaching the Exchange server through Essentials, will the Essentials Server automatically access OWA on the Exchange Server?

I'm sure someone is going to say "Use Outlook 365."  The cost is more expensive than an Exchange server for this client.  So, we need to configure it this way.

Any assistance is GREATLY apprec

June 8th, 2015 1:45pm

I wouldn't combine other applications with Exchange.  Consider using Hyper-V and running the products in separate VMs.
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2015 7:55pm

I am not combining the servers.  Essentials is one server and Exchange is on a separate Server 2012 machine.  It is the OWA that I have the question about.  In Essentials I can "attach" Exchange.  But can I do OWA by remoting into the Access Anywhere configuration or does OWA have to have it's own public IP and Certificate?
June 9th, 2015 12:02am

I don't know what you mean by, "remoting into the Access Anywhere configuration".

Exchange services can't have separate certificates unless you've created separate web sites for them, they all share the same certificate.  The usual minimum configuration is one name for OWA, ECP, OAB, Outlook Anywhere, ActiveSync and EWS; and another name for Autodiscover.  That would normally be a UCC certificate with two names, e.g., webmail.company.com and autodiscover.company.com.  But there are alternatives like a wildcard certificate, or using an SRV record for Autodiscover.

With straight Exchange, you could put the Exchange 2013 server in front of the downlevel Exchange server and it would proxy or redirect the sessions and traffic to it.  However, I don't know enough about the limitations of Server Essentials to answer your question, so I recommend that you post this in what I believe is a more appropriate Forum:  https://social.technet.microsoft.com/Forums/en-US/home?forum=smallbusinessserver2011essentials&filter=alltypes&sort=lastpostdesc

Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 8:29pm

Hi.

Exchange 2013 SP1 not support Windows 2012 Essentials.

Windows Server 2012 R2 Products and Editions Comparison

Exchange 2013 system requirements

June 9th, 2015 8:40pm

Hi,

Based on my knowledge,Microsoft does not support installing Exchange Server on a server that is running Windows Server Essentials. https://technet.microsoft.com/en-us/library/jj200172.aspx?f=255&MSPPError=-2147217396

We can install Exchange 2013 SP1 or later version on Windows Server 2012 R2 Standard or Datacenter version. For more information about supported operating systems for Exchange 2013, please refer to:https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Best Regards,

David 

Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 9:03pm

In each of the replies, you tell me that I cannot put exchange on essentials server.  I know that.  That is why I am putting it on a separate Sever 2012 R2 server.  The question I have is this -- going back in time to when Microsoft offered Small business server, we could get one certificate and point port 25 to the SBS server. Now, we have TWO servers.  We can add Exchange server to the Essential server (there are tons of instructions and videos out there explaining how), but the question I have is, "If I attach the Exchange server (which is a different server) to the Essentials server, can I set up the router and certificate to point to the Essentials server and have it forward the email and OWA to the new separate Exchange server, OR do I need to point OWA and port 25 to the NEW Separate Exchange server and have a separate certificate for the OWA on the new separate Exchange server?"
June 17th, 2015 9:39am

The problem is that in this forum few people do anything with Essentials and therefore aren't familiar with restrictions Essentials may place on connecting with other servers, which is why you might get a better response in an Essentials forum.
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 2:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics