Managing Container Settings
Table of Contents
Introduction
Many container settings are established during the creation process. You can review and modify these settings directly in the container using the Administrative Console.
To View Container Settings
Select a container, and then click the Appliance Settings tab.
The following settings appear in the tab:
Option | Description |
ID | The unique container identifier. Read-only. |
Description | A meaningful description of the container and its operation. |
Default App | The application that will run when the container starts. Enclose the path in quotation marks (“ “) if it includes spaces or an ampersand (&). |
Config File Path | Lets you specify a path for a Config-on-the-fly file for a selected container. |
Show Custom Scripts When They Run | Displays custom scripts when they are run. Several custom scripts are located in the container\scripts folder. These scripts can be run before and after docking and undocking containers and starting and stopping container services. |
Adding a Container Description
You can create a meaningful description of a container and its operation. The description has a maximum limit of 255 characters.
To Add a Container Description
Select a container, and then click the Appliance Settings tab.
Type a description of the container in the Description box.
Click Save.
Selecting a Startup Application
Containers can contain more than one application. Use this property to change the startup application to another application that is inside the container or on the underlying operating system.
To Select a Startup Application
Select a container, and then click the Appliance Settings tab.
Enter the full path of the container startup application in the Default App field. Enclose the path in quotation marks ("") if it includes spaces or an ampersand (&).
Click Save.
If you click the Run command button and a default application is not specified for a container, the VirtaMove command prompt is displayed.
To run the default application for a container, right-click the container and select Run Default App.
Specifying a Path for a Config-on-the-fly File
To Specify a Path for a Config-on the-fly File for a Container
Select an undocked container, and then click the Appliance Settings tab.
In the Config File Path field, specify the path to the Config-on-the-fly file.
Click Save.
Showing Custom Scripts When They Run
When you create a container, several scripts are created in the Container\Scripts folder as follows:
AfterDock.cmd
AfterStart.cmd
AfterStop.cmd
AfterUndock.cmd
BeforeDock.cmd
BeforeStart.cmd
BeforeStop.cmd
BeforeUndock.cmd
Script files can be customized to execute commands, call other batch files, make configuration changes, or make modifications to the system environment to support the applications and services in the container.
Do not rename script files.
Custom scripts can be run before and after docking, starting and stopping container services, and undocking containers.
For example, you can edit the BeforeDock.cmd script to add or remove a user or group from the container:
To add a user
net user username userpasswd /ADD
To remove a user
net user username /DELETE
To add a group
net localgroup group-name /add
To delete a group
To add a user to a group
To remove a user from a group
To Show Custom Scripts When They Run
Select a container, and then click the Appliance Settings tab.
Under Initialization, select Show Custom Scripts When They Run.
Click Save.
To Show Custom Scripts When They Run Using the CLI
Run the following:
To Change the Home Directory of a Script
Scripts (for instance, AfterDock.cmd) execute from the VirtaMove installation path (for example, C:\Progam Files\VirtaMove). You may wish scripts to execute from the directory in which they exist, such as the container’s scripts directory.
Add the following to the first line of the .cmd file:
This will change the Home directory to the directory in which the batch file is located.
Showing Container Properties in Scripts
All the container properties, including the source computer’s IP address, appear as environment variables in scripts.
For example, edit the Scripts/BeforeDock.cmd file as follows:
Then, dock the container, and run the following:
Locking or Unlocking a Container
You can lock a selected container to make sure that it is not modified during the migration process. Modifications could result in the application not running correctly after the tether process. You can then unlock the container once you're done.
To Lock a Container
Select a container, and then select Tools>Lock/Unlock VAA.
Enter a password in the first field. Take note or remember this password for when you want to unlock the container.
Confirm the password in the second field, then click OK.
To Unlock a Container
Select the locked container, and then select Tools>Lock/Unlock VAA.
Enter the password you created to lock the container, then click OK.