Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
I had to rebuild a server on a LAN last week. It's a Windows 2000
server running AD. I put another Win2K server running AD in it's place
temporarily. Between setting up AD, the user accounts and un-joining
and rejoining the 10 client computers to the domain I spent over 6
hours.
I have to return the old server to service THIS weekend and I'm
looking for a quick and easy way to do this. Basically I have a
Windows 2000 server replacing another Windows 2000 server. What is the
easiest way to accomplish this without having to go back an rejoin all
the client workstations to the new (rebuilt) server?
Would NTBackup help? Will I have to do anything to the client
computers??
Use what ever your current method is (DHCP or manually) to point all AD
clients to the new DNS server.
You *may* have to run ipconfig/flushdns followed by ipconfig/registerdns on
the clients to refresh the DNS cache.
hth
DDS W 2k MVP MCSE
<<Fran>> wrote in message news:f14ej0hfcb39spo1mcam1ksai07n03rk3f@4ax.com...
> I had to rebuild a server on a LAN last week. It's a Windows 2000
> server running AD. I put another Win2K server running AD in it's place
> temporarily. Between setting up AD, the user accounts and un-joining
> and rejoining the 10 client computers to the domain I spent over 6
> hours.
>
> I have to return the old server to service THIS weekend and I'm
> looking for a quick and easy way to do this. Basically I have a
> Windows 2000 server replacing another Windows 2000 server. What is the
> easiest way to accomplish this without having to go back an rejoin all
> the client workstations to the new (rebuilt) server?
>
> Would NTBackup help? Will I have to do anything to the client
> computers??
>
> Any suggestions are welcomed!
>
> -Fran-
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.