Hello, I am having a few issues configuring my Exchange 2013 Deployment. This is my first time setting up a deployment from scratch and it is very much on a budget. Here are the issues I've run in to.

1) Uncertain how to generate the proper SSL for external access.

We have a windows domain "domain.com" with the mailserver on it "exch01.domain.com", this is also on the secondary DC (jsyk, in case that may cause issues)

We have a webhost (lunarpages) with a domain that is: domain.pw.

mail.domain.pw has an A record that points to the static IP of the modem where exch01.domain.com is located.

There is an MX record for domain.pw with content: mail.abraxas.pw

I want to know how to generate the SSL certificate such that, when a user goes to mail.domain.pw/owa (externally) they are able to access the server without any SSL warnings. I have purchased a signed SSL to install. I think I just need to generate the CSR correctly but the two times I have done this it has resulted in the domain being designated host.domain.com (exch01.domain.com) instead of mail.abraxas.pw?

Any advice would be TREMENDOUSLY appreciated!

2) SPF record is not showing up as valid

I have set up a text record with the following: "v=spf1 a ip4:50.137.25x.xx ~all" (x's are filled in, obviously) and mxtoolbox is reporting this as valid, however, I have the same set up as an spf record and that is failing? Any ideas why? They are set for domain.pw and not on any subdomains.

Thanks so much!

• Edited by TechManLabs 12 hours 39 minutes ago

Generating exchange 2013 CErt REquest

http://support.godaddy.com/help/article/4773/generating-a-certificate-signing-request-csr-exchange-server-2013

Once done then install the Cert

http://support.godaddy.com/help/article/4774/installing-an-ssl-certificate-in-microsoft-exchange-server-2013

Now Assign assign new certificate on SMTP and IIS Services

http://exchangeserverpro.com/exchange-2013-assign-ssl-certificate-to-services/

Now pint your MX Record and Host A records to the Public IP of the Exchange 2013 server

Same you do for the SPF after the MX records are populated.

Test using www.TestExchangeConnectivity.com - once the domain and mx records are fully functional 24-72 hrs time for this.