You can migrate a mass of old user machines, for example, in the thousands, to new hardware models. The OS version is not changed in this process.

About this task

You use a CSV-based input file that defines the set of transitions needed, including source machine, destination machine, and parameters. This is performed using Mirage command line tools.

Table 1. CSV File Information



Source CVD name

Windows name of the CVD

New CVD name

Following the rebase - machine name + OU

Target device name

Windows name of the device

Optional note per machine

Appears in the Management console


Identifier of the target base layer (rebase) or no target base layer (universal restore)

Credentials for the domain join account

Username, password, and domain

Server address

URL of the server


  1. Centralize the source machines to the Mirage server.
  2. Assign these CVDs to a specific collection.
  3. Connect the new machines to the network with an initial Windows system and deploy the Mirage client to them. You can use mass deployment tools to deploy the client. There are several ways to do this:
    • Use the Mirage bootable USB or LAN to deploy the initial image.

    • Deploy an image using third party solutions, for example, PXE or MDT.

    • Ask the hardware vendor to integrate the Mirage client in the Windows image deployed on the machines.

  4. After the Mirage client is deployed, the new client machines appear in the Inventory > Pending Devices queue.
  5. Create a CSV file mapping of source machine names to target machine names.

    The target machine names are the desired names of the machines after the migration. Existing names are not used as these are sometimes randomly generated by the hardware vendor.

    Optionally, you can import this mapping from XML.

  6. Provide the Mirage Management console with a domain join account, with username and password.

    This account is used to rejoin the machines to the domain.

  7. Select the pending devices to be used as target machines.

    The number of target and source machines must be the same.

  8. Choose from the following base layer options:
    • Maintain the base layer from the source machines, which removes extraneous applications, such as OEM applications, from the target machines.

    • Apply a new base layer to the target machines to apply additional applications to the target devices.


The following migration processes take place:

  • For each source CVD, an available pending device is selected.

  • The source CVD is assigned to the selected pending target device, along with the base layer for the target model, if any.

  • The migration operation starts, including automatic boots whenever necessary.

  • The migration task is marked as done only when an upload was completed.

What to do next

After the process is completed, the previous CVDs are migrated to the new machines.