I want to know the checklist or anything we need to take care while/after upgarde.
After upgrade , does all orchestrator setting , robot,machine ,modern folder,queue item ,logs is automatically migrated to newer version
Migrating an on-premises UiPath Orchestrator requires careful planning and execution to ensure a smooth transition. Here is a checklist of tasks you should consider before and during the migration process:
Review the system requirements for the new version of UiPath Orchestrator to ensure compatibility with your infrastructure.
Create a backup of your existing Orchestrator database and configuration settings.
Review and document any customizations or integrations you have made to the current Orchestrator environment.
Notify your users and stakeholders of the upcoming migration and establish a communication plan for any service interruptions.
Install the new version of UiPath Orchestrator on the target server or virtual machine, following the installation guide provided by UiPath.
Verify that the new Orchestrator version is compatible with your existing database, and perform any necessary database upgrades or migrations.
Apply any customizations or integrations to the new Orchestrator environment, following the documentation and guidelines provided by UiPath.
Test the new Orchestrator environment to ensure that all functionalities are working as expected.
Migrate your data and workflows from the old Orchestrator to the new one.
Perform end-to-end testing to ensure that all processes are working correctly in the new Orchestrator environment.
Update any necessary configurations or settings, such as the web.config file, to reflect the new environment.
Notify your users and stakeholders that the migration is complete, and provide any necessary training or documentation on any new features or changes to the Orchestrator environment.
Monitor the new Orchestrator environment to ensure that it is performing as expected and that all processes are running smoothly.
Address any issues or bugs that arise during the initial deployment and testing phase.
Update any relevant documentation, such as runbooks or standard operating procedures, to reflect the new Orchestrator environment.
Here are some of the IIS settings that may need to be reviewed and adjusted during a UiPath Orchestrator migration:
Application Pool Settings: The application pool for the new Orchestrator instance should be configured with the correct .NET Framework version, identity, and other relevant settings. This can typically be configured through the IIS Manager tool.
SSL Certificate: If the previous Orchestrator environment used SSL encryption, a new SSL certificate may need to be installed and configured for the new environment. This can involve generating a new certificate, configuring the bindings for the site, and configuring the SSL settings in the web.config file.
Authentication Settings: The authentication settings for the new Orchestrator environment may need to be reviewed and adjusted to match the requirements of your organization. This can involve configuring settings for Windows Authentication, Forms Authentication, or other authentication methods that are supported by the new Orchestrator version.
URL Rewrite Rules: If you have implemented custom URL rewrite rules in the previous Orchestrator environment, these may need to be reviewed and adjusted to work with the new environment. This can involve configuring the URL Rewrite module in IIS and adjusting the rules to match the new site structure and environment.
It is important to carefully review and configure these IIS settings during the migration process to ensure that the new Orchestrator environment is functioning properly and securely.
thanks @Anil_G ,may i know how can i check which database is connected/point to orchestrator
Regardless of how you choose to update, if the database you point to does not exist, it is automatically created while running the update. If you point to an existing database, it is updated during the same process. The Orchestrator SQL database is automatically set to be case-insensitive (“OrchDB” = “orchdb”) at installation.
You can go to the orchestrator server machine and check the web.config file which generally is in this folder unless you changed it C:\Program Files (x86)\UiPath\Orchestrator … In that search for ConnectionString you should find the db details there
If you are admin…then on orchestrator settings page as well you should be able to check the db details