We are upgrading our on-prem orchestrator from 2018.4 to 2019.10 as a recommended version before upgrading to 2022.10. But we have only attended robots in the orchestrator and do we have have to update them as well and if that is the case how is that going to happen.
Second thing is we need to migrate from classic folders to modern folders and please suggest me the recommended procedure for that. I don’t think we have a tool for that as we are using 2018 at the moment and we are panning to upgrade them once we upgrade our orchestrator to 2019 version.
If there is any academy course is available for this then it will be so much helpful.
Hi @KishoreC ,
I think you need debug because have some differ from version
change each activity
but I think they correct, we don’t need up version
regards,
As we see in the latest versions of Orchestrator we have an option called create folder and migration tool but in older version like 2019 how can we create a modern folder? do we have any option to create a folder? With out migration tool how can we possibly create a modern folder?
Currently we have only packages, environments, processes, machines and users in the orchestrator( No Triggers, No Queues, No Assets) and I need to migrate them to modern folders and from the classic to modern folder document it is mentioned that all the environments are created as a folders and for me I have almost 300+ environments. In this case what is the best practice to create the folders?
Thanks for your reply! I didn’t get what you are mentioning but I am not doing any changes from studio. All I have to do is upgrade from 2018 to 2022 version along with classic to modern folder migration and I am seeking on best practices and recommendation to do these and from code end like I believe we may need to upgrade the studio dependencies if needed once we upgrade our orchestrator.
Also why dont you migrate to 2019 to 22 your end version and then convert once and for all?
300+ Environments that is weird but can you say how is your setup?
why do you have so many env?
First folder will be the same folder as your main folder and under as you dont have env in modern the only way to seggregate bots is through folders so you need to create sub folders as needed
I need to check that once I Upgrade it to 2019 version.
Many environments - That’s a big question for me as well
One more thing like in the orchestrator all we have is attended robots. So what is the possible way to update those robots? UiPath documents mentioned that from version 2021 we have an option called auto update from orchestrator but what about in the older versions?
When we am running the Upgrade tool we faced an issue with below error.
Our orchestrator database is hosted in PAAS and the Upgrade tool throwing error as bellow:
system.exception: init host: Login failed for user ‘myusername’
Can anyone help me on that?
And one more thing: What are the application that we need to put under maintanance before running the upgrade tool?
Right now we are just stopping the server from IIS where orchestrator is hosted.
What are the access that the user who is running the upgrade tool should have?
Is he just double click on the tool or and administrator access is need for him to do that? How to check the user access for that server?
we need to unlock the web.config sections from IIS right before upgrading.
But what are the sections we need to unlock. do we need to unlock all the sections which are available in system.webserver?
ashokkarale
Manisha_Ravindra
lakshman
Sanjay_Bhat
Sudeen_Raj_Shetty
natanfigueira
Akshaya89
Nisha_K21
Raja.G
Shruthika_r