Uploading your own image

If you already have a disk image in your cloud subscription, which has the required software for your automations, you can create a copy of that image and upload it in Orchestrator. Further, you can create cloud robot pools starting from your Windows image.

You can upload images from Azure, GCP, and AWS blob storages.

Important:

When exporting the image snapshot, use a virtual hard drive format (.vhd or .vhdx).

Make sure that the virtual hard drive you want to upload is compatible with Azure Gen2 VMs. For more information on how to prepare your image for uploading, read the Azure documentation.

To upload the image from your cloud subscription:

1. Navigate to Tenant > Settings > Cloud Robot Images. The list with the available custom images is displayed.
2. Click Add custom image to open the uploading wizard.
3. Provide the following details:

   Option	Description
   Image name * (mandatory)	The name for your custom image.
   Description (optional)	The description for your custom image. For example, installed software or size.
   Robot Service Username (mandatory)	This is the name of the robot account used to execute the workflows. The robot account must exist on the uploaded image.
   Image file link * (mandatory)	The public URL where your image can be found. The URL must be accessible by UiPath. Learn how to generate a public URL (or a SAS URI).
   Image OS (mandatory)	The operating system on top of which the image is created in Orchestrator.

Editing existing cloud robot pools to use your own image

Once you upload your custom image to Orchestrator, it is ready to use:

New Cloud Robot Pools

Simply select the custom image you previously uploaded from the Image name * dropdown under the Customized image option (see step 8 in Creating the Cloud Robot Pool).

Existing Cloud Robot Pools

When you change the base image of an existing cloud robot pool to the image you previously uploaded, consider the following behaviors:

• Manual pools - you may need to delete existing VMs and recreate them using the new base image.

• Automatic pools - no new VMs are provisioned on the old base image, and the existing VMs should shut out.