What's the fastest and most efficient way of porting over an IIS setup on one machine to a blank IIS 7 install on another?
Including all the sites, applications, virtual directorys, ftp accounts, etc?
Thanks.
+1
A:
You can use this tool http://www.iis.net/extensions/WebDeploymentTool (it can even migrate between IIS6 and 7)
Alternatively you can do it manually:
http://iterat.ive.ly/index.php/2009/06/10/howto-export-iis7-configuration-to-another-webserver/
DmitryK
2009-09-07 22:22:58
I like option 2 better. It seems more in line with the Microsoft-prescribed approach.
Jason R. Coombs
2009-09-07 22:30:30
unfortunately copying the applicationHost config file results in 503 errors across otherwise working sites (even static html), and kills the app pool. This seems to be a common problem
Scott
2009-09-08 03:37:39
Please use this document to troubleshoot 503 errors.http://mvolo.com/blogs/serverside/archive/2006/10/19/Where-did-my-IIS7-server-go_3F00_-Troubleshooting-_2200_service-unavailable_2200_-errors.aspx
DmitryK
2009-09-08 03:47:05
+1
A:
The Applicationhost.config xml file (%systemRoot%\system32\inetsrv\config\ApplicationHost.config) is the main configuration file of IIS 7.0, this configuration file contains all the information about sites, virtual directories, applications, application pools and global settings for the web server.
You can copy this file to the target server, or you may just be able to point both servers at the same file using symlinks, if they both have access to a shared filesystem.
i.e.
cmd /c mklink %systemRoot%\system32\inetsrv\config\ApplicationHost.config \server\share\config\ApplicationHost.common.config
I haven't done this, but voices on the web seem to indicate this is possible.
Also, if you want more control, consider using Appcmd.
Jason R. Coombs
2009-09-07 22:27:58