# A. Modify Existing Image with RR

# 1. Setup rrCloudConnector

•Start rrConfig, tab rrCloud

•Either create a new rrCloudConnector or use an existing rrCloudConnector.
If you use an existing non-Batch rrCloudConnector, then you should delete its resource group via the portal first. (Wait until it was deleted)

•Set the max VMs to some low value like 1 or 2.

VM Image:

You can choose an image...

•that you had created before.
This image does not require to have rrCloudService installed.

•use one of our images (They have rrCloudService installed)

## RR preinstalled images

We provide some ready-to-use images for a rrCloudConnector.
They can be used for all render jobs that use RR Shared Executables
Shared Executable have been copied inside the RR folder.
They do not require any installation on the target machine.

If you have already used them with RR on-premise, then you know it works with any machine.
By defaut, these render apps are already setup as Shared Executables:

•Redshift Standalone (for rendering .rs archive/scene files only)

•Arnold Standalone (for rendering .ass and .usd archive/scene files only)

•Mental Ray Standalone (for rendering .mi2 archive/scene files only)

•Octane Standalone (for rendering .mi2 archive/scene files only)

•Lightwave

•Altus

•FFmpeg

Then RR provides some config files to switch additional apps into Shared Executables.
(see Render_apps\_config_inhouse\examples\rrSharedExe\)

•Houdini

•Husk (Houdini)

•Blender

•Unreal Engine

•VRay Standalone (for rendering .vrscene archive/scene files only)

•Nuke

### Azure Images

Note: Smaller images create faster and boot up faster.
Therefore we recommend the 30GB or 60GB images.
They are sufficient for most of the render applications.

OS | Installed | rrCloudConnector Settings
CentOS 7.3 27GB free (30GB total) | •rrCloudService •mc (Midnight commander) •Lib packages that are required to run Maya, Nuke, Houdini, Modo and join an Active Directory/domain are installed. | VM Storage: royalrenderpublic VM storage SAS token: (none, enter nothing) VM Image filename: Empty-Linux.vhd
Windows 2016 16 GB free (30GB total) | •rrCloudService •Windows Component cleanup executed •All Windows Server Feature installers are removed •NVidia K80 Drivers •Total Commander c:\totalcmd\TOTALCMD64.EXE | VM Storage: royalrenderpublic VM storage SAS token: (none, enter nothing) VM Image filename: Empty-Win2016-30GB-K80.vhd
Windows 2016 46 GB free (60GB total) | •CloudService •Windows Component cleanup executed •All Windows Server Feature installers are removed •NVidia K80 Drivers •Total Commander c:\totalcmd\TOTALCMD64.EXE | VM Storage: royalrenderpublic VM storage SAS token: (none, enter nothing) VM Image filename: Empty-Win2016-60GB-K80.vhd
Windows 2016 108 GB free (120GB total) | •CloudService •Windows Component cleanup executed •All Windows Server Feature installers are removed •NVidia K80 Drivers •Total Commander c:\totalcmd\TOTALCMD64.EXE | VM Storage: royalrenderpublic VM storage SAS token: (none, enter nothing) VM Image filename: EmptyEmpty-Win2016-120GB-K80.vhd
Windows 2016 Core 23 GB free (30GB total) | •CloudService •Windows Component cleanup executed •All Windows Server Feature installers are removed •NVidia K80 Drivers •Total Commander c:\totalcmd\TOTALCMD64.EXE | VM Storage: royalrenderpublic VM storage SAS token: (none, enter nothing) VM Image filename: Empty-Win2016Core-30GB-K80.vhd

# 2. Create VM via rrCloudManager

•Start the rrCloudManager application.

•Click on the top right "Connect".

•Select the rrCloudconnector tab you just setup in rrConfig.

•Enable the checkbox "Advanced" at the bottom.

•Un-Check "Auto configure".

•Check "Create Manually" and "Start Manually" and set both to 1.

•Press <Start> to start the Cloud Connector.

# 3. Modify the image

1.Wait until the VM status is "Running" and has an IP.
Wait 3 more minutes to give the OS some time to setup.

2.How to copy files to the VM?
You can...

o...either copy files from your machine to the VM.
Linux: Right-Click on the VM and File Browser connection.
Windows: Connect to the VM temp drive by entering \\<IP>\c$ or \\<IP>\d$ into a Windows explorer and use the credentials you have set in rrConfig for the VM admin pass.

o...or remote connect to the VM and access your fileserver form the VM

3.Remote Connection
Right-Click on the VM and choose RDP/SSH session.

Use the temp drive!

You have a few options to get your installer files to the VM.
If you copy the installer to the VM, you might want to use a temp drive if it is provided.
If you extract installers (Like Autodesk), extract it to the temp drive as well.
This keeps the system drive less cluttered and clean.
Azure always offers a temp SSD drive.
This drive is located in D: (\\<IP>\d$) on Windows and /mnt/resources on Linux.

Note: DO NOT change the temp drive location on Azure. RR uses it while rendering!

GPU Image:

If your source image was already a GPU image, then please be sure the driver installation completed.
Check the Device manager if the GPUs are listed and the task manager (tab details) if the process drvinst.exe in still running.

# 4. Update RR

Continue with the section "3. Install the RR cloud service of the other help file use the latest version of the rrCloudService.

Afterwards, continue with the next step 5:

# 5. Capture Image

Continue with the section >> III. Capture Image

Afterwards, continue with the next step 6:

# 6. Cleanup

•After you have copied the image a storage that is not part of the resources created by the rrCloudConnector,
cleanup the resources in your cloud that are not required any more:

o Azure:
Login at the portal.
Delete the resource group of the rrCloudConnector.

•Open the config of rrCloudManager.
Either delete the rrCloudConnector or change the image to match your new image.