Replacing a Windows File Server

Posted by Keltari on Super User See other posts from Super User or by Keltari
Published on 2013-07-02T15:33:37Z Indexed on 2013/07/02 17:07 UTC
Read the original article Hit count: 272

Filed under:
|
|

We have a Windows file server that needs to be replaced. Unfortunately, there are to many custom build applications, shares, and random things that rely on the existence of that file server to just stand up a new one, so we need to make the transition as seamless as possible. We decided to copy the contents of the old server to the new and then rename the new one with the same name. I have made a list of everything I need to do. Am I missing anything?

  • The new file server is up and running
  • I copied the directories of the old file server to the new one
  • I set up all the shares/permissions for those directories in advance
  • Copy the contents from oldserver to newserver

robocopy \vash\d$\nasshare\ \vash2\l$\originalvash\nasshare\ /E /ZB /copyall /dcopy:T /FP /x /v /fp /np /mt:8 /eta /log:robocopy.log /tee

  • Rename and reIP oldserver to something else (need it available if something is missing)
  • Rename and reIP newserver to oldserver

Obviously, I need to test if shares are working properly.

Are there any steps im missing?

© Super User or respective owner

Related posts about Windows

Related posts about file-transfer