replacing an old server

wijcc

wijcc

wijcc

Soldato
Joined
10 Aug 2003
Posts
2,695
Location
London
Hi all, I need tip and advice on the easiest way of replacing an old server. I currently have a 10 year old server running win 2003, it is running AD, a shared network drive, SQL server and a few others programs which users access from the server. I am going to purchase a new server with win server 2012.
What would be the easiest way to replace the old server with the new one without the users being affected or knowing the change? I was planning of giving the new server the same IP and network name as the old one.. so all the shared drives and programs links etc stay the same and I will not have to reconfigure all these on the workstations.

Thanks in advance guys.
 
as its only a single server your best bet is to just re create it all im not sure you can migrate AD from 2003 to 2012.
how many users do you have?
also use tools like group policy to deploy printers and network drives! makes life so much easier.
I cant advise with sql stuff thats out of my reach.
 
to be clear here is this a member server or a DC? you say its running AD but this is often confused.

if its a dingle DC then the process is and will be different and require more steps. I can tell you either but t would be easier to know upfront.

ta
 
Your problem here is that the old server is running AD.

Personally, I'd migrate AD to one server and the services to another. And you should have AD on at least two physical servers anyway.

MS have a guide for migrating AD on Server 2003 to 2012 here.

Note that you cannot migrate SQL 2003 directly to SQL 2014. See here. You'll likely need to do an intermediate upgrade. Note also 32 bit / 64 bit issues.

Putting AD on as separate server will allow you to re-use the old name for the SQL & file server (but I wouldn't). If at all possible, I'd put these on separate, possibly virtualised, servers.

Plan everything very carefully. I'd go in the order:

0. Make 2 backups!
1. AD to new boxes.
2. Copy file services to new box
3. SQL to new box.
4. Decommission old server.

Note that at each stage, if it doesn't work, you can move back.

Do take the opportunity to sort out and rationalise AD groups, file access permissions, etc.

Above all, do your homework, prepare thoroughly, take it slowly, and keep everyone informed.
 
There's a walk through of 2003 to 2012 AD here.

Once the new server is in the domain, I would move the file shares over using a tool like the File Server Migration Toolkit and then update the drive / printer mappings on the clients as needed.
 
if its a single server then its as Quartz says.

you could have course install 2012 as the host OS and just virtualise the 2003 box and leave it running as a guest?.
 
If its a small businesses, having two separate boxes is probably not doable due to costs.

I'd ESXi the box and run a couple of VM's running different tasks.
 
as soon as I read the word if its a small business I suddenly had the thought... this isnt SBS 2003 is it? 2003. Single box. Alarm bells ring.
 
yeap its a small business, running win server 2003 r2... running about 50 workstations and about 80 users. Its a single server which is also the DC. will be replaced by the same.

Cost is an issue i guess.. what benefit would i have getting a separate server just for being the domain controller. It is not running exchange or any other mail server software?

Thanks guys for the tips guys :)
 
Last edited:
wijcc said:
yeap its a small business, running win server 2003 r2... running about 50 workstations and about 80 users. Its a single server which is also the DC. will be replaced by the same.
Click to expand...

If it's a small business then that's very different. Is this SBS 2003 or Server 2003? You'll likely be wanting to migrate to Windows Server 2012 Essential and Microsoft have detailed the process here.
 
Ploppy2k3 said:
if its a single server then its as Quartz says.

you could have course install 2012 as the host OS and just virtualise the 2003 box and leave it running as a guest?.
Click to expand...

The existing install is most likely OEM, there are no virtualization rights.

kitkat9933 said:
If its a small businesses, having two separate boxes is probably not doable due to costs.

I'd ESXi the box and run a couple of VM's running different tasks.
Click to expand...

I imagine the suggestion for two physical boxes was to spread the risk around, virtualizing guests onto one host gives you all of the headaches of a single-box, and all of the added complexity of a virtual environment.

If the existing server is SBS then it will have to keep certain AD roles or it falls out of licensing and shuts down. If it's just Server 2003 (R2?) then leave it running as a second domain controller, but this will prevent you from taking your forest/domain past 2003 functional level.
 
I think you've been dropped in it. SBS 2011 Premium was the last of the line that included SQL Server. Server 2012 Essentials has a 25 user limit that can be unlocked with a Server 2012 key. I'm not sure if this still stands for the R2 versions.

Normally in a SBS migration you can't keep server names, although you can keep the IP by shuffling them around. You can handle mapped drives and printers using Group Policy (although any XP machines may need an update to use the Group Policy Preferences part of Group Policy).
 
no its not SBS, running the server 2003 R2. Would be purchasing win server 2012 most likely as well unless there is a good reason not too. I already have licences for SQL server through one of the programmes that will be running on the server.
 
wijcc said:
no its not SBS, running the server 2003 R2.
Click to expand...

Then I strongly suggest you separate the roles. Think about what will happen if something goes wrong. How much will down-time cost? You can build a domain controller very cheaply, and you have two of them in case one fails.
 
i already have a backup DC which is just a workstation with several large HDDs as it is also used as a secondary backup.
I will update this workstation as well after i do the main server.
 
wijcc said:
i already have a backup DC which is just a workstation with several large HDDs as it is also used as a secondary backup.
I will update this workstation as well after i do the main server.
Click to expand...

I strongly suggest you update neither but migrate to new servers. The problem with updating the servers in situ is that if it all goes wrong you're in real trouble whereas if you migrate to new servers, if it all goes wrong, you just put the old ones back. And after a while the old equipment can be redeployed.
 
You must log in or register to reply here.
Back
Top Bottom