Company/Domain Name Change

  • Thread starter Thread starter ratheza
  • Start date Start date
R

ratheza

I'm still searching through the groups to find the parts and pieces of
the solution I'm looking for, but I figured I'd throw this out there
in the meantime.

1. Windows 2000 Active Directory, mixed mode (2 NT 4.0 DC's I
couldn't care less about).

2. Exchange 2000.

3. One domain - myhospital.org

4. Hospital is changing names, email addresses, etc.

5. Timing is not TOO bad, I've got my team set to visit every
workstation for some upgrades (HIPAA).

6. "The issue" My understanding is that when I created the domain
originally, since it's a single domain, that it is in essense my
forest. The new domain - mynewhospital.org - I'll need to create this
on a new server outside of our current AD setup. Then I can demote my
other AD servers for myhospital.org and then have them join the
mynewhospital.org domain. Does this sound about right?

I guess my big question involves Exchange. We would like to keep
myhospital.org in use for a while, in order to capture mail from
contact unaware of the name change.

I need to ask at this point - am I thinking correctly (for the most
part), or am I WAY of base.

Thanks for any input.
 
ratheza said:
I'm still searching through the groups to find the parts and pieces of
the solution I'm looking for, but I figured I'd throw this out there
in the meantime.

1. Windows 2000 Active Directory, mixed mode (2 NT 4.0 DC's I
couldn't care less about).

2. Exchange 2000.

3. One domain - myhospital.org

4. Hospital is changing names, email addresses, etc.

5. Timing is not TOO bad, I've got my team set to visit every
workstation for some upgrades (HIPAA).

6. "The issue" My understanding is that when I created the domain
originally, since it's a single domain, that it is in essense my
forest. The new domain - mynewhospital.org - I'll need to create this
on a new server outside of our current AD setup. Then I can demote my
other AD servers for myhospital.org and then have them join the
mynewhospital.org domain. Does this sound about right?
Click to expand...


Solution 1: deploy new domain with new name, mynewhostpial.org. You will
have to deploy new exchange organization too to build all from scratch.
Migrate usera accounts and mailboxes to new domain and new exchange
organization. After this demote old domain and You cen join old server
(after demotation for DCs) to new domain. To migrate domain resources
You can use ADMTv2 and Mailboxes can be migrated with exchange migration
Wizard.

Solution 2: I don't know if this can be done but You can upgrade Your
domain to windows 2003 and rename the domain to new name.
I guess my big question involves Exchange. We would like to keep
myhospital.org in use for a while, in order to capture mail from
contact unaware of the name change.
Click to expand...

This is easy, in Exchange just add another e-mail SMTP address in
Recipient policy, check the checkbox which states that "This exchange is
responsible for delivering mail for this domain" (or something like this
- i'm writing it from my memory) and this should be working. Of course
You should update Your SMTP servers configuration to allow relay for
this domain If You have some restriction for realy (and I think You can
have such :) ). This will give You ability to server mail services for
both domains.
 
That sounds pretty resonable, thanks alot!


Tomasz Onyszko said:
Solution 1: deploy new domain with new name, mynewhostpial.org. You will
have to deploy new exchange organization too to build all from scratch.
Migrate usera accounts and mailboxes to new domain and new exchange
organization. After this demote old domain and You cen join old server
(after demotation for DCs) to new domain. To migrate domain resources
You can use ADMTv2 and Mailboxes can be migrated with exchange migration
Wizard.

Solution 2: I don't know if this can be done but You can upgrade Your
domain to windows 2003 and rename the domain to new name.


This is easy, in Exchange just add another e-mail SMTP address in
Recipient policy, check the checkbox which states that "This exchange is
responsible for delivering mail for this domain" (or something like this
- i'm writing it from my memory) and this should be working. Of course
You should update Your SMTP servers configuration to allow relay for
this domain If You have some restriction for realy (and I think You can
have such :) ). This will give You ability to server mail services for
both domains.
Click to expand...
 
Why not leave your AD alone and just add the new domain name to Exchange?
Then users will get mail sent to both, no changes in profiles, passwords or
anything. Users wont even notice.
Your AD name and the domains that Exchange handles do not have to be the
same.
Exchange can handle many domain names.
Much easier.
 
I did exactly that at a hospital less than a year ago. worked like a charm.
Left the old domain in place, added the proper DNS records for the new
domain, eventually phased out the old email address and no longer resolve
the old www. Perfect. I guess it's a little weird that all internal
addresses are still oldaddress.org, but no big deal really. You rarely have
to specify by complete FQDN, so it goes unnoticed for most users.
 
Back
Top