Important:

• You must be logged in as the BUILTIN\Administrator or member of Local Administrators group on the destination machine.

• IIS application migrations require that system root drives match the destination and source machines.

• Before you migrate an application, complete the requirements listed in /wiki/spaces/VDOC/pages/310706978.

Notes:

• You cannot create a container on a drive where shortnames are disabled (if NtfsDisable8dot3NameCreation is set to 1 in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\File System).

• Services will not be retrieved if communication with the source machine is interrupted during the tethering process. This may occur for a number of reasons; for example, if the firewall on the source machine is enabled while tethering is in progress. If services are not retrieved, try any of the following: disable the firewall on the source machine; make sure that the Remote Registry service is enabled on the source machine; make sure that the user credentials you specify to connect to the source machine are correct; check the Tether log. Once you have identified the issue, connect to the source machine again.

• Some products or product components do not appear in the Source Products tab under the Tether tab of the Administrative Console. For example, Oracle 11g does not appear in the list because Windows does not understand it as an installed product. Oracle 11g does not register itself or leverage any Windows mechanisms related to installation and is therefore not recognized by the operating system as being installed. Therefore, Oracle 11g will not appear in the Source Products list but will be listed in Source Services and Source Accounts lists under the Tether tab. Make sure that you select services for such a product in the Source Services list.

To Migrate an IIS Application

1. Double-click the Administrative Console desktop shortcut icon on your desktop or click Start>VirtaMove>Administrative Console. VirtaMove Administrative Console opens.

2. Click Application>Create Empty VAA.

3. In the Create Empty VAA screen, enter the path to the container and then enter the name of the container. Click OK.

4. Select the new container, and then enable Use Tether.

5. In the Source Name field, specify the IP address or name of the source machine you want to connect to. Specify only an Administrator account.

   • Alternatively, click the Query Network button to display a list of machines on your network, and then select a machine and click OK to populate the Source Name field. If a source machine has a VirtaMove Source Agent installed on it, the Remote Discovery window will display Yes in the Source Agent column. You can sort the list by selecting a column heading to sort by.
     
     If you specified a source machine that has a Source Agent installed on it, the Administrator Username field and the Administrator Password field are automatically filled in. A green checkmark and "Source Agent" are displayed to the right of the Source Name field. Go to step 8. If you did not specify a source machine with a Source Agent, go to step 6.

6. In the Administrator Username field, type the username of the local administrator account on the source machine you specified in step 5. The default username is Administrator.

7. In the Administrator Password field, type the password of the local administrator account.

8. To tether the application based on IIS, click the Find Applications button. If credentials are valid, VirtaMove Tether retrieves all source applications, services, and user/group account information and displays this information in the tabs in the bottom half of the Tether window. To scroll through messages, click the Back or Forward button on the left or right of the message bar. If credentials fail or pre-requisites have not been met for tethering, an error message is displayed at the bottom of the Tether window. You can view the Audit Report by clicking the Audit report link to determine what the problem is and check the Migration log in C:\Program Files\VirtaMove\migration.log.

9. In the Source Products tab, review the list of remote applications.

10. Select Web Server (IIS) in the Source Products list. When you click away from this tab, VirtaMove Tether automatically selects all user/group accounts, services, and executables associated with the installed application and displays these in the Source Services and Source Accounts tabs. IIS services will be displayed after docking.

    

11. Click the Source Services tab and review the services that were automatically selected for the VAA.

    • Select more services as appropriate. IIS services will be automatically selected after docking.

    • Edit the User Name and Password for a service as appropriate. Note that you are setting a password only; VirtaMove does not validate a password against the original password associated with the source machine. You cannot edit passwords after you click Start Tether. Service User Names must be in the format domain\uid, where uid is the user identifier. This is a restriction of the Microsoft Win32 functions for working with the Service Control Manager (SCM), which is used by VirtaMove.

    • If you select a service and the service is "Started" on the remote machine, tethering will not succeed. Stop the service before tethering by right-clicking the service and then selecting Stop Source Service.

    • If you select a service and the service already exists on the underlying operating system, the Source Status column will display "CONFLICT". Resolve the conflict and then press F5 to refresh the list.

    • If you hover over a service in the list, a tool tip will display which selected service, if any, requires this service.

