How to Migrate from IIS 6 to IIS 7

 

Why Need to Migrate to IIS 7?

Here are some of the main reason why need to migrate our current web application from IIS 6 to IIS 7.
1) IIS7 is much more flexible and customizable than before.
2) We save loads of time by automating more tasks with the interface.
3) You can manage whole Web farms from one place.
4) IIS7 is faster and more efficient than any other version of IIS.
5) IIS7 makes it easy to publish content securely over FTP/SSL

Process of Migration to IIS 7

Part 1 – View dependencies of the source

1. Get the dependencies of the web site by running the following command:

msdeploy -verb:getDependencies -source:metakey=lm/w3svc/1

2. Review the output of the dependencies and look for any script maps or installed components in use by the site. For example, if Windows Authentication is in use by the web site, you will see .

3. If your site is inheriting any script maps, these will not be listed in the dependencies and you should also review the script maps for your site manually.

4. Compile a list of the components needed on the destination.

Part 2 – Configure the target or destination machine

1. Review the list of dependencies and install them on the destination server.

For example, let’s assume you had the following in use for your web site:

• ASP.NET

• Windows Authentication

• Anonymous Authentication

Based on analyzing your dependencies, you would install those components and modules.

Part 3 – To migrate the site to the source server

1. Always make a backup of the destination server. Even if you are just testing, it allows you to easily restore the state of your server. Run the following command to backup an IIS 7.0 server:

%windir%\system32\inetsrv\appcmd add backup “PreMsDeploy”

2. Run the following command on the destination server to take an archive of the server for migration:

msdeploy -verb:sync -source:metakey=lm/w3svc/1 -dest:archivedir=c:\site1archive

3. Run the following command on the destination server to validate what would happen if a migrate was run:

msdeploy -verb:migrate -source:archivedir=c:\site1archive -dest:metakey=lm/w3svc/1 -whatif > msdeploymigrate.log

Note: If you don’t wish to sync from an archive, you can sync using the remote service. Specify computerName with the name of your server, such as Server1. If you are not running on the default port and URL, you need to specify the full URL, such as http://Server1:8080/msdeploy. For example, change the source to
source:metakey=lm/w3svc/1,computerName=server1

4. After verifying the output, run the same command again without the whatif flag:

msdeploy -verb:migrate -source:archivedir=c:\site1archive -dest:metakey=lm/w3svc/1 -whatif > msdeploymigrate.log

Note: If you don’t wish to sync from an archive, you can sync using the remote service. Specify computerName with the name of your server, such as Server1. If you are not running on the default port and URL, you need to specify the full URL, such as http://Server1:8080/msdeploy. For example, change the dest to

dest:metakey=lm/w3svc/1,computerName=server1

You are now done migrating your site. To verify, test browsing to the web site on the destination server.
(Source: Official IIS blog at http://blogs.iis.net/bills/archive/2008/06/18/how-to-migrate-from-iis-6-to-iis-7.aspx)

Looking for IIS 7 compatible web hosting provider? Look no further! Check up SeekDotNet.com – one of the leading ASP.NET hosting provider with the hosting plan hosted at Windows server 2008 with latest ASP.NET 3.5 and IIS 7 technologies.
Contact SeekDotNet.com at http://www.seekdotnet.com/contactus.aspx on how to obtain your 3 months free IIS 7 hosting plan now.