changing external domain name and email address with SBS 2008 Server
We have an SBS 2008R2 server. We have an external domain name for email, OWA email access, Remote Web Workplace and externally hosted web page, Current external domain is say abc.com email is going to firstinitiallastname@abc.c
Management changed the company name and also added a new external domain name and externally host3ed web page with that domain name say xyz.com
They want email to now got to firstname@xyz.com and now use remote.zyx.com for OWA and Remote Web Workplace
Our issue is we have never done this with SBS. We believe it needs to be wizard driven or it can mess up everything with internal users and AD etc. The web page designers they have higher to do this have already created the web page and host it ad have created new letterhead and business cards and sent them out with xyz.com web page and email addresses. Then they come to use and say can t you just add an MX record? !!!
we don't have a lot of experience with SBS but I don't think it is anywhere that simple. We need to consider that they still want firstinitiallastname @abc.com mail to comes through.
There will be issues with SSL certificate for RWW and OWA we believe and also SBS can't have child domains so not really sure what will happen if we run the Internet Wizards and email wizard to change the external domain to xyz.com
think we loose all ability to get abc.com email;???
Can anyone explain just what needs to be done and even if it can at this point or have we been boxed in by SBS and a Web design marketing PR firm that mislead the owns and never suggested checking with us first before sending all this new stuff out. We get call telling us to "just change it" !!
Management changed the company name and also added a new external domain name and externally host3ed web page with that domain name say xyz.com
They want email to now got to firstname@xyz.com and now use remote.zyx.com for OWA and Remote Web Workplace
Our issue is we have never done this with SBS. We believe it needs to be wizard driven or it can mess up everything with internal users and AD etc. The web page designers they have higher to do this have already created the web page and host it ad have created new letterhead and business cards and sent them out with xyz.com web page and email addresses. Then they come to use and say can t you just add an MX record? !!!
we don't have a lot of experience with SBS but I don't think it is anywhere that simple. We need to consider that they still want firstinitiallastname @abc.com mail to comes through.
There will be issues with SSL certificate for RWW and OWA we believe and also SBS can't have child domains so not really sure what will happen if we run the Internet Wizards and email wizard to change the external domain to xyz.com
think we loose all ability to get abc.com email;???
Can anyone explain just what needs to be done and even if it can at this point or have we been boxed in by SBS and a Web design marketing PR firm that mislead the owns and never suggested checking with us first before sending all this new stuff out. We get call telling us to "just change it" !!
Last Comment
ASKER
ok a bit confused I am !
We don't want to get email at the old external abc.com domain for more than a few months. We also want to make the xyz.com be the OWA and RWW address, remote.xyz.com
so don't we have to run the wizard that changes all this and then create an SSL certificate for new domain name?
do we need to do all of the tech doc steps if wanting to change external domain via the wizard?
DO we have to deal with the email policy configuration?
can't we run wizard and then have the old domain name email be just a pop account for a bit???
sorry but thoroughly confused. Think I need to read thorough this some more
We don't want to get email at the old external abc.com domain for more than a few months. We also want to make the xyz.com be the OWA and RWW address, remote.xyz.com
so don't we have to run the wizard that changes all this and then create an SSL certificate for new domain name?
do we need to do all of the tech doc steps if wanting to change external domain via the wizard?
DO we have to deal with the email policy configuration?
can't we run wizard and then have the old domain name email be just a pop account for a bit???
sorry but thoroughly confused. Think I need to read thorough this some more
ASKER
also we have 2008SBS and attached references to 2011 . is there much difference and do all the referenced features an screens appear the same?
>We don't want to get email at the old external abc.com domain for more than a few months.
But you do want to get it, so you don't want to change anything having to do with this domain.
>We also want to make the xyz.com be the OWA and RWW address, remote.xyz.com
These should just be public DNS entries pointing to the same IP addresses that the old OWA and RWW are pointing to. If you have SSL certs, you'll need new ones.
>so don't we have to run the wizard that changes all this and then create an SSL certificate for new domain name?
I'm not sure what the wizard does. Running it may change your email domain, not add another one. This document is for adding another one.
>DO we have to deal with the email policy configuration?
Do you mean the recipient policy? It's what will give your mailboxes the additional address of user@xyz.com. Otherwise you'll have to manually change each of the users' email addresses and as new users are added you'll have to change them manually too.
>can't we run wizard and then have the old domain name email be just a pop account for a bit???
Since your current email is being sent to your mail server using SMTP, you'd have to have some other host accept email that you could then POP down. This is going to be a lot messier than just adding another authoritative email domain.
But you do want to get it, so you don't want to change anything having to do with this domain.
>We also want to make the xyz.com be the OWA and RWW address, remote.xyz.com
These should just be public DNS entries pointing to the same IP addresses that the old OWA and RWW are pointing to. If you have SSL certs, you'll need new ones.
>so don't we have to run the wizard that changes all this and then create an SSL certificate for new domain name?
I'm not sure what the wizard does. Running it may change your email domain, not add another one. This document is for adding another one.
>DO we have to deal with the email policy configuration?
Do you mean the recipient policy? It's what will give your mailboxes the additional address of user@xyz.com. Otherwise you'll have to manually change each of the users' email addresses and as new users are added you'll have to change them manually too.
>can't we run wizard and then have the old domain name email be just a pop account for a bit???
Since your current email is being sent to your mail server using SMTP, you'd have to have some other host accept email that you could then POP down. This is going to be a lot messier than just adding another authoritative email domain.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
>so don't we have to run the wizard that changes all this and then create an SSL certificate for new domain name?
> I'm not sure what the wizard does. Running it may change your email domain, not add another one. This document is for adding another one.
I don't think we wan to just add another. IT appears that we need to make the new one the primary and do it by running the wizard to change the external domain name.. This changes the RWW and OWA to remote.xyz.com (new one) and that is what they want to do. They then just want to receive old email at abc.com for a few months.
If we just add xyz.com it won't change the RWW and OWA I think
> I'm not sure what the wizard does. Running it may change your email domain, not add another one. This document is for adding another one.
I don't think we wan to just add another. IT appears that we need to make the new one the primary and do it by running the wizard to change the external domain name.. This changes the RWW and OWA to remote.xyz.com (new one) and that is what they want to do. They then just want to receive old email at abc.com for a few months.
If we just add xyz.com it won't change the RWW and OWA I think
ASKER
The last link for the article by Sean is very good. With SBS you need to run the internet wizard to change the external domain to xyz.com it leaves the old firstinitiallastname@abc.c
I am going to try what Sean says in the article but it doesn't quick address the order we are doing things in and everything I have read and heard is that it is very important in SBS to use the wizards and do things in correct order.
will let you know
thanks
I am going to try what Sean says in the article but it doesn't quick address the order we are doing things in and everything I have read and heard is that it is very important in SBS to use the wizards and do things in correct order.
will let you know
thanks
SBS
Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).
59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
http://blogs.technet.com/b/sbs/archive/2011/04/13/how-to-configure-sbs-2011-standard-to-accept-e-mail-for-multiple-authoritative-domains.aspx
You'll need an MX record and A record for the new domain in your public DNS.
Edit: Adding additional mail domains won't stop you from getting your old email. You'll also need to make sure your users have the appropriate email addresses.
And when you add the public DNS record you want to make sure you're adding it, and not replacing your current domain's DNS entries. That will break your ability to get email from the old domain.