Need help upgrading Orchestrator (on-premises) and Studio from version 2022.10 to the latest version

Hi Techies,

I need help upgrading Orchestrator (on-premises) and Studio from version 2022.10 to the latest version.

Questions:

  1. I’m currently using version 2022.10, and most of my processes are in Windows-Legacy. Do I need to update them before upgrading?
  2. Do I need to convert Classic Folders to Modern Folders?
  3. We haven’t added folder paths in the config file since we use only one Classic Folder. If we convert to Modern Folders, do we need to update the existing processes with folder paths?
  4. After converting to Modern Folders, how do I add unattended and attended bots in Orchestrator?
  5. All my Virtual Machines share the same credentials. How should I add users for six unattended bots in Orchestrator?
  6. Some of my processes need to run on specific machines only. How can I configure this in Orchestrator?

If I’ve missed anything, please let me know. Also, what major issues should I anticipate, and what precautions should I take before upgrading?

Thanks!

Hello @Madhukrishna_Telugu

While not answering all your questions, yes I believe you will need to:

  1. Convert your Windows/Legacy processes to Windows
  2. Migrate your Classic folders to Modern folders

This might look frightening at first but dividing the tasks into manageable chunks will make it easier.
Going one proces at a time and looking into dependency alternatives.
Along the way you might find this “conpendium” useful:

Regards
Soren

1 Like

This is a major thing to do. I highly suggest engaging UiPath support to help you do this. I sure hope you have a QA system to do this on before doing it to production.

  1. No
  2. Yes
  3. Paths for what? Assets etc? If that’s what you mean, no, you put the Assets etc into the process folder. This was the only way to control the robot(s) and machine(s) each process runs on. We created one folder for each process. That process’ Assets, Queues, etc are also in the same folder. That way you don’t have to designate folder paths.
  4. You assign the robot accounts to the folders
  5. See #4
  6. By assigning only those machines to the folder the process is in. You can also control it within the Triggers.

Again, when we went through this it was a major project and we only succeeded because we had UiPath directly involved in assisting us.

Frankly, the way modern folders work is awful, and you will need their help in converting.

1 Like

Hi @Madhukrishna_Telugu

  1. Convert Windows-Legacy processes to Windows before upgrading.
  2. Migrate Classic Folders to Modern Folders for better management.
  3. Update folder paths in processes if switching to Modern Folders.
  4. Add bots in Tenant → Folders → Manage Access and assign roles.
  5. Create six machine templates and assign them to users.
  6. Use Machine Templates and Execution Targets for specific machine assignments.
  7. Backup data, test in a lower environment, check dependencies, and verify licensing before upgrading.

Take help from the UiPath Support Team if required.

1 Like

@prashant1603765 @postwick @SorenB
Thanks for your suggestions! I will consider the suggestions mentioned above.

Actually, we don’t have a test environment—only production.
So, I need to practice directly in production, such as creating Modern Folders and testing via an Attended Robot. That’s why I’m looking for a detailed approach to this migration.

Your suggestions will be very helpful for me in making this migration smoother.

Hi @Madhukrishna_Telugu

Before starting, back up your data to avoid loss. Create Modern Folders in Tenant → Folders and migrate from Classic Folders. Update process folder paths to point to the new Modern Folders. Add Attended Robots in Tenant → Folders → Manage Access and assign appropriate roles. Create and assign Machine Templates to users, linking them to the right machines. Test processes in production with Attended Robots, monitoring for issues. Check dependencies and confirm licensing is correct.
Reach out to UiPath Support if you need help during the migration.

1 Like

@prashant1603765

Can I get any reference videos or screenshots related to this?

As I mentioned, a few of my processes need to run on specific machines because we have stored some text files that need to be referenced for new runs.

Note: All my VMs have the same credentials, so should I create one user or six users?

1 Like

Great @Madhukrishna_Telugu
Use the below link for reference:
1.

2.

Regarding your question about users: If all your VMs have the same credentials, it’s generally fine to create one user that can be used across all machines.

1 Like