Install Web Deploy on IIS (Export and Import Websites With Application Pools)

Hello everyone , in this video I will show you how can migrate Websites in IIS from one server to another servers with all required components by using Web Deploy tools. Let me describe Web Deploy Tools: Web Deploy (also known as MSDeploy) in IIS refers to a technology developed by Microsoft that enables seamless deployment, migration, and synchronization of web applications, websites, and web server configurations across IIS servers. It streamlines the process of exporting and importing IIS configurations and content, making it easier to move web applications between different servers or environments. Web Deploy provides a set of tools and utilities that allow you to Export IIS Configuration and Content, You can use Web Deploy to create a deployment package that includes not only the web application’s files but also the IIS server’s configuration settings. This package captures everything needed for the application to run correctly on another server. Second provided option is  Import and Deploy, On the target server, you can use the same Web Deploy tool to install the application and its associated configurations using the deployment package. This process ensures that the target server’s IIS configuration matches the source server’s configuration. Also you can use Web Deploy to synchronize changes between a source and target server. For example, if you’ve made updates to a web application on your development server, you can use Web Deploy to sync those changes to your staging or production server.

Step 1: Installing Web Deploy

  1. Download Web Deploy:
  2. Install Web Deploy:
    • Run the downloaded installer with administrative privileges (right-click and choose “Run as administrator”).
    • Follow the installation wizard:
      • Accept the license terms.
      • Choose the installation location (you can leave it as the default).
      • Select the components to install. Make sure to select at least the following:
        • Web Deployment Tool
        • IIS Deployment Handler
        • Management Service Delegation UI
      • Click “Install” to begin the installation.

Step 2: Configuring IIS for Web Deploy

  1. Open IIS Manager:
    • Press Win + R, type inetmgr, and press Enter to open the Internet Information Services (IIS) Manager.
  2. Enable Management Service:
    • In IIS Manager, select your server node (usually the top node in the Connections pane on the left).
  3. Double-Click on “Management Service” under the “Management” section in the middle pane.
  4. Configure Management Service:
    • Check the “Enable remote connections” checkbox to allow remote management of the IIS server.
    • Set the “Start Type” to “Automatic” to ensure the service starts automatically with Windows.
    • Specify a unique port for the management service (default is 8172).
    • You can also configure other settings like SSL and client certificates if needed.
  5. Configure Permissions:
    • Under “Management Service Delegation,” you can configure permissions for various users and roles. Click “Add User…” to specify the users or groups that should have permission to deploy websites.
  6. Apply Changes:
    • Click the “Apply” button to save your configuration.

Step 3: Exporting and Importing Websites with Application Pools

Now that Web Deploy is installed and IIS is configured, you can use Web Deploy to export and import websites with application pools.

Export a Website:

  1. Open a Command Prompt:
    • Press Win + X and choose “Command Prompt (Admin)” to open a command prompt with administrative privileges.
  2. Run the Export Command:
    • Use the msdeploy command to export a website. Replace placeholders with actual values:
    bashCopy codemsdeploy -verb:sync -source:webServer,computerName=<ServerName>,userName=<Username>,password=<Password> -dest:package=<PathToPackage.zip> -enableRule:AppPoolExtension
    • <ServerName>: Replace with the server name or IP address.
    • <Username> and <Password>: Replace with the credentials of an account with sufficient permissions.
    • <PathToPackage.zip>: Specify the path where you want to save the exported package.

Import a Website:

  1. Open a Command Prompt:
    • Open a command prompt with administrative privileges.
  2. Run the Import Command:
    • Use the msdeploy command to import a website. Replace placeholders with actual values:
    bashCopy codemsdeploy -verb:sync -source:package=<PathToPackage.zip>,includeAcls=“False” -dest:webServer,computerName=<ServerName>,userName=<Username>,password=<Password>
    • <PathToPackage.zip>: Specify the path to the package you want to import.
    • <ServerName>: Replace with the server name or IP address.
    • <Username> and <Password>: Replace with the credentials of an account with sufficient permissions.
  3. Execute the Command:
    • Execute the command, and the website with its associated application pool will be imported to the target server.

By following these detailed steps, you should be able to successfully install Web Deploy, configure IIS for remote management, and perform website export and import operations with application pools. Always exercise caution when making changes to production servers and ensure you have backups in place.

Capture Customized Windows Image by WDS

