Discussions

Migrating DHCP, Print Services, Data Directories to a new Server

+
0 Votes
Locked

Migrating DHCP, Print Services, Data Directories to a new Server

bweikel
I have a Server that is running Windows 2000 that is being used as the DHCP, Print Services, Data Directory and Lotus Notes Mail server. I have purchased a new Windows 2003 server and need to migrate these applications. My plan was to upgrade the existing server to Windows 2003 and proceed to migrate the DHCP, Print Services and data directory to a seperate 2003 server. The new purchased server would be used as the new lotus notes mail server. I'm thinking about using the same computer name and ip address for the new notes mail server. What is the recommended steps for moving DHCP and print services. Don't know if there is an easy way to perform this. Does anyone have any experience with Acronis True Image software
  • +
    0 Votes
    jpeoples

    As long as you have some flexability when it comes to launch day for the Notes server your best bet is to build the new box as a new server. That way if anything screws up you can shut it down and return to your previous configuration with no down time. If you make DHCP one of the last things to be set up you can remove the server from your production network and hook it up to an empty hub/switch. Then you can create your DHCP configuration exactly as you had it on the old box. When you're ready hook the new box back up and turn off DHCP on the old box. Since there will be only one DHCP server available to your workstations they will use it to get their info even if they then connect to the old server for shares. You can pretty much follow the same process for printing except that you'll have to make some adjustments for the printer's physical connection to the server. Depending on how extensive your network is you can use a script at login or group policies. Let me know if you have any questions.

  • +
    0 Votes
    jpeoples

    As long as you have some flexability when it comes to launch day for the Notes server your best bet is to build the new box as a new server. That way if anything screws up you can shut it down and return to your previous configuration with no down time. If you make DHCP one of the last things to be set up you can remove the server from your production network and hook it up to an empty hub/switch. Then you can create your DHCP configuration exactly as you had it on the old box. When you're ready hook the new box back up and turn off DHCP on the old box. Since there will be only one DHCP server available to your workstations they will use it to get their info even if they then connect to the old server for shares. You can pretty much follow the same process for printing except that you'll have to make some adjustments for the printer's physical connection to the server. Depending on how extensive your network is you can use a script at login or group policies. Let me know if you have any questions.