W2003 Upgrade Question

  • Thread starter Thread starter John Oliver
  • Start date Start date
J

John Oliver

I have 3 DC's which are GC's in a three site setup with a Single Domain.
The Corporate site GC holds all 5 FSMO roles and the other two sites hold a
GC each. Each site has Windows 2000 Server with Exchange 2000. I am going
to be replacing all servers with new hardware and Windows 2003 and Exchange
2003. Here is my question regarding the upgrade.

First run the Mangled Attributes fix for Exchange then after I run /ADPREP
and /Domainprep on the Corporate GC. I will then install Windows 2003 and
Exchange 2003 on a new server at this location. I would then like to make
this new Server a DC then GC. I assume I can just manually transfer the
FSMO roles from the existing Windows 2000 GC to the new Windows 2003 DC at
Corporate. Then run DCPROMO to remove the current Windows 2000 Server at
corporate. Then I can move to the other sites and repeat the process
without the FSMO transfer process of course. I would allow time for
replication but the point of my question is I want to make sure I can bring
my Windows 2000 AD to 2003 AD without having to do an in-place upgrade of
the Corporate Windows 2000 GC. Is this correct? Thanks for any input.
 
Yes, but don't forget about DNS!! Also, don't forget GCs, DHCP, WINS, etc.

-- http://www.msresource.net/content/view/24/47/


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I have 3 DC's which are GC's in a three site setup with a Single Domain.
The Corporate site GC holds all 5 FSMO roles and the other two sites hold a
GC each. Each site has Windows 2000 Server with Exchange 2000. I am going
to be replacing all servers with new hardware and Windows 2003 and Exchange
2003. Here is my question regarding the upgrade.

First run the Mangled Attributes fix for Exchange then after I run /ADPREP
and /Domainprep on the Corporate GC. I will then install Windows 2003 and
Exchange 2003 on a new server at this location. I would then like to make
this new Server a DC then GC. I assume I can just manually transfer the
FSMO roles from the existing Windows 2000 GC to the new Windows 2003 DC at
Corporate. Then run DCPROMO to remove the current Windows 2000 Server at
corporate. Then I can move to the other sites and repeat the process
without the FSMO transfer process of course. I would allow time for
replication but the point of my question is I want to make sure I can bring
my Windows 2000 AD to 2003 AD without having to do an in-place upgrade of
the Corporate Windows 2000 GC. Is this correct? Thanks for any input.
 
Yes, I will take care of all the other requirements just wondered about
transferring FSMO Roles from a Windows 2000 GC to Windows 2003 DC. I assume
once I make the transfer I will still have to go into Sites & Services MMC
to make the Windows 2003 DC a GC? Everything I have experienced so far is
by doing in-place upgrades to Windows 2003 thus bringing the domain to
Windows 2003 AD automatically.
 
Yes, you have to enable the GC. It will not do this automatically (except
for on the first DC created in a domain).

It's fine to transfer the OM roles from 2k to 2k3 or vice versa.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Yes, I will take care of all the other requirements just wondered about
transferring FSMO Roles from a Windows 2000 GC to Windows 2003 DC. I assume
once I make the transfer I will still have to go into Sites & Services MMC
to make the Windows 2003 DC a GC? Everything I have experienced so far is
by doing in-place upgrades to Windows 2003 thus bringing the domain to
Windows 2003 AD automatically.
 
ptwilliams said:
Yes, you have to enable the GC. It will not do this automatically (except
for on the first DC created in a domain).
Click to expand...

....first DC in FOREST actually.

(Just a small improvement.)

GCs are really a forest job.
It's fine to transfer the OM roles from 2k to 2k3 or vice versa.
Click to expand...
 
Yeah, this is a good plan. As everyone else is suggesting, you'll need to
pay attention to the other services: GC, DNS, DHCP, WINS. You should also
make sure that you have a secondary DC at the core. Remember that not all
of the FSMO roles should be on the same box and that not all like being on a
GC. Take the best box from the old set and make that a secondary at the
core.

Make sure that your replication completes after the forest prep and the
domain prep. It is better to do this completely than to jump the gun and
not have verified this.

Remember REPLMON, DCDIAG and NETDIAG are your friends. You want to make
sure your domain is completely healthy before you do an upgrade. Spend the
time to resolve all issues, especially with DNS, before starting this.
 
Remember that not all of the FSMO roles should be on the same box and that
not all like being on a
Click to expand...
GC.

I've seen some recommendations that in huge environments this is the case,
but haven't really ever seen the need to do this. The IM/ GC issue isn't an
issue in my eyes, and I'd prefer all the roles on one server. If that
server ever fails and I can't get it back on line (unlikely) then I'll seize
the roles...no big deal whatsoever. Spreading these things is asking for
trouble when you've a disparate environment, both physically and
administratively...

The last thing you want is a Junior admin in the London team going and doing
something to one of your servers...

(I'm no where near London)


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Yeah, this is a good plan. As everyone else is suggesting, you'll need to
pay attention to the other services: GC, DNS, DHCP, WINS. You should also
make sure that you have a secondary DC at the core. Remember that not all
of the FSMO roles should be on the same box and that not all like being on a
GC. Take the best box from the old set and make that a secondary at the
core.

Make sure that your replication completes after the forest prep and the
domain prep. It is better to do this completely than to jump the gun and
not have verified this.

Remember REPLMON, DCDIAG and NETDIAG are your friends. You want to make
sure your domain is completely healthy before you do an upgrade. Spend the
time to resolve all issues, especially with DNS, before starting this.
 
Back
Top