Orchestrator Update / Flex licenses / Windows legacy / Orchestrator versions out of support

Help Studio
, ,
1

Hi,

This year we found several clients receiving a mail from UiPath explaining that in X date of X month the client will be out of support unless it changes the orchestrator to a new versión. And when we see de product life cycle of orchestrator you’ll see that you have 2 options, change to version 2022 or 2023.

This creates different doubts about what things should you take into account about dependencies to this new versions, like:

  • If a clients comes to you because they have a 2019 version and they want to update to 2023, what’s the best way to do it, it will generate big changes?

  • is it a requirement to change the licenses from normal to flex if you change to 2023 or you can still have your old licenses?

  • is it a requirement to change “Windows Legacy” processes to “Windows” processes in order to execute in 2023 version, why are we doing this change?

  • what “out of support” really means? what could happend to this kind of clients who doesn’t have the newest version of the products? what are they missing about support? what could we have or need or ask to UiPath if we are under support dates?

  • Are they dependencies between the flex licenses, the “Windows” type of processes and the orchestrator versions? for example: I’ve found that if you connect a studio flex license in an old orchestrator version, the studio license doesn’t appear, so you are forced to update the orchestrator.

I’m asking this because this year i’m seeing more alerts about “Out of support” or “change from windows legacy to windows” or in the new license renewal you could’ve received a flex license and doesn’t work with you orch version. But nobody shows why is need it or required, the impact of this changes and how to solve the problems that comes with it.

2
  • If a clients comes to you because they have a 2019 version and they want to update to 2023, what’s the best way to do it, it will generate big changes?

Upgrading from 2019 to 2023 version:Upgrading from an older version of Orchestrator to a newer version, such as from 2019 to 2023, can involve several considerations. You should review UiPath’s official documentation and release notes to understand what has changed between these versions and any potential migration or compatibility issues. The specific steps and potential impact of the upgrade can vary depending on the complexity of your automation processes and the features you’re using. It’s often recommended to start with a test or development environment to assess the impact of the upgrade before applying it to your production environment.

“Windows Legacy” to “Windows” Processes:Changes in process execution may be due to updates in Orchestrator’s capabilities or changes in how it handles automation. Switching from “Windows Legacy” processes to “Windows” processes might be necessary to take advantage of new features or improvements, or it could be part of a transition strategy. This transition could involve redeveloping or reconfiguring existing automation processes to ensure compatibility with the new version.

@KevinDS

3
  • is it a requirement to change the licenses from normal to flex if you change to 2023 or you can still have your old licenses?

*License Changes:The license requirements for upgrading to a new version of Orchestrator can also change. UiPath’s licensing terms and conditions may evolve with each new version. It’s essential to review the licensing documentation provided by UiPath to understand if there are any changes or requirements related to licensing when upgrading to Orchestrator 2023. The decision to switch from “normal” to “flex” licenses, if required, should be based on your organization’s needs and the licensing options provided by UiPath.

@KevinDS