Table of Contents

Moving Containers

To move a container between two machines, you must compress the container into a .cap file. You move only .cap files between machines.

If scripts are required for the tethering process, place the scripts in the container's scripts folder before you move a container.

Compressing Containers

To move a container between two machines, you must compress the container into a .cap file. You move only .cap files between machines.

Compressing the container preserves the short file names of the files in the container as they exist on the source machine.

A container.cap file is created in the folder where the container is located.

A compressed container is displayed as "Compressed" in the Administrative Console.

Open

Notes:

• If a .cap file of the same name already exists, you must move it.

• Do not rename a container.cap file.

• Do not use a third-party file compression application to compress containers.

• If Tether is enabled for a container and you compress the container, the CPROP_USE_TETHER property for the .cap file will be set to "N".

• If you compress a container that is still tethered, the compression process will disable tether on the container. Additionally, credentials to the source machine will be lost. You will have to enable tethering again and specify credentials again as required when you uncompress the container later.

To Compress a Container Using the Administrative Console

1. In the Administrative Console, select a container, and then click Undock if it is docked.

2. Click the Compress button.

To Compress a Container Using the CLI

1. In the Command Prompt window, change to the VirtaMove installation folder.

2. Make sure that the container is undocked, and then compress the container:

   virtacompress <container>

   container is the full path of the container.

3. Move the .cap file to the destination machine where VirtaMove is installed, and then uncompress it.

Uncompressing Containers

To Uncompress a Container Using the Administrative Console

1. In the Administrative Console, select the compressed container file. Make sure that a container of the same name as the .cap file doesn't exist in the container folder.

2. Click the Uncompress button.

To Uncompress a Container Using the CLI

1. Make sure that a container of the same name as the .cap file doesn't exist in the container folder.

2. In the Command Prompt window, run the following command:

   virtauncompress <container.cap>

   containeris the full path of the compressed container.
   The container is created and populated with the container file set.

Compressing and Uncompressing Containers and Config-on-the-Fly Files

Compressing

When you compress a container, if the COTF file being used is not in the container's folder, VirtaMove will make a copy of the COTF file, put it into the container\scripts\ folder, and update the config file path to be relative to the container folder. For example:

.\scripts\StandardCOTF.xml

If a file of the same name already exists in the container\scripts\ folder, the existing file will be renamed by appending a date and time stamp to the filename.

Example:

If you are using a COTF file from outside the container folder (e.g., "C:\CustomCOTF.xml"), and a "CustomCOTF.xml" file already exists in the scripts folder, the existing COTF file inside the scripts folder will be renamed to "CustomCOTF_Dec.05_11.49.37.xml" (month, day, hour, minute, second), and the config file path will refer to the COTF file that was copied into the scripts folder: ".\scripts\CustomCOTF.xml".

Uncompressing

When you uncompress a container, VirtaMove converts the absolute config file path into a relative path to the container folder.

Example:

If the appliance folder is in the C:\ drive, "." would equal "C:\appliance\containerName"

"C:\appliance\containerName\hello\StandardCOTF.xml" would equal ".\hello\StandardCOTF.xml"

"D:\appliance\containerName\scripts\StandardCOTF.xml" would equal ".\scripts\StandardCOTF.xml"

Deleting Containers

You can delete a container that is no longer required.

Use the Administrative Console Delete function to delete a container to make sure that a container is undocked and that none of the processes that belong to the container are still running. Do not use the operating system Delete command to delete a container.  

To Delete a Container Using the Administrative Console

1. In the Administrative Console, select the container you want to delete.

2. Click Undock. The status of the appliance changes to "Undocked".

3. Select Delete from the VirtaMove tool bar.

4. Click Yes to delete the container.

Note: 

If you cannot delete a container folder even after you have restarted the computer, check to see if cinit.exe and crun.exe are running in the Windows Task Manager. End these processes and then delete everything in the container folder that you can. Reboot the computer. You should now be able to delete the folder.

To Delete a Container Using the CLI

• Run the following:

  virtaundock c:\mycontainers\mynotes virtadel.exe c:\mycontainers\mynotes

Deleting a Container that Contains Adobe Flash Player Active X

By default, the Adobe Flash Player Active X control .ocx file has the Read-Only attribute set and its security permission is Deny Everyone Write Attributes.

To successfully delete a container that contains the Adobe Flash Player Active X control, you must remove the Deny Everyone Write Attributes security permission on the .ocx file.