Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
VirtaMove Knowledge Center

VirtaMove Documentation
  • VirtaMove Support Knowledge Base
    VirtaMove Support Knowledge Base
     This trigger is hidden
Results will update as you type.
  • V-Migrate Documentation
    • 01. Managing Your VirtaMove Licensing
    • 02. Installation Guide
    • 03. Application Migration Guide
      • Environmental and Machine Requirements for Migration
      • Introduction to VirtaMove Application Migration
      • Activating Your VirtaMove License
      • Migrating an Application
      • Migrating an IIS Application
        • About Migrating an IIS Application
        • Support for Up-Level Migration of IIS Applications
        • Migrating an IIS Application Using Administrative Console
        • Migrating an IIS Application Using the VirtaMove CLI
        • Performing a Staged IIS Application Migration
        • Migrating an IIS Server on a Web Farm
        • Migrating an IIS Web Site that Uses HTTPS (SSL)
        • Viewing the IIS Migration Log
        • Advanced IIS Migration Features
      • Using VirtaMove Source Monitor
      • Monitoring Migration
      • Running and Exercising Your Application
      • Dissolving Your Application
      • Advanced Application Migration
    • 04. Administration Guide
    • 05. CLI Guide
    • About VirtaMove V-Migrate Documentation
  • V-Maestro Documentation
  • VirtaLinux Documentation

    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Migrating an IIS Web Site that Uses HTTPS (SSL)
    Published Mar 03, 2022

      Migrating an IIS Web Site that Uses HTTPS (SSL)

      You must perform extra steps when migrating a website that uses Hypertext Transfer Protocol Secure (HTTPS), because HTTPS must be configured to use a security certificate. Security certificates are created for a specific machine and are encrypted, and so VirtaMove cannot use the source server's security certificate on the destination server. You must therefore create a new certificate for the destination server and then register it with the bindings.

      The following procedure explains how to create a self-signed certificate, which should be used for testing purposes only. You will need to create a new certificate by contacting a certificate licensing authority.

      1. Complete the pre-requisites listed in Environmental and Machine RequirementsPreview and perform steps 1 to 11 inclusive in Migrating an IIS Application Using Administrative ConsolePreview.

      2. Double-click the VirtaMove CLI desktop shortcut to open a VirtaMove command prompt window.

      3. At the command prompt, type:

        c:\windows\system32\inetsrv\inetmgr.exe
      4. In IIS Manager, click on the server in the left pane.

      5. In the middle pane, right-click Server Certificates, and select Create Self-Signed Certificate.

      6. Enter a name for the certificate.

      7. Expand the server, then expand Sites and click on your website.

      8. In the right pane, click Bindings.

      9. Double-click the binding for HTTPS.

      10. Select your new certificate at the bottom of the window.

      11. Test the website.

      {"serverDuration": 13, "requestCorrelationId": "bf93d2608ffc4b7e959f103e5c168012"}