Hybrid Connector migration: requirements

  • Last update on November 11th, 2026

Migrate your CoreView Hybrid Connector when you need to move it to a different server, such as when you:

  • Upgrade the operating system of the server or virtual machine where it runs
  • Replace the server or virtual machine, for instance because it is being decommissioned

The process involves deploying the new Hybrid Connector version on a new server, then moving your workload from the previous one. Before you start, check the requirements below.

Required expertise

This procedure is intended for your organization’s senior IT staff who support enterprise services. Before scheduling the migration, make sure the right people review this document and contact CoreView with any questions.

Downtime required

Plan the migration during a maintenance window. 

While the procedure is in progress, your management session is interrupted and management actions are not executed. Any actions submitted during this time are queued and run automatically once the target Hybrid Connector version is up and running.

Docker requirements

The CoreView Diagnostic Tool runs on Docker, and the Hybrid Connector runs in a Windows Server container. Windows containers must match the Windows Server version of the host, so each Hybrid Connector must run on its corresponding version:

  • Windows Server 2019: Hybrid Connector 2019
  • Windows Server 2022: Hybrid Connector 2022
  • Windows Server 2025: Hybrid Connector 2025

To install Docker on your Windows Server, follow Get started: Prep Windows for containers in the official Microsoft documentation.

Installation package and SKU

The Hybrid Connector uses the same installation package for every Windows Server version. What differs is the SKU, which you must configure to match your Windows Server version. For the step-by-step procedure, see Upgrade the Hybrid Connector: Migration steps.