How to replace Windows 2000 domain controller with 2003

  • Thread starter Thread starter Lasse
  • Start date Start date
L

Lasse

Guest
Hi

I am planning to upgrade our current Windows 2000 servers to Windows Server
2003.
We have four location in different cities (HQ and 3 branch offices). At HQ
we have a Windows 2000 domain controller and a Server 2003 domain controller,
at each of the branch offices we have one Windows 2000 DC. All the FSMO roles
for the entire domain is located on the 2000 DC at HQ.
I don't want to upgrade the 2000 servers, I want to do a fresh Server 2003
installation but I can't figure out how to do it. All four locations have
been setup in AD Sites and Services with four different subnets.
Is it as simple as demoting the branch servers and removing them from the
domain and then do a fresh installation?
If I demote a branch office DC will the users log on to one of the other
DC's in the domain despite been on a different IP segment?
At HQ I can just move the FSMO roles to the 2003 DC and demote the 2000 DC
and then do a fresh installation.

Hopefully some one can understand my problem and give me an idea how to do it?

/Lasse
 
Re: How to replace Windows 2000 domain controller with 2003

Hi Lasse,
Not so complicated. You got the main piece figured out already and that is
at HQ you will need to transfer the FSMO roles from the Win 2000 DC to the
Win 2003 DC thaen you can do a DCPROMO on the Win 2000 server make it a
member server then remove it from the domain and do a fresh install of Win
2003.
Now for your remote sites I am assuming given the information you have all
remote offices connected via a VPN? I am assuming that given you have setup
DC's in the remote offices to handle authentication locally. If that is
correct then you can take these remote DC's and DCPROMO them to members
servers and remove them from the domain and do fresh installs of Win 2003.
You users will be authenticated to your home office. It may take a longer
for them to authenticate for obvious reasons. It may also be a good idea to
do a Metadata cleanup on the HQ DC after each DC is removed.


"Lasse" <Lasse@discussions.microsoft.com> wrote in message
news:F92E948C-1F18-4CAF-ACED-3D743C476525@microsoft.com...
> Hi
>
> I am planning to upgrade our current Windows 2000 servers to Windows
> Server
> 2003.
> We have four location in different cities (HQ and 3 branch offices). At HQ
> we have a Windows 2000 domain controller and a Server 2003 domain
> controller,
> at each of the branch offices we have one Windows 2000 DC. All the FSMO
> roles
> for the entire domain is located on the 2000 DC at HQ.
> I don't want to upgrade the 2000 servers, I want to do a fresh Server 2003
> installation but I can't figure out how to do it. All four locations have
> been setup in AD Sites and Services with four different subnets.
> Is it as simple as demoting the branch servers and removing them from the
> domain and then do a fresh installation?
> If I demote a branch office DC will the users log on to one of the other
> DC's in the domain despite been on a different IP segment?
> At HQ I can just move the FSMO roles to the 2003 DC and demote the 2000 DC
> and then do a fresh installation.
>
> Hopefully some one can understand my problem and give me an idea how to do
> it?
>
> /Lasse
>
>
 
Re: How to replace Windows 2000 domain controller with 2003

Hi Mr. Rocker :-)

Thanks for your quick reply.

We are using VPN connections between all the locations. I think I got it
figured out now, was just a bit uncertain about the branch offices. I will do
the upgrade outside working hours so the users shouldn't be affected.

I was planning on using Print Migrator to save all the local printer
installations and then saving all the data on a external drive and then do
the fresh installation.

/Lasse

"SBS Rocker" wrote:

> Hi Lasse,
> Not so complicated. You got the main piece figured out already and that is
> at HQ you will need to transfer the FSMO roles from the Win 2000 DC to the
> Win 2003 DC thaen you can do a DCPROMO on the Win 2000 server make it a
> member server then remove it from the domain and do a fresh install of Win
> 2003.
> Now for your remote sites I am assuming given the information you have all
> remote offices connected via a VPN? I am assuming that given you have setup
> DC's in the remote offices to handle authentication locally. If that is
> correct then you can take these remote DC's and DCPROMO them to members
> servers and remove them from the domain and do fresh installs of Win 2003.
> You users will be authenticated to your home office. It may take a longer
> for them to authenticate for obvious reasons. It may also be a good idea to
> do a Metadata cleanup on the HQ DC after each DC is removed.
>
>
> "Lasse" <Lasse@discussions.microsoft.com> wrote in message
> news:F92E948C-1F18-4CAF-ACED-3D743C476525@microsoft.com...
> > Hi
> >
> > I am planning to upgrade our current Windows 2000 servers to Windows
> > Server
> > 2003.
> > We have four location in different cities (HQ and 3 branch offices). At HQ
> > we have a Windows 2000 domain controller and a Server 2003 domain
> > controller,
> > at each of the branch offices we have one Windows 2000 DC. All the FSMO
> > roles
> > for the entire domain is located on the 2000 DC at HQ.
> > I don't want to upgrade the 2000 servers, I want to do a fresh Server 2003
> > installation but I can't figure out how to do it. All four locations have
> > been setup in AD Sites and Services with four different subnets.
> > Is it as simple as demoting the branch servers and removing them from the
> > domain and then do a fresh installation?
> > If I demote a branch office DC will the users log on to one of the other
> > DC's in the domain despite been on a different IP segment?
> > At HQ I can just move the FSMO roles to the 2003 DC and demote the 2000 DC
> > and then do a fresh installation.
> >
> > Hopefully some one can understand my problem and give me an idea how to do
> > it?
> >
> > /Lasse
> >
> >
>
>
>
 
Back
Top