IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved [Answered]RSS

6 replies

Last post Jan 02, 2014 04:39 PM by chrisjonesaz

  • IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    Aug 02, 2013 05:36 PM|VictoriaMnfd|LINK

    Hi there!

    Here is our situation:

    1. We need to move one site with a big amount of data (10 Gb) from IIS 6 (Windows Server 2003 named W2003) to IIS 8 (Windows Server 2012 named W2012). W2003 and W2012 are located in 2 different forests. There is no trust between the forests.
    2. We installed Web Deployment Tool: version 2 on W2003 and version 3 on W2012.
    3. We tried packaging all sites which reside on W2003, but after about 10 hours of packaging the command failed with the error regarding insufficient space. There are 85 GB of space available though. The same command with "-whatif" finished successfully. Here is the command:
      C:\Program Files\IIS\Microsoft Web Deploy V2>msdeploy -verb:sync -source:metakey=lm/w3svc -dest:package=c:\Temp\IIS6.zip,encryptPassword="P4ssword" > "c:\Temp\LM w3svc Package Report.txt"
    4. We followed http://www.aip.im/2012/02/how-to-migrate-multiple-sites-from-iis-6-to-iis-7/
      1. On W2008 we ran:
        msdeploy -verb:sync -source:metakey=lm/w3svc -disableLink:contentExtension -dest:package=C:\Temp\Sites.zip,encryptPassword=P4ssword > C:\Temp\WebDeploySource.log
      2. On W2012 we simulated the sites import and received the following error:
        C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy.exe -verb:sync -source:package=c:\Temp\Sites.zip,encryptPassword=P4ssword -disableLink:contentExtension -dest:metakey=lm/w3svc -whatif > C:\temp\WebDeployWhatIf.log
        Error Code: ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH
        More Information: The versions of the .NET Framework Configuration Provider (rootWebConfig32) are different on the source (2.0.50727.3623) and destination (4.0).  Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH.
      3. On W2012 we followed the referenced article and run the following commend (Solution Option #1)
        C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy -verb:sync -source:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2 -dest:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2,computername=W2012

        It executed without error, but made no changes:
        Total changes: 0 (0 added, 0 deleted, 0 updated, 0 parameters changed, 0 bytes copied)
      4. When we executed step 4.2 we still received error ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH.

    Questions:

    1. What would be the best way to migrate required site from W2003 to W2012? And would you be so kind to outline the migration steps?
    2. How to find out which site to package?
    3. How to package only specific site from several sites which are running on IIS 6.0?

    Thank you very much for your time and attention in advance!

    msdeploy migration iis iis8 iis6

  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    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?

    http://support.microsoft.com/kb/2734782

    Lex Li
    IIS Consulting Services at https://support.lextudio.com/services/consulting.html
    ---------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    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!

    Cheers!

  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    Aug 06, 2013 09:24 AM|Angie xu - MSFT|LINK

    Hi VictoriaMnfd

    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,

    Regards

     

    Angie xu

    MSDN Community Support
    Please remember to "Mark as Answer" the responses that resolved your issue.
  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    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

  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    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: http://www.hoststools.com/index.php/order/

    Terri Morton
    ASP.NET/IIS.NET Website Manager, Neudesic
  • Re: IIS6 to IIS8 Site Migration Failed - How To Migrate IIS6 Site - Unresolved

    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