Before You Install VirtaMove

Table of Contents

Permissions

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). This is the best practice account to use.

Failing this account, you may use an account that is a member of a local Administrator Group (for example, a member of an Administrator Group with SID 1001). If User Account Control (UAC) is enabled, the LocalAccountTokenFilterPolicy registry key must be set to allow you to be elevated.

For assistance with administrator credentials, contact your system administrator.

If the name of the System Administrator account is changed (for example, from "Administrator" to "Test"), you must restart the computer before you install VirtaMove. Otherwise, Windows will still show that you are logged in as Administrator and not as Test.

Platform Support

VirtaMove installation is supported on the following destination operating systems:

  • Windows Server 2012

  • Windows Server 2016

  • Windows Server 2019

Microsoft .NET Framework

VirtaMove requires Microsoft .NET Framework 3.5 SP1. If Microsoft .NET Framework 3.5 SP1 is not installed on your destination machine, you will not be able to install VirtaMove software.

To Enable .NET Framework 3.5 on Windows Server 2012 Without Internet Access

If your servers do not have internet access, you can install .NET Framework 3.5 without Internet access using one of the following options.

Manually Adding .NET Framework 3.5

  1. When you manually add the .NET Framework 3.5 feature, you can specify an alternate source path on the Confirmation screen. Point this to a \sources\sxs for that particular Windows version.

  2. Proceed with the installation.

Using PowerShell to Install .NET Framework 3.5

You can use PowerShell to add .NET Framework 3.5 and provide access to the \sources\sxs folder on the installation media. The \sources\sxs folder can be copied to a network share - for example, \\network\share\sxs - to make it easily accessible to multiple computers. The destination computer account, DOMAIN\SERVERNAME$, must have read access to the network share.

Requirements

  • Windows Server 2012 R2

  • Installation media

  • Administrator user rights. The current user must be a member of the local Administrators group to add or remove Windows features.

  • Destination computers may require network access and rights to use either alternate sources or an Internet connection to use Windows Update.

Installation Steps

  1. In the Administrator Command Prompt, start PowerShell by typing:

    1 powershell
  2. To install .NET Framework 3.5 from installation media located on a network share, use the following command:

    1 Install-WindowsFeature Net-Framework-Core -source \\<Computer>\<share>\sxs
  3. For more information about the Install-WindowsFeature cmdlet, see http://technet.microsoft.com/en-us/library/hh918370.aspx

  4. To verify the installation, run the following command:

    1 Get-WindowsFeature

    The Install State column should show "Installed" for .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature.

Configuring Alternate Sources for Feature Files in the Group Policy Setting

The Group Policy setting specifies authorized source locations for .NET Framework 3.5 files. The policy setting Specify Settings for Optional Component Installation and Component Repair is located in the Group Policy Management Console or Local Group Policy Editor, in the folder Computer Configuration\Administrative Templates\System.

  1. In the Local Group Policy Editor or Group Policy Management Console, open the following policy setting:

    1 Computer Configuration\Administrative Templates\System\Specify Settings for Optional Component Installation and Component Repair
  2. Select Enabled to enable the policy setting, if it is not already enabled.

  3. In the Alternate Source File Path field in the Options area, specify a fully qualified path to a shared folder or a WIM file. To specify a WIM file as an alternate source file location, add the prefix WIM: to the path, and add the index of the image to use in the WIM file as a suffix. The following are examples of values that you can specify:

    1 2 3 4 5 #Path to a shared folder: \\server_name\share\folder_name #Path to a WIM file, in which 3 represents the index of the image in which the feature files are found: \\server_name\share\install.wim:3
  4. If you do not want computers that are controlled by this policy setting to search for missing feature files in Windows Update, select Never Attempt to Download Payload from Windows Update.

  5. If the computers that are controlled by this policy setting typically receive updates through WSUS, but you prefer to go through Windows Update and not WSUS to find missing feature files, select Contact Windows Update Directly to Download Repair Content Instead of Windows Server Update Services (WSUS).

  6. Click OK when you are finished changing this policy setting, and then close the Group Policy editor.

See: http://technet.microsoft.com/en-us/library/hh831809.aspx#BKMK_configgp

Unicode

VirtaMove software supports unicode for double-byte characters. For Unicode characters, make sure that you select a font that can display the relevant characters. For example, change the font of the command prompt to Lucida Console.

Verifying the Integrity of Downloaded Software

You can verify the integrity of your downloaded software by checking the MD5. See here for more details.