• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 233
  • Last Modified:

Steps to transfer file server to new machine and OS

I have an old Dell PowerVault 775N running Win Server 2003 Standard being used as a fileserver. I would like to move all files and data to a new Dell PowerVault NX3000 running Win Storage Server 2008 Standard, and take the 775N offline. What would be the steps and procedures involved in making this transition? I don't want to miss anything.
 I'm running DHCP, DNS, and WINS on Win Server 2003 Standard on two Dell Dimension 8200 PCs concurrently with different address scopes for DHCP.
Thanks for any help.
0
Ryan Moore
Asked:
Ryan Moore
2 Solutions
 
greedjCommented:
If you do not wish to reinstall Windows, here is an advanced method I would use.

On the new machine, Install a new copy of Windows 2003 picking the same x32 or x64 version on the old server (You will erase this copy).

In device manager, write down the scsi controller Hardware ID and the name of the driver file.
The hardware id looks something like this PCI\VEN_8086&DEV_2822&SUBSYS_514D8086&REV_02 (all the numbers will be different from this example)

Copy the driver file to a USB pen (It is stored in C:\Windows\System32\Drivers)
In Regedit:
export HKLM\System\CurrentControlSet\Services\NameOfDriver to USB
export HKLM\System\CurrentControlSet\Control\CriticalDeviceDatabase\Hardware ID to USB

On the old server, in device manager, check to see that the driver file name is NOT the same between servers. If it is, the risk of issues becomes high and you should stop and use another method (Unless you know how to undo the changes).

Copy the driver file to C:\Windows\System32\Drivers from USB
Import the 2 registry keys.

You have now installed the disk controller driver for the new server onto the old.

Image the server from old to new using BartPE or whatever you use for imaging.

This clone method works on 2000, XP, 2003, Vista, 2008 and Windows 7. It prevents the dreaded STOP 0x0000007B when imaging to new hardware.


0
 
Darius GhassemCommented:
What I would do is just migrate the data over to the server.

Richcopy and Robocopy are great file migration tools.

ViceVersa cost a little money but works very well. You get 30 days free as well.
0
 
greedjCommented:
Robocopy works well but if you have shortcuts, databases, or file save history on the clients, it will break.
0
How to change the world, one degree at a time.

By embracing technology, we can solve even the biggest problems—including the gender gap.  By earning a degree from WGU, you have an opportunity to gain the knowledge, credentials, and experience it takes to thrive in today’s high-growth IT industry.

 
SandeshdubeyCommented:
Use tool ROBOCUPYGUI.EXE and copy/move the shared folders to the new server again as this tool will keep the existing permissions structure of the folders.

Also make sure if any group policy is define like folder redirection of roamin profile or mapping of drive you need to change the path to new server.
0
 
greedjCommented:
It keeps permissions but the server name will be different. So Access DB, file history, etc will be broken.
0
 
Ryan MooreAuthor Commented:
How would you fix broken database, etc. after migrate? Could you take original server offline and rename new server with old name?
0
 
Darius GhassemCommented:
You can rename the server and change IP address to the old server's.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now