Moving a PDC to new hardware
Tech-Archive recommends: Fix windows errors by optimizing your registry
Hi
Haven't done this before so seeking some basic advice
We have a Windows 2000 server as a domain controller in a small network with
about a dozen XP clients
We need to move to a new Windows 2003 server (new physical server) with
minimum disruption to the client PC setups
Question - what is the easiest way of achieving this ?
We would ideally like the new server to have the same name and IP address as
the old one
We have the option of upgrading the Windows 2000 server to 2003 first if
that makes the transition easier
Help !
TIA
Mike
.
Relevant Pages
- RE: Printing from Win9x clients stops
... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
(microsoft.public.windows.server.sbs) - RE: Printing from Win9x clients stops
... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
(microsoft.public.windows.server.sbs) - RE: Printing from Win9x clients stops
... > and make sure this software does not interfere with SBS Server. ... > clients, please disable it and try again. ... Create a local printer and redirect the port to the network server. ...
(microsoft.public.windows.server.sbs) - Re: User to change TCP/IP settings:
... If you happen to have any Windows XP or Server 2003 member server clients do ... > Administrative Templates -> Network -> Network Connections) there are a ...
(microsoft.public.win2000.active_directory) - Re: random lockouts
... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
(microsoft.public.win2000.security) |
|
