moving iis application/database to another server


Client has a windows 2003 server they want to move to a windows 2012 r2 system.

I know it's a custom application and has a database (running on IIS) and "Classic ASP".  I've been tasked with moving everything from the old system to the new system.  

I can back up and restore the database, and I can install IIS on the new system with classic ASP, but what's involved with copying the custom application to the new server, and registering third party components with the new operating system?  and then changing the connection string?  Anything else you think would be required?

This is supposedly a very straightforward deal, but I've never done it before.  Would appreciate any help, suggestions, or tutorials.

Who is Participating?

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

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.

Dan McFaddenSystems EngineerCommented:
The process is relatively straight forward.  If the IIS feature is installed and the necessary extra features (Classic ASP) then it should be something like the following:

** some config under Server 2003 & IIS6, does not translate to Server 2012 R2 & IIS8.5.

At the start, both servers are online.

1. verify all DNS entries relative to this site
2. verify content structure on old server (paths and/or ACLs)
3. document the IIS AppPool config on the old server.
4. document the IIS web site config on the old server.
5. fully patch new server OS
6. install database engine (what is it?  MSSQL, SQL Express, MySQL, ...)
7. move database to new server
8. verify db connectivity and data access
9. create directory for website on new server
10. copy content over the website structure to the new server
11. verify all files and directories have been moved.
12. setup a new AppPool on the new server, take the defaults.
13. setup a new website on the new server.
13a.  update the web.config or connection strings if needed
14. verify the site can be accessed remotely
14a.   the verification process most likely will take more time since you'll have to check all the sites functionality.
15. if the site's functionality tests as expected, the site is migrated

At this point, you have 2 choices to switch the traffic to the new server.
A. move the old IP address to the new server
B. use a new IP address for the website, update DNS records to reflect new IP
   b1. leave both servers online
   b2. update DNS record with new IP
   b3.  traffic will move to the new server as DNS updates propagate thru the global DNS system

I'm conservative, so I would recommend waiting 2 to 4  day or so to decommission the old server.  You can verify the website's activity by checking your http logs on both the servers.  When there are no more requests hitting the old server, I would disable the NIC on the old server then wait 2 more days before shutting down the server.  

First option is the fastest since you will not have to update DNS records.  This is easy if the new server is on the same subnet as the old server.  

The second option makes a clean break from your old infrastructure.  If the new server exists on a different network or in a new facility, this is your option.

There are also tools to perform this, but I haven't had a lot of success with them.  I've frequently run into small issues here and there.

Here is a link to a tool specifically built for a migration:



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
Loganathan NatarajanLAMP DeveloperCommented:
Anything else you think would be required?

What you had specified steps are correct and this is the way I used to do my classic asp app. And you need to test it with any firewall blocking those components
Mystical_IceAuthor Commented:
So one is running IIS6 the other (new server) is running IIS 8.

I copied the files over to the sites, but to be honest i'm not sure where to go from here.  

Got the bindings set, but don't know how to find out where the connection to the database is even.
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

From novice to tech pro — start learning today.