Clone activity

The Clone activity sends commands to vCenter to clone a given VMware virtual machine or virtual machine template.

Several input variables require a MOR ID. ServiceNow stores MOR data in the Object ID field of configuration item records.

These variables determine the behavior of the activity.

Table 1. Input variables
Field Description
vCenter IP address of the vCenter server that manages the virtual machine to clone and also will manage the clone.
VM uuid The VMware universal unique identifier assigned to the machine you are cloning. The Virtual Machine UUID topic provides instructions on properly formatting the unique identifier for creating a workflow.
Clone name The name to assign to the newly cloned virtual machine. The clone name has the following requirements:
  • Maximum length is 80 characters.
    • The special characters %, /, and \ are escaped in a clone name. A slash(/) is escaped as %2F or %2f, a backslash(\) is escaped as %5c or %5C, and a percent is escaped as %25. The special character % is not escaped when used to start an escape sequence.
  • Clone name is unique within a folder.
Folder MOR id The managed object reference ID for the folder in which the cloned virtual machine resides. This variable is optional. If this field is blank, Orchestration places the cloned virtual machine in the same folder as the source virtual machine.
Datastore MOR id The managed object reference ID for the datastore the new virtual machine belongs to. This variable is optional. If this field is blank, Orchestration places the cloned virtual machine in the same datastore as the source virtual machine.
Host MOR id The managed object reference ID for the host the new virtual machine is assigned to. This variable is optional. If this field is blank, Orchestration assigns the cloned virtual machine to the same host as the source virtual machine.
Resource pool MOR id The managed object reference ID for the resource pool the new virtual machine is assigned to. This variable is optional when cloning a virtual machine. If this field is blank, Orchestration assigns the cloned virtual machine to the same resource pool as the source virtual machine.
Resource Pool Owner Owner of the resource pool as seen by vCenter. For example, the owner might be something like labesx01.service-now.com or an IP address. The owner should point to the ESX box on which the original VM and clone are located (whatever vCenter's representation of that ESX name is).