Replacing a failed 2003 server / websites

I had a Compaq Proliant 800 2003 Server that is basically used as a webserver.  The hardware has failed and I am installing a new Dell 1425SC server in its place.  I have the websites backed up.  What are the steps to replicate the old server on the new and get the websites back up and operational.  I would like to keep the naming conventions / ip info the same on the new server.  Do I need to do anything with the DC (it is a separate server)?

I need to get this  back up and running ASAP.

Any help would be much appreciated.  Thank you
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.


We just had to do this for our intranet server.  If this is serving public web pages, the steps may vary.  Reset the computer account in users and computers.  Join the new computer to the domain as the old computer's name.  This will keep all the old ip address associations (if you were running multiple ip's) in DNS (assuming AD integrated DNS running on your DC).  Setup appropriate ip address(es) on the new server.  Start resetting up your web sites with their former ip associations, and folder/file permissions, as required.  That should be about it.
Any questions, let me know.

Good Luck!
lobarassocAuthor Commented:
Thanks very much for the quick response.  I appreciate the info including the server reset in AD.  I set up the server w/ the same configuration setting and joined it to the domain.  

The server is up and operational.  I copied over the websites data files.  Where do I go from here?  Before the folders had the globe listed as an active website.  Now they just look like normal folders.  I appreciate the help.

Thank you

That depends on your setup.  At the very least, you'll need to reinstall IIS 6 (it's not on by default in 2003 server) or whichever web server you're running.  Reinstall whatever components you require, like asp or  Your default web site will point, by default, to c:\inetpub\wwwroot.  Change as required.  You'll also need to change ntfs permissions, as required.  You'll be using IIS Manager for most of your settings.

If you're running multiple sites, you'll need to set that back up the way you had it, whether that was by host headers, or different ports, or like us, separate ip addresses.  Setup your other web sites as needed and any distinct applications pools, as you need.  Configure each web site to operate on the ip address you previously had it set to.  Set your permissions, as required.  Change your home directory and app pool, as required.  Change your authentication if you don't want anonymous access.  Restrict your number of connections and set your domain/ip restrictions as usage dictates.

That should get you through basic sites.  I recommend giving separate sites their own app pools with multiple worker processes if your server can handle it, so that a failure/memory leak/etc. is less likely to affect other sites.  Get in and tweak those app pools as you have time.  If you have more complex setups, that may require additional configuration.
Exploring SharePoint 2016

Explore SharePoint 2016, the web-based, collaborative platform that integrates with Microsoft Office to provide intranets, secure document management, and collaboration so you can develop your online and offline capabilities.

lobarassocAuthor Commented:
I am recreating the websites pointers on the new server. On the old server, we did not assign individual ip address (they were all unassigned) and on port 80.  What benefit is it to assign an ip to each site?  When setting up the website it asks for host header # (default is none) this doesn't refer to SOA in lookups does it? Also, now that I created the web sites it will not start the other sites since it says they are on the same port - they all were in the past too.

Any ideas? thanks.
The separate ip's is the only thing I ever did, so I can't intelligently discourse on other methods.  It's just what I learned and it suited what I needed.  I used separate sites with separate ip's in order to do the following:

1.  I was able to assign an alias through DNS to provide easy to remember names for each of the primary intranet sites (ie helpdesk.domainname instead of domainname/path/path/someasppage.asp)
2.  I had different permissions requirements for different intranet sites (some I wanted anonymous, some I wanted to have authentication required)
3.  I was able to use separate applications pools for different sites with varying degrees of domain access (some would work with just local rights, some needed domain rights for remote SQL interaction).
4.  I can move web sites around on different servers, but the friendly names remain the same.  I should even be able to do DNS round robin when I get to that point.

Some of this could perhaps be accomplished in other means, such as using the same ip, but with different port numbers.  That just seems to be more difficult than necessary for end users.

How did it work before?  Were all the folders under, say, wwwroot and users just got around by using the paths?  Did the different sites all use the same ip but different port numbers.  Were host headers in use?

I have what I do down pretty good, but if you had a really complex setup, you might have better luck from a full-time webmin.  You might want to consider putting a pointer question to this post in the IIS section:

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
lobarassocAuthor Commented:
I would like to close this question and thank WerewolfTA for all your help.  The new server is installed and the websites are migrated over and we are up and operational.  I did use host header names with a common ip address.

thanks again for all your help
You're welcome.  I'm glad everything's back up and running.
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 2003

From novice to tech pro — start learning today.