Pré-requisitos de migração

Antes de iniciar a migração, certifique-se de atender aos seguintes pré-requisitos:

.NET Runtime 6.0

É necessário ter o .NET Runtime 6.0 ou posterior para executar a ferramenta UiPath.OrganizationMigrationApp. Você deve baixá-lo e instalá-lo antes de executar o UiPath.OrganizationMigrationApp.

Linux

If .NET Runtime 6.0 or later is not present, download and install .NET Runtime for Linux before using UiPath.OrganizationMigrationApp.

Para instalar o .NET Runtime 6.0 no RHEL, execute o seguinte comando:

sudo yum install dotnet-sdk-6.0 -y

Windows

The UiPath.OrganizationMigrationApp tool requires .NET Runtime 6.0 at a minimum. If .NET Runtime 6.0 and beyond is not present, download and install .NET Runtime 6.0 for Windows before using UiPath.OrganizationMigrationApp.

UiPath.OrganizationMigrationApp

A ferramenta UiPath.OrganizationMigrationApp ajuda você a executar operações como mover os dados de identidade de todos os tenants de independentes para o Automation Suite e mesclar organizações.

To download UiPath.OrganizationMigrationApp, see Downloading the installation packages.

To see which UiPath.OrganizationMigrationApp version is compatible with your environment, see Compatibility matrix.

Ferramenta para gerenciar o Microsoft SQL Server

Você deve baixar e instalar o SQL Server Management Studio (SSMS) ou uma ferramenta semelhante para gerenciar o Microsoft SQL Server. Essa ferramenta ajuda você a restaurar o banco de dados do Orchestrator para a instância do SQL Server do Automation Suite ou uma instância diferente do SQL Server.

1. Baixe e instale o SQL Server Management Studio.
2. Faça login no SQL Server independente usando a string de conexão SQL independente.
3. Abra a porta 1433 para o banco de dados de origem e destino.

Regras de escape de caractere especial para senhas da string de conexão

In most instances, connection passwords are encapsulated within a single quotation mark ('). However, when the password includes special characters such as ``` or $, a different approach is required.

In these cases, the password must be formatted as \"`", replacing ` with the actual password. Moreover, you must also adhere to the escape rules as detailed in the following table:

Formato original no ADUC	Formato escapado na string do PowerShell
cn=James $ Smith	"cn=James $ Smith"`
cn=Sally Wilson + Jones	"cn=Sally Wilson \+ Jones"
cn=William O'Brian	"cn=William O'Brian"
cn=William OBrian`	"cn=William O``Brian"
cn=Richard #West	"cn=Richard #West"
cn=Roy Johnson$	"cn=Roy Johnson$"

Exemplo

Assume that the original password is 7'8:<=XMe$y[@vC?_4ZeY8c-~y'W!1dU4gnczuf'/p>j<I. Adhering to the special character escape rules, it becomes: Password=\"7'8:<=XMe$y[@vC?_4ZeY8c-~y'W!1dU4```gnczuf'/p>```j<I\"`.

O comando completo, com a senha configurada na string de conexão de destino, tem a seguinte aparência:

./UiPath.OrganizationMigrationApp.exe migrate -a -m -s "Server=tcp:abc.com,1433;Initial Catalog=UiPath_20230531;Persist Security Info=False;User ID=username;Password=asiodhyf;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;" -d "Server=tcp:cde.net,1433;Initial Catalog=AutomationSuite_Platform;Persist Security Info=False;User Id=[e-mail];Password=\`"7'8:<=XMe`$y[@vC?_4ZeY8c-~y'W!1dU4```gnczuf'/p>```j<I\`""