Windows 2003 to 2012 -- keeping same server IP & name ?

I am going to replace my 2003 server
which does DNS, FileServer, etc functions
with a 2012 server over a weekend
and want to keep the same
  1. server IP address
  2. server name
  3. server share names

I assume this is easily doable since
the below links talk about it, after
everything has been replicated I would
change the IP/name of the OLD machine
to "nameOLD/IPsomethingElse" and change
the IP/name of the NEW machine from
"nameNEW/IPNEW" to "nameOriginal/IPOriginal" ?
  ** If not, what do you recommend ?

http://community.spiceworks.com/how_to/75097-replace-an-old-file-server-with-a-new-file-server-using-the-same-ip-same-name-same-shares

https://blog.workinghardinit.work/2011/02/07/keeping-the-same-server-name-ip-address-when-moving-a-domain-controller-dns-dhcp-wins-server-to-new-hardware
finance_teacherAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

ptsolutionsCommented:
This sounds like you're asking for a lot of trouble. What reasons do you have to want to stay? I've done a 2003 > 2012 multiple times and it is super easy and painless. It seems a lot more painful to do it the way you want to.
finance_teacherAuthor Commented:
I have about 50+ static IP servers, clients, Cisco switches, printers, etc that all use my current Windows 2003 IP address as their primary DNS server and \\servername\share as lots of their fileserver shortcuts.

What do you recommend when dealing with that if you do NOT recommend keeping the same servername and IP address when migrating from a Windows 2003 32 bit machine to a Windows 2012 64 bit machine ?
Dirk MareSystems Engineer (Acting IT Manager)Commented:
I don't see any problems with what you suggested.

I assume this is easily doable since
the below links talk about it, after
everything has been replicated I would
change the IP/name of the OLD machine
to "nameOLD/IPsomethingElse" and change
the IP/name of the NEW machine from
"nameNEW/IPNEW" to "nameOriginal/IPOriginal" ?
  ** If not, what do you recommend ?

To get your shares across note down the drive letter on source server
export shares registry on old 2003 server
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares]
Join new server to domain with different temp name

Use robocopy to copy data on new server
robocopy <source share> ,destination share> /e /zb /copyall /mir /secfix /sec

Open in new window


Robocopy will mirror files and folders on source to destination with NTFS security
Run robocopy a couple of times to ensure you have all the data
Ensure that source and destination drive letters remain same
shutdown the old server
Delete temp computer account in AD
Rename temp server to match old server hostname and IP and Join to domain
import registry on new server, this will create share folders as it was.

DirkMare

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
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.