Howdy All,
I inherited this network I manage about 19 months ago and am finally getting to make some very needed changes! Right now ONE of my domain controllers is also an exchange 2003 server (I didn't do this!) and servs up not only all the goodness of exchange but DHCP, DNS, Printers, Files and NTP -- all of this in 1gb of RAM.
So since I need to add more exchange users I'm moving everything but exchange off of the box (finally!). Files and printers are easy enough and I can handle all of the remappings and what not easy enough.
DHCP moving to the new server looks like it has a well defined path and should move easy enough (and if not, I don't have that many reservations and can recreate them if really necessary).
DNS is all ADI zones so I'm not to worried about moving those records.
The server has the following FSMO roles that will need to be moved:
- Schema, PDC Emulator, Infastructure (RID and Domain tree are handeled by my other DC)
Both of my existing domain controllers are global catalogs.
I'm not moving any of this stuff to an existing server, I'm purchasing a new server to move all this stuff on to (actually two, one will handle ONLY file and printers and will not be a DC)
I am only dealing with one domain and thus one forest. The domain Functional Level is Windows Server 2003, the forest functional level is Windows 2000.
So here is my question: What are the gotchas in this process, does anybody have a well defined check list for checking and verifying everything that needs to be moved (generally, everybody's environment is a little different) prior to removing this machine as a domain controller. Exchange always complicates matters so what should I look out for when I go to remove the domain controller role on the exchange side?
Any advice or tips from other people having gone through or in the process of going through and cleaning this process up would be greatly appreciated.
Mark At LMFJ
I inherited this network I manage about 19 months ago and am finally getting to make some very needed changes! Right now ONE of my domain controllers is also an exchange 2003 server (I didn't do this!) and servs up not only all the goodness of exchange but DHCP, DNS, Printers, Files and NTP -- all of this in 1gb of RAM.
So since I need to add more exchange users I'm moving everything but exchange off of the box (finally!). Files and printers are easy enough and I can handle all of the remappings and what not easy enough.
DHCP moving to the new server looks like it has a well defined path and should move easy enough (and if not, I don't have that many reservations and can recreate them if really necessary).
DNS is all ADI zones so I'm not to worried about moving those records.
The server has the following FSMO roles that will need to be moved:
- Schema, PDC Emulator, Infastructure (RID and Domain tree are handeled by my other DC)
Both of my existing domain controllers are global catalogs.
I'm not moving any of this stuff to an existing server, I'm purchasing a new server to move all this stuff on to (actually two, one will handle ONLY file and printers and will not be a DC)
I am only dealing with one domain and thus one forest. The domain Functional Level is Windows Server 2003, the forest functional level is Windows 2000.
So here is my question: What are the gotchas in this process, does anybody have a well defined check list for checking and verifying everything that needs to be moved (generally, everybody's environment is a little different) prior to removing this machine as a domain controller. Exchange always complicates matters so what should I look out for when I go to remove the domain controller role on the exchange side?
Any advice or tips from other people having gone through or in the process of going through and cleaning this process up would be greatly appreciated.
Mark At LMFJ