Everything about migrating with the WebDeploy 2.0 tool from Windows Server IIS 6 and IIS 7 environments
Web ImplementationWeb Deployment Toolsimplifies the migration, management, and deployment of IIS web servers, web applications, and websites. Administrators can use command-line scripting with Web Deploy to synchronize IIS 6.0 and IIS 7.0 to migrate servers or an IIS 6.0 server to IIS 7.0. Web Deploy tools also allow administrators and delegated users to use IIS Manager to deploy ASP.NET and PHP applications to an IIS 7.0 server.Learn all about migration with the WebDeploy 2.0 tool!
All about migration with the WebDeploy 2.0 tool web applications between IIS 6.0 and IIS 7.0 with ease
Simplify your IIS 6.0 to IIS 7.0 migrations by determining incompatibilities and previewing proposed changes before you begin the process. Learning about potential issues beforehand gives you the opportunity to take corrective action and simplifies migration with the Web Deploy 2.0 tool.
Synchronize the server farm efficiently
Allows efficient synchronization of sites, applications, or servers across an IIS 7.0 server farm by detecting differences between source and destination content and transferring only the changes that need synchronization. The tool simplifies the synchronization process by automatically determining the configuration, content, and certificates to be synchronized for a specific site. In addition to the default behavior, you still have the option of specifying additional providers for synchronization, including databases, COM objects, GAC assemblies, and registry settings.
Archive package, and deploy web applications with greater ease
Allows packaging of Web application configuration and installed content, including databases, and using these packages for storage or redistribution. These packages can be deployed using IIS Manager without requiring administrative privileges. The tool integrates with Visual Studio 2010 to help developers simplify Web application deployment to the Web server. The tool also integrates with the Web Platform Installer, allowing simple and easy installation of Web applications from the Community. You can submit your own application to the Web Application Gallery – learn.
Features
- Seamless integration with IIS 7.0 Manager and the Visual Studio 2010 interface to create packages and deploy them to a machine, both locally and remotely.
- The perfect integration with the Web platform installer to easily install Community web applications.
- Application Packaging Website
- Package a web application or entire site, including associated databases.
- ACL, COM, GAC package capacity, and Registry configuration.
- Supports both live servers and compressed packages as source or destination.
- Web Application Implementation
- Administrative privileges are not necessary to implement web applications.
- Possibility of adding powerful parameters to change text in files when deployed (e.g., prompts to replace a connection string when deploying from QA to staging environments).
- Integration with IIS 7.0 Web Service Management (WMSVC) for remote deployment by non-administrators.
- Server administrators have granular control over operations that can be performed and can delegate tasks to non-administrators.
- Server Migration and Synchronization Website
- Synchronize or migrate the entire web server, a website, or application.
- Sync only changed data.
- Detect missing dependencies during synchronization.
- Automatically collects content, IIS configuration, SSL certificates, and ASP.NET settings when synchronizing a website.
- In addition to IIS Manager and Visual Studio 10, tasks can be performed using the command line or the public API.
What kind of migrations can be achieved with the Web Deployment Tool?
- One or 1,000 IIS 6.0 to IIS 7 websites, including all configuration options, content, and certificates
- Migrating a single application with Web Deploy 2.0
- Full server (all websites, application pools, etc.) from IIS 6.0 to IIS 7
- Custom manifest composed of sites, application groups, assemblies, COM objects, registry keys, content, and much more from IIS 6.0 to IIS 7
Prerequisites
This guide requires the following:
- .NET Framework 2.0 Service Pack 1 or higher
- Web 1.1 Tools Implementation
Note: If you have not installed the Web Deploy tool, see Installing Web Deploy.
Part 1 – View Your Site’s Dependencies
- Get web page dependencies by running the following command: msdeploy -verb:getDependencies -source:metakey=lm/w3svc/1
- Review the output of dependencies and look for script maps or components that are in use by the site. For example, if Windows authentication is in use by the website, you may see
- If the site inherits dash maps, they will not appear in dependencies and you must also review the script maps for your site manually.
- Compile a list of the necessary components at the destination.
For detailed instructions on analyzing the output of getDependencies, see Viewing Dependencies.
Part 2 – Configure the target server, to which we will migrate everything
Check the list of dependencies and install them on the target server.
For example, suppose you said the following on your website:
ASP.NET
• Windows and anonymous authentication
Based on this dependency analysis, you must install the corresponding components and modules.
Part 3 – Migrating Your Site to the Destinations Using a Package File
- Always back up the target server. Even if you’re just running a test, this will allow you to easily restore the server’s state. % Windir% \ system32 \ inetsrv \ appcmd add backup «PreWebDeploy»
- Execute the following command on the source server to create a package (compressed) of the server files: msdeploy -verb:sync -source:metakey=lm/w3svc/1 -dest:package=c:\Site1.zip > WebDeployPackage.log
- Copy the package file to the target server.
- Run the following command on the target server to validate what would happen if a sync operation runs: MSDeploy -verb:sync -source:package='c:\Site1.zip' -dest:metakey=LM/W3SVC/1 -whatif > WebDeploySync.log
- After verifying the output, run the same command again without the WhatIf flag: msdeploy -verb:sync -source:package=c:\Site1.zip -dest:metakey=lm/w3svc/1 > WebDeploySync.log
- {Optional – Migrate their site to the metaverse by using the Service Implementation Agent Web
Web Services Implementation Agent
If you do not wish to use a package, you can use the Web service implementation agent (MsDepSvc, also called «remote service») to synchronize from IIS 6.0 to IIS 7. WebDeploy 2.0 Migration
- Install the remote service on the source or destination depending on whether you want to synchronize from a remote source or to a remote destination.
- Start the service on the machine. net start msdepsvc
- Run the following command to perform a synchronization "push" from the local source to a remote destination (replace Server1 with the name of the remote computer). Run the command first with the WhatIf flag, then without it once you have confirmed that the command does what you want. msdeploy -verb:sync -source:metakey=lm/w3svc/1 -dest:metakey=lm/w3svc/1,computername=Server1 -whatif > msdeploysync.log
- You can also run the following command to perform a sync «pull» from the remote source to the local destination (replace Server1 with the remote computer name). Run the command first with the WhatIf flag, then without it once you have confirmed the command does what you want. msdeploy -verb:sync -source:metakey=lm/w3svc/1,computername=Server1 -dest:metakey=lm/w3svc/1 -whatif > msdeploysync.log
Discover more articles from our blog, such as Installation of WiFi networks with Ubiquiti products.