We're looking to replace our current file server with a new file server with more space and newer hardware. Here is our plan: 1. Copy all files to the new file server. 2. Remove the old file server from the domain, rename the new file server with the old file server's name, and change the IP address to the old file server's IP. We are doing this, because we don't want to change our login scripts, drive mappings, GPOs, programs, etc which are all pointed at the old file server name. Any suggestions/objections? What have you all done in this situation?

What will you do in your plan to migrate the login scripts, drive mappings, GPOs, programs, ACL's from old server to new server? Best is use the File Server Migration Toolkit http://www.microsoft.com/windowsserver2008/en/us/fsmt.aspx This utility will reduce your downtime considerably and help you auto migrate all the settings like a breeze - thestriver

The login scripts, drive mappings, GPOs, programs, ACLs, etc were already copied to the new file server. Since we're renaming the new file server with the old file server's name, we believe everything will function correctly. Is that a wrong assumption?

That should be fine. Here is a similar thread: How to replace old server with new server with same computer name and IP address? http://social.technet.microsoft.com/Forums/en/winserverMigration/thread/f18c3d9e-4db8-45e1-8426-ad11d538c6a3Shaon Shan| TechNet Subscriber Support in forum| If you have any feedback on our support, please contact tngfb@microsoft.com

GPO's , ACL's , Programs are not tied with hardware which is disk. make sure you also count the persistent connections if any to the disk. But important - TEST , TEST and TEST before implementing in production.

Okay, sounds like our plan is good to go. Thanks for the replies.

Okay, sounds like our plan is good to go. Thanks for the replies. Unfortunately we don't have a test domain environment.

Okay, sounds like our plan is good to go. Thanks for the replies. Unfortunately we don't have a test domain environment. Any other suggestions would be welcome.

Okay, sounds like our plan is good to go. Unfortunately we don't have a test domain environment. I have one more question. How long should we wait after removing the original file server before renaming the new file server with the original name and IP?

Okay, sounds like our plan is good to go. Unfortunately we don't have a test domain environment. Thanks for the replies.