windows2003 -> windows2012 IIS마이그레이션

 

 

 

 

 

iis6.0toiis7.5_migration.pdf

다운로드

 

 

.net framework 버전이 다를 경우 아래와 같이 조치하시면됩니다.

 

ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH

http://www.iis.net/learn/publish/troubleshooting-web-deploy/web-deploy-error-codes

Diagnosis - This can occur if you are doing a web server sync between two machines that have different versions of .Net installed.Resolution - By default, Web Deploy will favor running in the version of .Net that is specified in its configuration file. If the version of .Net that Web Deploy is using on the client is different from the version on the server, we will block a Web Server sync to prevent settings from different versions of .Net from being migrated. To get around this, you have two options:

1. Use the netFxVersion provider setting to tell Web Deploy exactly which .Net settings to migrate. Here is a command line example which forces Web Deploy to sync .Net 2.0 settings:msdeploy.exe -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=destServername
2. Run Web Deploy in the same version of .Net between client and server. On the client side, you can change the ordering of the supportedRuntime version element in the "%programfiles%\IIS\Microsoft Web Deploy V3\msdeploy.exe.config" file for the version of .Net that is specified first (see gacInstall provider for an example of this). This will indicate the version of .Net that will be loaded, assuming it is installed on your system. On the server side, you can do the same for "%programfiles%\IIS\microsoft web deploy\msdepsvc.exe.config". If you modify this file, make sure to restart the Web Deployment Agent Service (net stop msdepsvc & net start msdepsvc).

http://www.iis.net/learn/publish/troubleshooting-web-deploy/web-deploy-error-codes