Step 1: Prepare the Reference Computer
Install Windows on a reference computer.
Customize the Windows installation as needed (install applications, configure settings, etc.).
Step 2: Sysprep the Reference Computer
Open a command prompt with administrative privileges.
Navigate to the Sysprep folder (usually located at C:\Windows\System32\Sysprep).
Run the Sysprep tool with the following options:
bash
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml
  • /generalize: Prepares the Windows installation to be imaged.
  • /oobe: Configures the computer to boot to Windows Welcome upon the next restart.
  • /shutdown: Shuts down the computer after Sysprep completes.
  • /unattend:unattend.xml: Specifies an unattend.xml file to automate the Sysprep process. This file is optional but recommended for consistency.

Step 3: Boot the Reference Computer into Windows PE

  • Insert a bootable media (USB drive or DVD) containing Windows PE.
  • Boot the reference computer from the bootable media.

Step 4: Capture the Image

  • In Windows PE, open a command prompt.
  • Use the WDSUTIL command to capture the image. For example:

mathematica
WDSUTIL /Verbose /Progress /Capture-Image /Image:”CustomImage” /Name:”Custom Image” /Description:”Customized Windows Image” /CaptureDir:”D:\Captures”

  • /Image:"CustomImage": Specifies the name for the captured image.
  • /Name:"Custom Image": Specifies a friendly name for the captured image.
  • /Description:"Customized Windows Image": Provides a description for the captured image.
  • /CaptureDir:"D:\Captures": Specifies the directory to store the captured image.

Step 5: Upload the Captured Image to WDS Server

  • After capturing the image, navigate to the WDS server.
  • Use the WDS MMC snap-in or the WDSUTIL command to upload the captured image to the server.

Step 6: Create an Install Image

  • In the WDS MMC snap-in, right-click on “Install Images” and select “Add Install Image.”
  • Specify the location of the captured image file and follow the wizard to create the install image.

Step 7: Deploy the Image

  • Boot a client computer from the network using PXE boot.
  • Select the customized image from the WDS server for deployment.
  • Follow the on-screen instructions to deploy the image to the client computer.

Make sure to test the deployment thoroughly before deploying to production environments.

Install Windows OS from Network | Install And Configure Windows Deployment Service (WDS)

1. Install Windows Deployment Services Role:

  • Open Server Manager on a Windows Server machine.
  • Click on “Add roles and features.”
  • Select “Windows Deployment Services” as the role to install.
  • Follow the wizard to complete the installation.

2. Configure Windows Deployment Services:

  • After installing the role, open the Windows Deployment Services console from the Server Manager.
  • Right-click on the server name and select “Configure Server.”
  • Follow the wizard to configure the server.
  • Choose the location to store the images (you can use the default location).
  • Select “Integrated with Active Directory” if you want to use Active Directory Domain Services (AD DS) to authorize clients and manage computer accounts.
  • Specify the DHCP server settings. You can choose to configure DHCP options 60, 66, and 67, or you can manually configure DHCP options if you’re using a separate DHCP server.

3. Add Boot and Install Images:

  • In the Windows Deployment Services console, expand the server name.
  • Right-click on “Boot Images” and select “Add Boot Image.”
  • Browse to the location of the Windows installation files and select the boot image (boot.wim) file.
  • Repeat the process to add the install image (install.wim) file for the Windows version you want to deploy.

4. Configure DHCP Options (if not done in step 2):

  • If you didn’t configure DHCP options during the WDS configuration, you’ll need to do it manually on your DHCP server.
  • Configure option 60 to PXEClient.
  • Configure option 66 to the IP address of the WDS server.
  • Configure option 67 to boot\x64\pxeboot.n12 for BIOS-based systems or boot\x64\wdsmgfw.efi for UEFI-based systems.

5. PXE Boot and Install Windows:

  • Boot the client computer from the network (PXE boot). This usually involves pressing a key (e.g., F12) during startup to access the boot menu and selecting the network boot option.
  • The client will contact the WDS server and load the boot image.
  • Follow the on-screen instructions to select the install image and complete the Windows installation.

6. Monitor Deployment:

  • Use the Windows Deployment Services console to monitor the deployment process and view the status of client installations.

By following these steps, you can set up Windows Deployment Services to deploy Windows operating systems over the network, making it easier to manage and deploy Windows installations across multiple computers.