12. Click the Source Accounts tab. The group account IIS_IUSRS in the case of Windows Server 2008 or higher is automatically selected; the group account IIS_WPG in the case of Windows Server 2003 is automatically selected. Select additional accounts for the container as required.  If you select user accounts that do not correspond to a service, these accounts will be imported to the operating system of the destination machine with the default password 1password! when you dock the container. VirtaMove recommends that you change the passwords of these accounts at the earliest opportunity. For information about changing the default password to a different password if required, see Default Password.

13. Optionally, specify a https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/311263613/Config-on-the-Fly?search_id=fd0c4f5c-ced0-4c41-99bf-36c6f648c799 (COTF) file. Click the browse button to the right of the field to search for a COTF file or type the path.
    VirtaMove supports paths that are relative to the container folder. That is, VirtaMove supports:

    ".\scripts\StandardCOTF.xml"

    or the absolute full path:

    "C:\appliance\ContainerName\scripts\MyCustomCOTF.xml"

    You can also specify only the file name of the COTF file if the file is in the scripts folder. For example:

    "StandardCOTF.xml"

14. When you are ready, click the Pre-Populate button. If you have not yet activated your VirtaMove license key, you will now be prompted to do so. See Activating Your VirtaMove License for information. Note that the Pre-Populate portion process may take some time. A window displays the status of the Pre-Populate process and the amount of data copied. If you hover over the data moved in green, you can see the estimated time remaining. You can cancel the process by clicking Cancel.
    
    At the Migrating application data stage of pre-populate, the Tether Monitor icon in the system tray will spin until the end of the process. If you hover over the spinning icon, a tooltip will show the file size transferred and the rate of transfer.

    

    Click the Close button in the VirtaMove Pre-Population window to close the window when the process is complete.

15. To launch IIS Manager, double-click the IIS Manager shortcut on your desktop, or click the Launch Application button, and then select IIS Manager. Note that ODBC Manager is available in the Select an Application window if required for your application.
    The IIS Manager window opens.

    

    Note: The root node may display the hostname of your source server (for example, WEBWIN2008R2 as in the screenshot above). You can change it to the destination's hostname by right-clicking the root node and selecting Rename.

16. In the Administrative Console, click the Source Services tab. Right-click each service in the list and select Start. If you are migrating SQL and an IIS application, VirtaMove recommends that you start the SQL services first followed by the IIS services.

17. You are now ready to launch the application so you can exercise the main components of the application and test the application while it is tethered. Click the Launch Application button to select an application associated with a selected remote product or to open the VirtaMove command prompt. The Select an Application window opens. Do one of the following:

    • Select an application from the list, and then click Select. The selected application opens.

    • Select VAA Command Prompt. The container Command Prompt opens.

18. Exercise the application by connecting to the localhost with a browser. Make sure to open the browser from the destination's Start menu, and not from within the Launch Application window. Verify that the features of the application are functioning properly. See https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/311394496/Running+and+Exercising+Your+Application?search_id=bf9d6b7f-0eed-4fec-8f45-8c2e555364d8 for more information. If the web page of the web application fails to load, you can check the status of the IIS services by clicking Administrative Tools>Services on the destination machine. If these services are not running, start them again on the Remote Services tab of the Tether window.

19. As required, use VirtaMove Tether Monitor to monitor Tether activity and get an idea of when application components have been fully copied from the source machine. For more information, see https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/311230847/Monitoring+Migration?search_id=d9a00b87-9d7c-472b-84e2-ec6896284c10.

20. When you are satisfied that the main components of your application have been migrated, do the following:

    • Close your application.

    • Click the Source Services tab, and then right-click each service and select Stop.

21. Exit Administrative Console. You should now check whether the container state is "Undocked" or "CID Already Docked" by executing virtalist. If this is the case, execute https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/314179902/virtaundock?search_id=e0453485-e8b2-4d2f-9e20-27701a0dd8f0: 

    virtaundock /f <container>

    on the container with the same CID to stop the services and undock the container.

22. Optional. You are now ready to Dissolve the container. Before you run Dissolve, you must use the Windows Service Control Manager on the destination machine to stop all IIS services. For information about dissolving IIS applications, see https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/311460124/About+Dissolve?search_id=3097106a-761f-4a48-8aff-9ba977d44400.