Inheriting Lab Profiles

A lab can optionally inherit some properties from anotherLab Profile. When a lab profile inherits from another lab profile, this is known as a parent lab profile and child lab profile.

The virtual environment (virtual machines, virtual networks, etc) can be inherited, as well as resources and content (manuals, scenarios, activities, etc).

Best Practices for Inheriting a Lab Profile

When To Use the Parent Feature

Inheritance is recommended for lab profiles that need regular updates to the content, certifications or licenses. Inheritance allows for updates to be made to a parent lab profile, to safely update all child lab profiles that inherit from the parent.

Configuring Inheritance

1. Navigate to the lab profile that you intend to make a child lab profile, that will inherit from another lab profile.

2. Select edit in the upper-right corner of the lab profile.

3. On the Basic Information tab, select choose next to the Parent field.

4. In the dialog that appears, search for the lab profile that will be the parent to this lab profile.

5. Select the parent lab profile and then select OK.

6. After selecting the parent lab profile, select inheritance options for the child lab profile.

   • Inherit Environment: selecting this will allow the child lab profile to inherit virtual machines, virtual networks, removeable media, etc.

   • Inherit Content: selecting this will allow the child lab profile to inherit all content from the parent lab profile such as manuals, instructions, scenarios, question and automated activities, and activity groups.

7. Select Save, to save the changes.

After saving the lab profile, you will notice a banner on the lab profile details page that specifies that the lab profile is a child, with a link to the parent lab profile.

After configuring inheritance, there is no need to make any changes to any TMS courses that use this lab profile.

When To Not Use the Parent Feature

It is not recommended to use the parent feature if the lab profile uses a public IP or shared lab network configuration setup. When a parent lab profile that uses a public IP is configured on a child lab profile, it may prevent the network configuration from functioning correctly.