title: Ignore application pool when migrating from IIS 6 to IIS 7.5 with MSDeploy
body: <p>I am currently migrating my websites from a Windows Server 2003 (<strong>SourceServer</strong>) with IIS 6 to a Windows Server 2008 R2 (<strong>DestServer</strong>)with IIS 7.5.</p>
  
  <p>I use the <strong>MSDeploy</strong> tool to perform the operation. After checking the dependencies (just <em>Windows Authentication</em>, already installed in <strong>DestServer</strong>), I create the package in the <strong>SourceServer</strong>: </p>
  
  <blockquote>
    <p>msdeploy -verb:sync -source:metakey=lm/w3svc/5
    -dest:package=c:\Site5.zip > WebDeployPackage.log</p>
  </blockquote>
  
  <p>And I copy it in the <strong>DestServer</strong>. From the <strong>DestServer</strong> I test the deployment by using:</p>
  
  <blockquote>
    <p>msdeploy -verb:sync -source:package=c:\Site5.zip
    -dest:metakey=lm/w3svc/5 -whatif > WebDeploySync.log</p>
  </blockquote>
  
  <p>But it gives me an error related to the <strong>missing application pool</strong>. Indeed one of my goals was to tide up the websites, since in the <strong>SourceServer</strong> the person who was responsible for the deployment made quite a mess with naming conventions (both for pools and sites), assigned too many applications (even 10) in a single application pool and so on.</p>
  
  <p>Therefore my goal was to run the site in a dedicated brand new application pool in the <strong>DestServer</strong>. But if MSDeploy does not find in the <strong>DestServer</strong> the application pool with the same very name of the <strong>SourceServer</strong> it does not deploy the package on the <strong>DestServer</strong>.</p>
  
  <p>I also tried to use the command <code>-enableLink: AppPoolExtension</code> in MSDeploy in both creation and deployment of the package to get also the Application Pool. The package then installs correctly but, I do not know why, it gives errors in the config file. For instance I cannot enable any kind of Authentication module.</p>
  
  <p>Is there any way to let the MSDeploy ignore the application pool when deploying?</p>