Windows Server

Cakeholes · Guest

Ok here is my scenario:

- Single W2K Domain (single site)
- Approximately 80 hosts
- 2 servers
- One server to eventually be phased out completely (just a desktop running
W2K Server acting as BDC, although it does control all FSMO roles as it was
the first DC on the network)
- Main file/print server to be replaced by new W2K3 server (this server will
eventually be resurrected as a W2K3 server when time and money permit)

I have my new W2K3 server on the network as a member server. After looking
at the FSMT etc. I have come to a conclusion that it makes more sense to
migrate the files without using DFS as I will promote this server to a DC
(yes I know it's not advisable for file server to be DC but this will be a
one server network for some time).

I have seen a number of posts where people are trying to replace the
existing server by renaming the new server to replace the old server and I
would like to do the same. I think I know all of the steps I need to take
but the order is where I'm a little unclear (and if I'm missing anything
else I hope you will help guide me!). So here is the way I plan to go about
this:

1.) Run ADPREP /FORESTPREP and ADPREP /DOMAINPREP
2.) Use FSMT to migrate data shares and permissions etc. to new server.
3.) DCPROMO the new server to make it a DC
4.) Transfer all FSMO roles
5.) Configure DHCP, DNS, WINS etc. on new server
6.) Demote old file server then rename it
7.) Rename new server with old server's name and ensure that it has the old
server's IP as well

Now I should have a W2K3 domain with one W2K3 DC and 1 W2K DC and 1 W2K
member server. From here I hope to muster up the funding to buy another
license of W2K3 Server and rebuild the old server and have it as a second DC
and eventually phase out the oldest (desktop) W2K Server.

Any advice is appreciated and if I have left out any details let me know. I
should have a full weekend (Friday evening to Sunday evening) to peform all
necessary tasks when the time comes.

Thanks,

Kevin Coles

Kevin Coles · Guest

Since my post I discovered a fly in the ointment in that I cannot rename a
W2K3 DC unless all of my domain controllers are W2K3 (functional level as
well?). Can you work around this by temproarily taking the W2K DCs offline
while the rename is done or does the domain functional level have to be W2K3
native for a rename to be possible?

Kevin Coles

"Cakeholes" <kcoles@fransen-eng.com> wrote in message
news:fv96f.48573$ir4.16078@edtnps90...

Vincent Xu [MSFT] · Guest

Hi Kevin,

Please refer to following article to rename Windows 2003 DC.

814589 HOW TO: Rename a Windows 2003 Domain Controller
http://support.microsoft.com/?id=814589

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

Kevin Coles · Guest

Vincent,

That link did not work....although I believe I have already read it.

Can anyone provide a little more detail aside from referring to KB articles?
I appreciate their importance and I am collecting as many as I can for
reference, but I would really appreciate some real world advice and input.

Thanks,

Kevin Coles

"Vincent Xu [MSFT]" <v-xuwen@online.microsoft.com> wrote in message
news:RvwRphH2FHA.3220@TK2MSFTNGXA01.phx.gbl...

Kevin Coles · Guest

OK I have had a chance to research a little more and would like to outline
my migration plan again, taking into account the fact that I can't make this
a native 2003 domain until later on down the road.

1.) Run ADPREP /FORESTPREP and ADPREP /DOMAINPREP on FSMO master (Server1)
2.) Use FSMT to migrate data shares and permissions etc. from old file
server (Server2) to new server.(Server3)
3.) Demote old file (Server2) server then rename it to OldServer and change
static IP
4.) Rename new server (Server3) with old server's name (Server2) and change
static IP to that of old server
5.) DCPROMO the new server to make it a DC
6.) Transfer all FSMO roles from Server1
7.) Configure DHCP, DNS, WINS etc. on new server

If anyone has any suggestions or can think of anything that would make this
unadvisable I would appreciate your input.

Thanks,

Kevin Coles

"Kevin Coles" <kcoles@fransen-eng.com> wrote in message
news:WA67f.51200$S4.9542@edtnps84...

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1