Re: Rename Domain

In news:16D95562-D58C-4421-83ED-FE6902C32BCD@xxxxxxxxxxxxx,
blaine <blaine@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hello;

We have 1 domain name for our internal domain and external website.
company.com. It has been brought to my attention that this may cause
problem for us in the future.

Meh. The only problem you're likely to have is that internal users who try
to go to your publicly hosted website/whatnot at whatever.company.com will
not be able to reach it unless you create static host entries in your AD
DNS, which is easy enough to do.

Renaming a domain with Exchange in the picture is not a pretty thing and I
would avoid it....unless you absolutely must do so, and in this case I don't
see the point.

We currently have 2 - 2k3 servers, 1
with exchange 2003 and the other with DC,DNS, DHCP, AD, SQL 2005, 2
IIS websites and 15 users. In the near future, (3 month from now) we
will be adding a child domain,

Why a child domain, just out of curiosity?

10 servers, and 100 users on this
domain. I beleive that if we need to change our domain name, we
should do it now before adding the child/servers/users.
new.company.com

From reading some documents, it soulds like the best and the cleanest
solution to this is the creat the new domain and transfer our current
user over to this new domain name and demote the old domain. But I
have some questions. How will this affect our current runnig
programs.

How will this affect the our current users sign-ons (Active
Directory)? I will need to visit every PC and rejoin to the new
domain. Will this curate a new user on the domain and will I need to
transfer the user data to the new domain user.

How will this affect the SQL 2005? What do I need to do to make sure
everyone still have the same access. (I was thinking we just demote
this server and attach it to the new domain or just rebuild it
(something similar upgrading from SQL 2k to 2K3))

How will this affect the exchange server? will email still work as
@company.com.
What steps can I follow to move the exchange svr to the new domain?

Any insight would be help. Thanks for your time.
Blaine



.

Relevant Pages

  • Re: Internal vs. External Domain Name
    ... will give problems if you want to reach the company's website and email. ... > The external domain name, for example, MYDOMAIN.com is registered and has ... The internal domain name under AD is ... What other Exchange issues should I be concerned about? ...
    (microsoft.public.win2000.networking)
  • Re: Internal domain name conflict
    ... "Lanwench [MVP - Exchange]" wrote in message ... I know the issue is that they named their internal domain ... website on the internal system. ... Note that SBS questions are best posted in m.p.windows.server.sbs - although this particular one isn't SBS specific, there are many things you have to do differently in SBS. ...
    (microsoft.public.windows.server.networking)
  • Re: win2003 & exchange 2003 mail problem
    ... Have a look in IIS Manager under the Default Exchange website, ... > I have a win 2003 enterprise edition server with one domain, ...
    (microsoft.public.exchange.admin)
  • Re: Point me in the right direction??
    ... for internal users since you will be hosting a website and email locally, ... If you are going to use exchange, using chemical.com will make that setup ... easier since Exchange adopts the Active Directory domain name as its default ... If you use chemical.mfg the Exchange setup will use that name ...
    (microsoft.public.win2000.dns)
  • Re: Exchange 2003 ActiveSync, Sprint PPC-6700 and SSL: Giving me a
    ... > certificate, but once you've got it working it just continues to work. ... Both Exchange and the Exchange OMA virtual ... >>> My certification path was the same www.mydomain.com that my website uses ... When I look at IIS in Server Management, ...
    (microsoft.public.windows.server.sbs)
Loading