• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 63
  • Last Modified:

New Exchange 2010 & MX record required

A new company (companyB) was started under the umbrella of an existing company (companyA).  CompanyA had an existing AD forest/domain and an existing Exchange server.  An Accepted domain was added to the exchange server to allow email to be sent/received from companyB (user@companyB.com).

Now companyA is moving office and at the same time moving to office365.  They are leaving their existing office and AD/Exchange infrastructure to be used by companyB.

I would like to know what changes need to be made in order to allow companyB to reconfigure the infrastructure to reflect their own company name.  Currently owa is pointing to https://mail.companyA.com/owa, as do the autodiscover DNS records.  Company B's MX record points to mail.companyA.com.

As I understand it the following changes will be required:
1)  Create and apply a new SAN certificate from a 3rd party CA including the mail.companyB.com name
2) Create a new A DNS record: mail.companyb.com and repoint the MX record to mail.companyB.com
3) IN EMC Server Config> Client Access > set a new external url for activesync and OWA to mail.companyB.com

Should this cover everything?
0
Riana
Asked:
Riana
2 Solutions
 
Matthew BorrussoCommented:
You on the right track.

Create your new A records for DNS, both hostname and what you will reference in the MX record.
You may also want to update any associated SPF records to include the new FQDN.

You need to verify IIS and the exchange settings to make sure if there are any bindings in play that point to the old FQDN are removed and replaced with the new.

You will need to generate a CSR and purchase a certificate. You need to import the certificate onto the box(s). You will need to update exchange via a powershell command to tell exchange to present the new cert.

Once you have this sorted out, you may just need to update within exchange any masquerade domain names (ie smtp.companya.com to smtp.companyb.com) which "should" match the A record you created publicly.

At that point, you can now change your MX record within DNS, or if pointing to spam service, then you would modify the service to direct your mail from the spam filter to the server.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
As I understand it the following changes will be required:
1)  Create and apply a new SAN certificate from a 3rd party CA including the mail.companyB.com name
2) Create a new A DNS record: mail.companyb.com and repoint the MX record to mail.companyB.com
3) IN EMC Server Config> Client Access > set a new external url for activesync and OWA to mail.companyB.com

As you have stated above you will also need to do the following steps...
- make sure that you add autodiscover.domainb.com to your SAN DNS names as well
- If your internal FQDN (active directory) is different than your external FQDN for domainb.com you will also want to ensure that you create an internal zone for domainb.com, then create your A record for mail.domainb.com
- once you have done the above, you can then set your internal and external URL's for Exchange to be the same https://mial.domainb.com/owa/oab/etc

You will also need to register the certificate once you have imported the certificate on your Exchange servers.
Use the command below...
Get-ExchangeCertificate | ft

then use

Enable-ExchangeCertificate -Thumbprint xxxxxxxxxxxxxxxxxxxxxx -services "pop,imap,smtp,iis"

You need to do this on all of the CAS servers you have in your environment.

Will.
0
 
RianaAuthor Commented:
Many thanks for getting back to me on this.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now