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 https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/310706978.

Notes:

• Both destination and source machines must be server machines. VirtaMove does not support IIS migrations to desktop operating systems (Windows XP, Windows Vista, Windows 7, Windows 8).

• 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.

To Start Remote Registry Service on the Source Machine

Remote Registry Service must be started on the source machine to migrate an application.

Membership in the local Administrators group, or equivalent, on the source computer, is the minimum required to complete this procedure.

1. On the source machine, open a command prompt window.

2. Execute:

   sc start RemoteRegistry

To Migrate an IIS Application Using the VirtaMove CLI

1. Store the activation code for the VirtaMove license. At the command prompt, enter the following:

   virtalicense <activation_code>

   Where <activation_code> is the activation code for the VirtaMove license.

2. Create a container. At the command prompt, enter the full path and name of the container. Spaces in the pathname are not permitted. For example:

   virtacreate C:\appliances\ContainerName> /E

3. At the command prompt, specify a default application for the container:

4. Synchronize roles and features between the source machine and destination machine. Run the following at the command prompt:

   where hostname is the name of the source machine, username is the name of the Administrator account on the source machine, password is the password of the Administrator account; ContainerName is the full path and name of the container.

5. Check for migration errors and resolve any errors.

6. Note the IIS services listed in the uos_services file in the VirtaMove installation path under the EXTRAS\IIS folder, so you can include them in steps 9 and 18 below.

7. At the command prompt, enable Tether:

8.  As appropriate, specify the path to the Config-on-the-fly (COTF) file:

   A standard COTF file is located in C:\appliances\<ContainerName>\scripts\StandardCOTF.xml. If you do not specify the complete path for the COTF file, VirtaMove automatically looks for it in the container\scripts directory. For example, you can specify:

9. List container services:

10. Add container services:

11. As appropriate, list user accounts on the source machine:

12. If you need to export user accounts to the container, enter the following:

    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. As required, specify user credentials for services:

14. List the group accounts on the source machine:

15. If you need to export group accounts (in addition to IIS_IUSRS or IIS_WPG, which are added automatically by VirtaMove) to the container, enter their SIDs and then export the group accounts:

16. Import the group accounts you exported in step 15 to the destination machine as follows:

    Where bundlepath is the full path to the account bundle you want to import.

17. On the source machine, make sure that the services you added are stopped.

18. Dock the container:

19. Start container services:

20. Run IIS Manager by double-clicking the IIS Manager icon on your desktop, or by opening a command prompt outside the container context and executing: 

    For example:

21. Close IIS Manager.

22. Open a web browser and go to http://localhost/

23. Browse to the application's page: http://localhost/<app name>/

You are now ready to test the container to make sure that it performs correctly, and then optionally run Dissolve. Before you run Dissolve, you must run undock and then use the Windows Service Control Manager on the destination machine to stop all IIS services. You can also identify IIS services by looking in the uos_services file in the container scripts folder.

virtamigrate