Migrate file server to a different named server

That should not be a problem. I assume the new machine will not be an additional domain controller? the best way to copy the data from one machine to the other would be to back-up the data with Windows backup and then restore it to the other machine. This will preserve all permissions.

You can copy data and preserve NTFS permissions with XCOPY and ROBOCOPY but these do not deal with share permissions and cannot cope with open files.

There is nothing to stop you copying the data and them renaming the servers.

That is all really good advice thanks.

I did have a question regarding a DFS server. I am tryingt to avoid going to every users PC and remap drives, and there are many programs that reference UNC paths on this server. I did find the Microsoft File Server Migration Toolkit. Has anyone used this before, did it work?

Some additional information. I am told there are a few programs and links pertaining to this file server that are quite difficult to change. We would really like to use a new server name and have the old UNC paths point to the new locations.

What I am reading on Microsoft's File Server Migration Toolkit seems to be helpful and usefu, has anyone tried it?
If not, then what would be the best method for using a new server name without having to change login scripts or programs? If I were to use the tool kit then i see the steps looking something like the following:
1. Backup server A (using Microsoft backup)
2. Configure DFS root server on Server B
3. Stop sharing on Server A
4. Restore files and shares from backup tape

Why not create a login script that automatically maps drives when the client logs on.

Say mapped drive F points to your HR folder or whatever.  When you change servers all you need to do is update the login script.

Fig 1
@Echo Off

REM **** Map Network Drives
net use u: \\Servername\users
net use s: \\Servername\shared
net use m: \\Servername\mis
net use q: \\Servername\acctg
net use x: \\Servername\hr

And change programs and links. I was hoping to avoid having to go in and change all programs that reference the server UNC name..

Th problem with DFS from what I have read is that it changes the name say from \\server1\share to domainname-DFSnamespace\share so if you set up DFS you will still have the issue with your existing programs.

There are articles on how to bring the new machine online and let all active directory update then bring the old machine down and change the name.
You could also do backups of the old machine bring it down, bring the new machine up with the same name and then do a restore of all the old data.  

Hmmm... that would be a little problematic.  To make that work you would need to do a "one-shot" migration of data from the old server to the new server, down the old server (permanently) and then edit your AD DNS to point the "old server" DNS name to the new server's IP address.  That would, in essence, keep your UNC references relevant and functional without having to edit them...  Definately test this before implementing, though...

Our initial plan was to do just as Scooter said, but it seemed rather risky. We are a little worried about losing some of the share and permissions and object authorities if we encounter any problems. I know the backup is supposed to save that information, but once we take the old server off the domian we can no longer refernce that server tor file share and permission information.

I was under the impression DFS was designed so that you can replace a server or consolidate many servers onto one and it will have no affect on users and there is no need to re-do drive mappings. I am not familiar with DFS and am trying to read up on it as much as I can. If we really do have to redo log in scripts and change the path all the users go to access their data than DFS does not help me in the slightest. If that is the case than I don't really see the point in utilizing DFS at all to be honest.