C
Craig Matchan
Hi all,
I have a problem and I would like to tap into the knowledge of this group
for advise and possibly any white papers relating to the topic.
Currently we are run a Win2000 Serv and Linux environment. Within the Win2k
area we run AD and Exch2000. We are looking at upgrading to Win2003 /
Exch2003. Currently our AD consists of 2 DCs (both of which also run DNS
services). To complicate things, the current Exch2k Server acts as a DC,
though not the master roles. I know that is not ideal but at the time of the
build I had no choice.
At first I was considering just upgrading to Win2003 and then Exch2003 on
the existing servers, however the company has now decided to change company
names and hence want's our website and mail server to operate under a new
domain name.
From what I have read there is no way to rename a Win2k Domain if it is in
Native mode, which our is. I've also just read that although you can rename
a Win2003 domain, you cannot if a Exch2k server is located within the
domain, which in our case it would be. Also, I must admit to being rather
daunted by the MS paper on domain renaming for Win2003. It seems a complex
and danger fraught process. Add to this that the fact that the existing
servers, IBM NF 5500M20's do not have Win2003 certification. All in all I am
not confident in a domain rename. Lastly, I must admit to not being
confident in the integrity of our current AD schema due to a failed install
of Exch2k in the early days of our migration from Banyan Vines to
Win2k/Exch2k. Basically the Exchange2k install failed, but traces of it were
left behind and I had to resort to the manual uninstall for Exch2k as
described by one of the MS papers. Although this allowed us to re-install
Exch2k (onto a different server), parts of AD still appear to reference the
failed installed instance on the original server. Though things appear to
work ok, it's always been in the back of my mind when something odd happens.
So what I am now considering is to build a set of new Win2003 servers and
create a new domain from scratch..along with a new install of Exch2003. This
appeals to me as my work are prepared to purchase new h/w for this and it
means there will be no impact on our production system whilst we build the
new domain. I assume (still reading manuals) that once the new domain is
setup and configured I should be able to
- migrate/move users from the old domain to the new domain
- migrate users mailbox from Exch2k server to Exch2003
- migrate member servers from the old domain to the new domain
My question are
1. Am I overreacting to the domain rename issue..is it safe? What have
others done faced with a similar situation?
2. Assuming we do build the new domain on new servers, how easy is it to
migrate users,mailbox's, member servers, lists between the two domains. I
presume the ADC control panel will allow the user and member server
movements, but I am not sure on the Exch2k front. I presume the Exchange Sys
Management tool would be used.
Any comments / suggestions / references most welcome
regards
Craig
I have a problem and I would like to tap into the knowledge of this group
for advise and possibly any white papers relating to the topic.
Currently we are run a Win2000 Serv and Linux environment. Within the Win2k
area we run AD and Exch2000. We are looking at upgrading to Win2003 /
Exch2003. Currently our AD consists of 2 DCs (both of which also run DNS
services). To complicate things, the current Exch2k Server acts as a DC,
though not the master roles. I know that is not ideal but at the time of the
build I had no choice.
At first I was considering just upgrading to Win2003 and then Exch2003 on
the existing servers, however the company has now decided to change company
names and hence want's our website and mail server to operate under a new
domain name.
From what I have read there is no way to rename a Win2k Domain if it is in
Native mode, which our is. I've also just read that although you can rename
a Win2003 domain, you cannot if a Exch2k server is located within the
domain, which in our case it would be. Also, I must admit to being rather
daunted by the MS paper on domain renaming for Win2003. It seems a complex
and danger fraught process. Add to this that the fact that the existing
servers, IBM NF 5500M20's do not have Win2003 certification. All in all I am
not confident in a domain rename. Lastly, I must admit to not being
confident in the integrity of our current AD schema due to a failed install
of Exch2k in the early days of our migration from Banyan Vines to
Win2k/Exch2k. Basically the Exchange2k install failed, but traces of it were
left behind and I had to resort to the manual uninstall for Exch2k as
described by one of the MS papers. Although this allowed us to re-install
Exch2k (onto a different server), parts of AD still appear to reference the
failed installed instance on the original server. Though things appear to
work ok, it's always been in the back of my mind when something odd happens.
So what I am now considering is to build a set of new Win2003 servers and
create a new domain from scratch..along with a new install of Exch2003. This
appeals to me as my work are prepared to purchase new h/w for this and it
means there will be no impact on our production system whilst we build the
new domain. I assume (still reading manuals) that once the new domain is
setup and configured I should be able to
- migrate/move users from the old domain to the new domain
- migrate users mailbox from Exch2k server to Exch2003
- migrate member servers from the old domain to the new domain
My question are
1. Am I overreacting to the domain rename issue..is it safe? What have
others done faced with a similar situation?
2. Assuming we do build the new domain on new servers, how easy is it to
migrate users,mailbox's, member servers, lists between the two domains. I
presume the ADC control panel will allow the user and member server
movements, but I am not sure on the Exch2k front. I presume the Exchange Sys
Management tool would be used.
Any comments / suggestions / references most welcome
regards
Craig