IIS 7 and Above
IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unres...
Last post Jan 02, 2014 04:39 PM by chrisjonesaz
Aug 02, 2013 05:36 PM|VictoriaMnfd|LINK
Here is our situation:
Thank you very much for your time and attention in advance!
Aug 03, 2013 01:08 AM|lextm|LINK
Windows Server 2012 does not have .NET Framework 3.5 installed. Can you enable that first and then try again?
Aug 05, 2013 09:18 AM|VictoriaMnfd|LINK
Thank you for your time and attention, Lextm!
We installed .NET 3.5 SP1 which included .NET v.2 and v.3 as a part of the initial Windows 2012 preparation. Also on W2012 we enabled all IIS components which were enabled on W2008.
Any other ideas would be highly appreciated!
Aug 06, 2013 09:24 AM|Angie xu - MSFT|LINK
A Migration tool is avaiable on IIS download site - IIS Easy Migration Tool
(IEMT), you can also have a try,
The IIS Easy Migration Tool (IEMT) is a new generation of the IIS Sites Transfer tool. The IEMT helps to migrate web sites from Microsoft Internet Information Server version 6 (IIS 6.0) to IIS 7.5, IIS 7.0, IIS 8.0 or another IIS 6.0 server. It also helps
to transfer Windows users from one server to another and copy FTP logins, virtual directories, application pools, SSL certificates, Web/FTP folders structure and assign NTFS folders permissions,
hope it helps you,
Dec 17, 2013 04:40 PM|KUYJKTV UFTVIURUYGVUYK|LINK
IIS Easy Migration Tool (IEMT), is a licensed application do not use it
You will install it and start using it just to find out you cannot do what you want to becauser the WONDERFUL ppl at MS want to steal more of you money
Jan 02, 2014 02:57 PM|tmorton|LINK
IIS Easy Migration Tool (IEMT) is not a Microsoft product. It was developed by, and is supported by, a third party (Hosts Tools). The listing in the Community-Contributed Downloads area of the IIS.NET site (http://www.iis.net/downloads/community/2013/04/iis-easy-migration-tool-(iemt))
clearly lists that it's "free to try". The HostsTools.com website lists the full license fee:
Jan 02, 2014 04:39 PM|chrisjonesaz|LINK
My advice would be to use appcmd to export the site and app pools to an xml file, import them in your newer servers and validate the settings, then copy code over as you would normally when moving data between servers/shares. In IIS 6 you can export the
site settings, in IIS7 you would use appcmd
To Export the Application Pools on IIS 7 : %windir%\system32\inetsrv\appcmd list apppool /config /xml > c:\apppools.xml
To import the Application Pools: %windir%\system32\inetsrv\appcmd add apppool /in < c:\apppools.xml
To Export all you’re website: %windir%\system32\inetsrv\appcmd list site /config /xml > c:\sites.xml
To Import the website: %windir%\system32\inetsrv\appcmd add site /in < c:\sites.xml
To export/import a single application pool: %windir%\system32\inetsrv\appcmd list apppool “MyAppPool” /config /xml > c:\myapppool.xml
Import: %windir%\system32\inetsrv\appcmd add apppool /in < c:\myapppool.xml
To export/import a single website: %windir%\system32\inetsrv\appcmd list site “MyWebsite” /config /xml > c:\mywebsite.xml
Import: %windir%\system32\inetsrv\appcmd add site /in < c:\mywebsite.xml