a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

ba895dd2-36db-47cc-bf1c-12fde6ed2ead.png

RPA Infra Engineer

Trying to use this tool on my cloud orchestrator. Getting the following error. Every indication says that I'm using all the rcorrect parameters (clientID, userkey, etc) in the powershell command line. Please help.

Invoke-RestMethod : The request was aborted: Could not create SSL/TLS secure channel.

At C:\UIPath\tools\orchestrator-export-entities.ps1:103 char:16

+ ... esAccount = Invoke-RestMethod -Uri $uriAccount -Method Post -Body $bo ...

+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebExc

    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

4/27/2022 4:57:43 PM    ERROR: Orchestrator Login failed

It does exactly what it says. It is also a good thing that JSON is included in the exported file so one can extract the required data.

bf053cf4-cd13-4e6f-81da-8c480b0136d6.zip

- tenantName: The tenant name of Orchestrator. The default value is "default"

- adminName: On-premises Orchestrator admin user name who has appropriate Roles against all Folders.

- adminPasswd: The password of the corresponding Orchestrator admin user

- windowsAuth: Set $true if logging-in the on-premises Orchestrator with Windows Authentication

- userKey: User key for Cloud Orchestrator

- accountLogicalName: Account logical name for Cloud Orchestrator

- tenantLogicalName: Tenant logical name for Cloud Orchestrator

- clientId: Client ID for Cloud Orchestrator

- The administrator specified by adminName or userKey must have the following Roles against all Folders to export entities:

- Tenant Permissions: Machines View, Folders View, Users View

- Folder Permissions: Assets View, Processes View, Queues View, Robots View, Triggers View

.\orchestrator-export-entities.ps1 -uriOrch "https://your-orchestrator-url" -adminName "export-admin" -adminPasswd "password"

.\orchestrator-export-entities.ps1 -uriOrch "https://cloud.uipath.com" -userKey "abcde_123456789012345678901234567890123456789" -accountLogicalName "MyAccount" -tenantLogicalName "MyTenant" -clientId "12345678901234567890123456789012"

* Reference: https://docs.uipath.com/orchestrator/reference#consuming-cloud-api

- If you create a new user to execute this script on Orchestrator v2020.4, please pay attention to this known issue: https://docs.uipath.com/orchestrator/docs/identity-server-troubleshooting#section-api-account-authenticate-calls-failing-for-users-who-changed-passwords-at-first-login

PowerShell script to export Orchestrator entities (User, Role, Robot, Machine, Process, Trigger, Queue and Asset) per Folder to a single CSV file.

- tenantName: Orchestratorのテナント名、既定値は "default"

- adminName: オンプレミスOrchestratorにおいて、対象フォルダーに適切なロールを持つ管理ユーザー名

- adminPasswd: 管理ユーザーのパスワード

- windowsAuth: Windows認証を使用してオンプレミスOrchestratorにログインする場合には$trueを指定

- userKey: Cloud Orchestrator のユーザーKey

- accountLogicalName: Cloud Orchestrator のアカウントロジカル名

- tenantLogicalName: Cloud Orchestrator のテナントロジカル名

- clientId: Cloud Orchestrator のClient ID

- adminName またはuserKey で指定される管理ユーザーはエンティティエクスポートを行うフォルダーに対して次のロールが必要:

- テナント許可: マシン参照、フォルダー参照、ユーザー参照

- フォルダー許可: アセット参照、プロセス参照、キュー参照、ロボット参照、トリガー参照

* 参照: https://docs.uipath.com/orchestrator/reference#consuming-cloud-api

- Orchestrator v2020.4でスクリプト実行用に新しい管理ユーザーを作成する際には、次の既知問題に注意してください: https://docs.uipath.com/orchestrator/lang-ja/docs/identity-server-troubleshooting#section-api-account-authenticate-calls-failing-for-users-who-changed-passwords-at-first-login

Orchestrator エンティティ (ユーザー、ロール、ロボット、マシン、プロセス、トリガー、キュー、アセット) をフォルダーごとにCSVファイルへエクスポートするPowerShellスクリプト

Export Orchestrator entities to CSV

NuGet package uploading script

フォルダ監視/キュー登録スクリプト

Call Orchestrator API from SQL Server

Orchestrator Manager