Transfer Attended bot from PRD orchestrator to DEV orchestrator

Hi Community,

We have a attended bot in the PRD orchestrator, we wanted to disconnect Attended Bot from PRD and connect it to DEV.

Can someone guide me with this question of mine.

To add unattended Bot I know the process, but for attended bot what would be the process I want to know.

Thanks

Hi Rajnish_Pandey,
You can do the below steps:

  1. Download the Nuget package from PRD orchestrator.
  2. Upload downloaded package to DEV Orchestrator

Another approach is you can change the orchestrator url pointed to DEV orchestartor from the studio settings under Manage packages. After that you can publish your package from studio directly, which is not recommended/best practice.

Cheers!

To switch an attended robot from one Orchestrator environment (e.g., PROD) to another (e.g., DEV), you’ll need to perform the following steps:

Disconnect Attended Bot from PROD Orchestrator:

  1. Stop the Robot Service:
  • On the machine where the attended robot is installed, stop the UiPath Robot service. You can do this through the Services application or by using the command: net stop UiRobotSvc.
  1. Disconnect Robot from Orchestrator:
  • Open the UiPath Robot settings on the system tray.
  • Navigate to the Orchestrator settings.
  • Disconnect the robot from the PROD Orchestrator by clicking the “Disconnect” button.

Connect Attended Bot to DEV Orchestrator:

  1. Update Orchestrator Settings:
  • Open the UiPath Robot settings on the system tray.
  • Navigate to the Orchestrator settings.
  • Update the Orchestrator URL to point to the DEV Orchestrator.
  • Provide the necessary credentials for the DEV Orchestrator.
  1. Start the Robot Service:
  • Start the UiPath Robot service. You can do this through the Services application or by using the command: net start UiRobotSvc.
  1. Verify Connection:
  • Verify the connection to the DEV Orchestrator by checking the status in the Orchestrator settings. It should indicate a successful connection to the DEV Orchestrator.
  1. Check Robot Configuration in Orchestrator:
  • In the DEV Orchestrator, navigate to the “Robots” page and ensure that the attended robot is configured correctly and is in an available state.
  1. Test the Connection:
  • Execute a simple process on the DEV Orchestrator to ensure that the attended bot is connected and working as expected.

Considerations:

  • Ensure that the attended robot is licensed in the DEV Orchestrator.
  • Be cautious about switching between environments, as it may affect ongoing processes and automation jobs.
  • If the DEV Orchestrator uses a different machine key, make sure to update it in the Orchestrator settings on the attended robot machine.

Always perform such changes during maintenance windows or low-impact periods to minimize disruptions.

1 Like