Moving an Array to a New Server 2012

I have been tasked to install a new file server with Microsoft Server 2012 installed to replace an existing server 2003 machine which is the current file server.  Both servers are member servers.  The existing server also has few other applications installed like door entry and camera software etc.  It also has an HP MSA70 SAS Enclosure with P800 Smart Array Controller which I will need to move across to the new machine and re-create the security and file shares as they were on the old server.  My plan is to rename the old server to something completely different and then rename the new server to the old servers name so that to the end users it will appear to be the same server as regards to \\servername\shares\ mapped drives etc.

Can someone give me guidance as to how to achieve this as seamlessly as possible.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Interesting question ! i opt in to see a solution.
Since you move the raidset i assume you only have to re-annouce the shares to the new server and edit local users/groups-rights but i am not 100% sure....
Daniel HelgenbergerCommented:
I would not recommend renaming servers, there may happen some very unpleasant and unexpected things, I had this quite often.

I do not know if this is still possible in your setup, but the most seamless way I know about are DFS replicated folders, there will be no downtime at all. This means you have to change the mount points first however to something like:

The way to do this would involve the following steps:
1. Setup the new Server with the new storage
2. domain join it
3. install the File Server and DFS role
4. and recreate every share needed, install all software.
5. test it.

Now, create DFS namespaces and replication folders:
1. In DFS, create a new name space and Folders for all the shares needed.
2. Then add folder targets to the DFS folders, both servers with its shares each. Eg, if you have a share 'security' on both servers, then add a DFS folder named 'security' and set both server's 'security' share as targets.
3. The DFS wizard will prompt you to setup replicated folders. Do as it says. Just make sure you choose as your old server as master to be replicated from. Be careful here! If choosing the wrong one, your old share will be emptied (though not permanently).
4. Wait until the replication is done, depends on the stuff to be replicated.

The switch
1. If everything is replicated, change your GPOs to point to the DFS folder instead of directly to the old file server.
2. Wait until everything is propagated and set the rest manually.
3. If everything works, disable the old server's folder target in DFS.
4. If nobody complains after a few days switch off the old server, remove it's DFS targets and disable the replication groups.

I think your best and fastest way to do this as I understand you don't want to use another space or copy of your data if you already have it on a "portable" device (HP SAS).

here is what I will do:

Have the new server out of the Domain, regardless the name.
Write down all the shares of the old server, permissions, etc.
Remove the actual server (2003) from the domain.
Install the SAS on the new 2012  and make sure it is working and you can access it on the server.
Join the 2012 to the domain using the old name.
Recreate all shares, permissions, etc.
Test access from a client.

Also, you can try just taking the SAS to the new server, recreate shares and everything and add a GPO rule to all the machines to kill the previous share name and use the new one, this will work fine if you have already a GPO to create a "Mapped Drive" at login.  With this option though all user will have to logout and login again. With the previous one, if done correctly they will have time down but as soon the share is up they will have access to it without having to login back again.

Good Luck!
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

jongrewAuthor Commented:
I'm weighing up the answers that have been posted...
jongrewAuthor Commented:
I have completed this task much as I originally said by moving the array with NTFS permissions intact and exporting the shares registry key and renaming the server

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jongrewAuthor Commented:
My solution was the easiest and most simple solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.