I want to create Orchestrator test Instance

Hi Team,

I have Prod Orchestrator instance but i want to create a test or dev Orch instance before PROD upgradation , so how can i create an test instance of orchestrator same as PROD.

It could be helpful if any response.

Thankyou

hi @Snehamayi_Senapati

Recommended Solution for Test Orchestrator Instance:

Option 1: Automation Cloud (Recommended)

  1. Go to Admin > Tenants > Create New Tenant
  2. Select “Development” environment type
  3. Enable Orchestrator service & allocate licenses
  4. Export packages/assets from Prod → Upload to Test tenant​

Option 2: On-Premises/Automation Suite

  1. Take Prod database backup + config files
  2. Deploy fresh Automation Suite on test servers
  3. Restore backup during installation (uipathctl commands)
  4. Test upgrade safely before Prod cutover​

Never clone VMs directly (licensing conflicts). Use separate instances/tenants for isolation.

Thankyou for the response ..
Currently i am using 2023.4.1 version of Orch so i need to do in the same orch?

@Snehamayi_Senapati

For 2023.4.1 Orchestrator:

Cloud: Admin > Create Development tenant with Orchestrator
On-Prem: DB backup → Fresh 2023.4.1 install → Restore

THEN test your Prod upgrade safely.

Export packages/assets from Prod → Import to Test tenant.

This is the official UiPath methodology regardless of version.

Version 2023.4.1 supports both approaches perfectly. Same best practice applies across all versions

  1. Restore backup during installation (uipathctl commands)
  2. Test upgrade safely before Prod cutover​

how to do this step no 3 as explained above. could you plz help with detailed step.

Thankyou

@Snehamayi_Senapati

2023.4.1 Test Instance - EXACT STEPS:

  1. Backup Prod: DB + web.config + UiPath.Orchestrator.dll.config
  2. Fresh 2023.4.1 install on test server (empty DB)
  3. SQL Restore: Prod DB backup → Overwrite test DB
  4. Replace config files from Prod backup
  5. Restart services → Test works!

Now safely test upgrades before Prod.

Docs:

Refer to this video for more details:

Hi @Snehamayi_Senapati

You can’t directly clone Orchestrator. Create a separate Test/Dev Orchestrator (new tenant or server) with the same version as Prod, restore a Prod DB backup to it, update configs, and disable triggers/robots. Use this to test the upgrade before Prod.

Thankyou for the response.
for * Backup IIS Configuration Using IIS Manager

  • Open IIS Manager
  • Click the Server Name (top level, not the site)
  • Double-click Configuration Editor
  • In the Actions pane (right side), click Backup Configuration (but not able to see this option in the below screenshot)
  • Enter a backup name, for example: Before_UiPath_Upgrade_2026-01-13
  • Click OK

    Not able to find the option for backup configuration can anyone help me.
    Thankyou

hi @Snehamayi_Senapati ,

SOLUTION 1 (Enable feature):

IIS Manager → Server Name → Feature Delegation
→ “Configuration Editor” → Read/Write → Refresh
→ Backup button APPEARS

SOLUTION 2 (Recommended - MANUAL):

Copy these from C:\Program Files (x86)\UiPath\Orchestrator:

web.config
UiPath.Orchestrator.dll.config

Manual copy is safer & faster

Thankyou..
ok I have taken the backup of as u mentioned in SOlution2 is it again required to take back of IIS configuration?

In addition to that where is the below steps which i can perform it is mentioned in the link Orchestrator - Orchestrator Backup and Restore

In addition to the web.config and UiPath.Orchestrator.dll.config files, you must also copy the Application Settings and Connections Strings as follows:

  1. Select your Orchestrator App Service.
  2. From the Settings menu, select Configuration.
  3. From the Application Settings section, select Advanced Edit and copy the displayed value.
  4. From the Connection strings section, select Advanced Edit and copy the displayed value.
  5. Save these values to your designated backup location.

@Snehamayi_Senapati

NO IIS BACKUP NEEDED

Your Solution2 backup = COMPLETE:
web.config
UiPath.Orchestrator.dll.config
DB backup

IIS “Backup Configuration” = OPTIONAL (server-level, not Orchestrator)

Official UiPath docs confirm: Just those 3 files + DB

You’re 100% ready for test instance!

You have everything needed. Skip IIS backup - proceed to test server setup.

@Snehamayi_Senapati

PERFECT BACKUP - NO MORE NEEDED

Docs ON-PREMISES section (your case):

C:\Program Files (x86)\UiPath\Orchestrator
├── web.config ← ✓ YOU HAVE
└── UiPath.Orchestrator.dll.config ← ✓ YOU HAVE

“App Service” steps = CLOUD ONLY - skip them!

NEXT: Fresh 2023.4.1 test install → Restore your 3 backups [web:63]

You’re 100% complete!

Proceed to test server setup. Nothing missing.

1 Like

Hi Arjun,
Thankyou so much for your quick response..

Just a quick question: since the PROD environment is on a separate VM and the TEST environment is also on a different VM, do I need to copy the backups from the PROD VM to the TEST VM and install them there? The plan would be to perform a fresh 2023.4.1 installation on the TEST VM and then restore the three backups (Web, Orchestrator, and Database).please correct me. How to restore them.

Thankyou

@Snehamayi_Senapati

YES - Copy backups → Fresh 2023.4.1 install → Restore:

TEST VM STEPS:

Fresh 2023.4.1 install (empty DB)
SSMS → Restore PROD .bak → Overwrite test DB
Copy PROD config files → C:\Program Files (x86)\UiPath\Orchestrator
Update connection strings (if SQL name different)
IIS restart → DONE!

Your PROD data now lives safely on TEST VM!