Table of Contents

Installation Log File

The log file is created in the directory defined by your %temp% Windows Environment Variable. The log name is:

VirtaMove-64 Installation.log

Installation Location

By default, VirtaMove is installed in the system drive under:

Program Files\VirtaMove

VirtaMove cannot guarantee that the system root directory is "C:\".

Installing VirtaMove

Important:

• If you are installing VirtaMove on a Windows Server 2012 machine, the installer may encounter an error related to Universal C runtime Update (KB2999226). See "Installing VirtaMove on a Windows Server 2012 Destination Machine" below.  

Notes:

• Review the requirements listed in Before You Install VirtaMove.

• To install and have full access to the VirtaMove solution, you must be logged in as the local "built-in" System Administrator (user with SID 500) or as an account with administrator privileges (for example, a member of an Administrator Group with SID 1001). For information about how to elevate permissions, see http://kb.macrium.com/KnowledgebaseArticle50132.aspx .

• VirtaMove requires Microsoft .NET Framework 4. If Microsoft .NET Framework 4 is not installed on your destination machine, you will not be able to install VirtaMove software; the installer will stop.

• The Source Agent installers (x86 and x64) are part of the main installation package (VirtaMove_x64.msi) of V-Migrate.

1. Run VirtaMove_x64.msi.

2. Click Next.

3. Do any of the following:

   1. Click I accept the terms in the license agreement, and then click Next.

   2. Click I do not accept the terms in the license agreement to cancel the installation, and then click Cancel.

   3. Click Print to print the license agreement, and then save the file.

4.  If you accept the terms, do any of the following:

   1. Click Next to install to the default folders.

   2. To select a different installation folder for VirtaMove software, click Browse, then specify a folder, click OK, and then click Next.

   3. To select a different folder for containers, click Change, then specify a folder, click OK, and then click Next.

5. Generate a new security key for the VirtaMove Source Agent or select an existing security key file, and then click Next.

6. Choose one of the following:

   • No Maestro connection - does not make V-Maestro the CA.

   • Maestro connection certificates - makes V-Maestro the CA, which generates the VirtaMove Micro SSL certificates and pushes them to the destination machine.
     
     If you select Maestro connection certificates, click Browse to select a Key, select a certificate, and select a CA Root Certificate. Click Next.

     

7. Click Install to begin the installation.

8. Click Finish to complete the installation.

The installer places three shortcut icons on your desktop:

• VirtaMove CLI

• Administrative Console

• VirtaMove Web Documents

Installing VirtaMove on a Windows Server 2012 Destination Machine

When you run VirtaMove_x64.msi on a Windows Server 2012 machine that is not current with Windows updates, the following error may occur:

Running the universal C runtime update (KB2999226) by itself may not work.

To resolve this issue:

1. Verify that the downloaded update is for the machine in question (for the same OS version and platform). Note that the update for Windows Server 2012 64-bit (Windows8.1-KB2999226-x64) may reference Windows 8.1, which is fine because Windows 8 and Windows Server 2012 may share the same update.

2. Verify that Windows Update>Installed Updates does not indicate that KB2999226 is already installed.

3. If both conditions above are confirmed, VirtaMove recommends that you first install pre-requisite updates on the machine:

   1. Go to Windows Update>Check for updates.

   2. Select all the Important Updates and install them.

4. Restart the machine.

5. Repeat steps 1, 2, and 3 until KB2919355 is installed.

6. Install the Universal C runtime update (KB2999226).

7. Run the VirtaMove destination installer again.