# Linked Clone

## Linked Clone

Linked Clone is an optional setting which can be set by Admin in a VM Template. The list of pre-requisites of linked clone are listed below

### Pre-Requisites&#x20;

1. vCenter 6.7&#x20;
2. VMware PowerCLI version 12.0.0.0 - To be installed on the RP server(s)

### Directory structure

1. A new directory needs to be created on the first level directory on the datacenter in vCenter server.&#x20;
2. Create a new VM with the required software's and configurations.

{% hint style="info" %}
You can drag and drop the VMs in to the new directory if you have already created a VM in a different folder in the vCenter server
{% endhint %}

1. Create a snapshot of the VM
   1. Once a VM is created, a snapshot of the VM should be created

![Hybr pre-requisites for linked clone](https://2861565768-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LoVCDjvSJF03p2a5huX%2F-M731fqkmUME6_-adDk-%2F-M7353PmQtiiudGO_vMR%2FLinked%20Clone%20Pre-Req.png?alt=media\&token=20e07f8b-6c9a-4bb9-b35f-39276ee02b23)

{% hint style="warning" %}
Once a snapshot is created, any new changes made on the parent vm will not reflect on the cloned VM. To reflect the changes, a new snapshot has to be created and updated in Hybr's VM Template
{% endhint %}

### Hybr Mapping for Linked Clone

Hybr uses VM Template to provision VMs. To enable Linked Clone, Admin should set the linked clone properties in Hybr VM Template.

#### Parameters include:

1. Parent VM Name
2. Parent VM Folder Name
3. Parent VM's snapshot name

{% hint style="info" %}
It is recommend to maintain an excel sheet with the list of all Hybr VM Templates and it's Linked Clone mapping parameters. This will come handy as a reference when there are a lot of templates. &#x20;
{% endhint %}

For all existing templates, CLI shall be used to update the templates with the Linked Clone parameters.&#x20;

#### Parent VM Requirements

In Parent VM – (One time Process)&#x20;

1. Enabled Administrator User Set password for the Administrator
2. User UAC we brought down
3. Shut down the parent VM
4. Snapshot to be taken on the Parent VM
