Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 772
  • Last Modified:

Replace file server in domain

Should be an easy one. I just have not done it before.
I'm replacing our file server with a new server system. I want to keep the same computer name and IP address. Users are mapping shares using a login batch file directed to the computer share name. I need to have my users log in as normal after replacing the server and have everything work as if the server was not replaced. I'm worried about security permission issues and logins.
What is the best way to handle this?
Thanks
0
wlamore
Asked:
wlamore
3 Solutions
 
Rick HobbsRETIREDCommented:
As long as it is only a File Server and not an AD controller, DNS, or DHCP, bring it online with a new, static IP address and a different name,  Copy all the data over.  Take the old server offline or rename.  Rename new server to desired name,  You should be in business.
0
 
EricIT ManagerCommented:
I would just get it ready with a different name.
backup the data on old take offline, restore it to new, rename, give same iP.
YOu could look into DFS and never worry about it again.
all you mapapings would be
\\domain.com\sharename
and you tell the dfs host where it is. YOu can change it on the fly.
 
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You CAN keep the same name using procedures as described above.  However, why?  Your reasons aren't really valid.  If your users map the drives with a logon script, then change the script.  Done.  If they don't, then you should get them mapping drives this way. It's a lot faster doing a find/replace than swapping names (not that it's a time intensive task otherwise, but if it takes 15 seconds to do a find replace, it'll probably take 2-3 minutes to swap names... so, strictly speaking, modifying the script will be 8-12 times faster.

As for the process of copying the data, there are several options - XCOPY, ROBOCOPY, SCOPY will all do it from the command line and, using the appropriate switches (type <command /?> for more information on the switches), preserve the security information.  But I would really suggest you do this using your backups.  Doing this with your backups wil help ensure your backups are good, give you EXPERIENCE restoring a server's data from them, and if there turns out to be a problem, it's no big deal - you've always got the old server WORKING and can investigate why the backups weren't.  FYI, you would restore your last full backup to the new machine (just of the data, not the OS) and then, when you are ready to make the final switch, do a differential backup (assuming you don't use incremental backups) and then restore that differential to your new server.  That's the fastest way to be able to switch servers while providing the least interruption to users short of using something like DFS.
0
 
wlamoreAuthor Commented:
Thanks,
 All valid points and solutions. There are internal reasons for our naming renaming the same, the backup restore is a great test, and I'll look more into DFS for future use.
Thanks All
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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