Studio および Robot のインストールおよび更新を行ったり、コマンド ラインから UiPathStudio.msi
インストーラーを実行して既存のインストールを変更できます。
以下のセクションに、使用できるパラメーターの説明およびいくつかの使用例を示します。
注:
- これらのコマンドを実行するには、管理者権限が必要です。
- インストーラーをコマンド ラインからサイレント モードで実行して、既存のインストールを変更することはできません。ただし、インストーラーをサイレント モードで実行して、旧バージョンから更新することはできます。
- msiexec.exe の
/passive
オプションを使用した無人モードのインストールの実行はサポートされていません。
コマンド ライン引数の説明
以下の表に、使用できるすべてのコマンド ライン パラメーターのリストを示します。
クリーン インストールにはすべてのパラメーターを使用できますが、旧バージョンからの更新または既存のインストールの変更の場合は、以下のパラメーターのみサポートされます。
ADDLOCAL
を使用して機能を有効化します。REMOVE
を使用して機能を無効化します。Robot を無効化することはできませんので注意してください。SERVICE_URL
-RegisterService
引数を含めずに Robot をサービス モードからユーザー モードに切り替える場合に使用できます。NUGET_OPTIONS
、ENFORCE_SIGNED_EXECUTION
、DISABLE_SECURE_XAML
、およびTELEMETRY_ENABLED
- 古いバージョンからの更新で利用できます。既存のインストールを変更する場合は利用できません。
Command | Description |
---|---|
/q | Helps you install the specified UiPath features silently, without displaying the user interface. |
/l*vx <LogFile> | Generates an installer log file at the specified path. Starting with v2018.4.2, this file can also include licensing information if you license Studio or Robot at install time. You can send the file further to our support team if, for any reason, you encounter difficulties during the installation process. |
ADDLOCAL | Enables you to select what features to install. If ADDLOCAL is used, only the features specified in it are installed. If ADDLOCAL is not used, the following features are installed: Studio, the Robot in service mode, the activities packages, and the JavaScript add-on.It supports the following options: DesktopFeature - indicates that you want to install Robot and Studio features.Studio - Installs Studio. It cannot be used without DesktopFeature .ExcelAddin - Installs the StudioX Excel Add-in. It cannot be used without Studio .Robot - Installs the Robot in user mode or service mode, as well as the Assistant. It cannot be used without DesktopFeature .To install the Robot in service mode, also add the RegisterService option. This is the recommended choice for unattended Robots.To install the Robot in user mode, do not add the RegisterService option. This is the recommended choice for attended and development Robots.![]() .xaml files from the original NuGet Packages folder. For details on how to resolve this, see the NuGet packages not accessible after migration troubleshooting article.Packages - Installs the activities packages. It cannot be used without the Robot argument.StartupLauncher - Runs the Robot at Windows startup. It cannot be used without the Robot argument.JavaBridge - Installs the UiPath Java Bridge for a better integration and automation in regards to Java applications. Please note that installing the Java Bridge may cause the installation to last longer than usual. It cannot be used without the Robot argument.ChromeExtension - Installs the UiPath Google Chrome Extension. It cannot be used without the Robot argument.FirefoxExtension - e.g. : UiPathStudio.msi ADDLOCAL=Studio,Robot,ChromeExtension,FirefoxExtension /Q EdgeExtension - Installs the UiPath Microsoft Edge Chromium-based Extension. It cannot be used without the Robot argument.CitrixClient - Installs the UiPath Citrix Client Extension. It cannot be used without the Robot argument.JavaScriptAddOn - Installs the browser embedding JavaScript add-on for robot.SapPlugin - Installs the SAP Solution Manager plugin. Requires the SAP Connector for Microsoft to be installed on your machine. On clean installs, you must also provide an address for the instance using the SAP_SOL_MAN_HOST parameter. It cannot be used without Studio .VMwareExtension - Installs the UiPath Extension for VMware Horizon. It cannot be used without the Robot argument.WindowsRdpExtension - Installs the UiPath Extension for Microsoft Remote Desktop. It cannot be used without the Robot argument. |
MSIINSTALLPERUSER | Enables you to install Studio and Robot only for the current user. To install per user, add MSIINSTALLPERUSER=1 . To install per machine, do not include this parameter.The following options are not available in per-user installations: RegisterService, CitrixExtension, VMwareExtension, SapPlugin, PACKAGES_FOLDER, CODE. |
SAP_SOL_MAN_HOST | Hostname or IP address for your SAP Solution Manager instance. Required for clean installs if the SapPlugin argument was provided for the ADDLOCAL option.For example UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,SapPlugin SAP_SOL_MAN_HOST=ip_address |
APPLICATIONFOLDER | Enables you to install Studio and Robot in a custom location. |
NUGET_OPTIONS | This parameter is recommended if you are working in an offline environment. If set to DisableOnlineFeeds , this parameter helps you disable the online UiPath official and Community feeds for the Robot - only the Orchestrator and local feeds are taken into consideration.Please note that the URL feeds are not deleted from the configuration files, just ignored. It can be used for both installations and upgrades. |
PACKAGES_FOLDER | Enables you to change the download location of your workflows and their dependencies for Studio and/or Robot. This folder can be user specific or accessible by all users from a machine. This parameter can be used for both service mode or user mode robots. If you do not provide this parameter the default folder is %userProfile%\.nuget\packages .![]() ![]() PACKAGES_FOLDER parameter, there are some limitations. Find out more in the custom package folders and network paths documentation.If you need to use environment variables such as %USERNAME% or %USERPROFILE% , the % special character needs to be escaped as follows:When the setup is invoked from Command Prompt - use - UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^% .In batch scripts - use % - UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^% .In PowerShell console or scripts - no escaping is needed. When using Active Directory domain accounts, it is recommended to specify the domain name in the folder structure too, such as C:\packages\^%UserDomain^%.^%Username^% .For information on how to change the download folder for packages after installation, see Managing Activities Packages in the Studio Guide. |
CUSTOM_NUGET_FEEDS | Enables you to add custom NuGet activities feeds for Studio and/or Robot. This command only adds or updates the existing list of feeds. It must be populated with key-value pairs of type string. Valid locations include online feeds, folder paths, and shared network drives. Make sure that the provided feeds are reachable by all users from a given machine. Separate feeds with semicolons (;). Example: CUSTOM_NUGET_FEEDS="FeedName1,https://my.custom.nuget.feed; FeedName2,D:\Custom\Activities\Packages\" . |
ENFORCE_SIGNED_EXECUTION | Optional. Enables you to enforce your Robots to execute only signed packages. It can be used at clean installs or updates of your instances. If this parameter is not specified at deploy-time, package signing is not enabled. It supports the following options: 1 - The Robot is able to download, install, or execute only packages author or repository signed by UiPath. If you want to add your own certificate as a trusted source, you have to do so by modifying the nuget.config file. To learn how to do this, please see this page.0 - No package signing rule is enforced on your Robot deployment.For information on how to enforce signed execution after installation, see Signing Packages in the Studio Guide. |
CODE | Licenses your Studio instance. |
CONNECTIONSTRING | Automatically connects the Robot to Orchestrator on-premises using the connection string while also installing it. Please note that the following are required: the WindowsAuth.Enabled parameter from the UiPath.Orchestrator.dll.config file has to be set to true the WindowsAuth.Domain parameter has to be set to a valid domainthe Service Mode Robot a Standard Machine configuration has to be in place. ![]() CONNECTIONSTRING can only be used with Orchestrator v2020.10. |
CLIENT_ID and CLIENT_SECRET | Automatically connects the Robot to Orchestrator using client credentials while also installing it. Example: UiPathStudio.msi ORCHESTRATOR_URL=https://demo.uipath.com/company/tenant/orchestrator_ CLIENT_ID=1234-abcd-1ab2-cd32-1111 CLIENT_SECRET=2143ndafj32k |
CHROME_INSTALL_TYPE | Allows you to choose the installation method for the Chrome extension. This parameter requires the installer to run with admin rights. If it's omitted, the most appropriate installation method is selected automatically. It supports the following options: POLICYOFFLINE - The Chrome Extension is automatically installed per system via the Group Policy Offline method, the equivalent of calling the /Chrome-Policy-Offline command using the SetupExtensions tool.POLICYONLINE - The Chrome Extension is automatically installed per system via the Group Policy Online method, the equivalent of calling the /ChromePolicyGlobal command using the SetupExtensions tool.MANUALPERMACHINE - The Chrome Extension is installed for all users, the equivalent of calling the /ChromeGlobal command using the SetupExtensions tool.NATIVEHOSTONLY - Only the Native Messaging Host component (ChromeNativeMessaging.exe ) is installed, the equivalent of calling the /ChromeNativeHostGlobal command using the SetupExtensions tool.Note: The old installation methods names ( STORE , GLOBAL ) are kept for backwards compatibility. |
EDGE_INSTALL_TYPE | Allows you to choose the installation method for the Edge extension. This parameter requires the installer to run with admin rights. If it's omitted, the most appropriate installation method is selected automatically. It supports the following options: POLICYOFFLINE - The Edge Extension is automatically installed per system via the Group Policy Offline method, the equivalent of calling the /Edge-Policy-Offline command using the SetupExtensions tool.POLICYONLINE - The Edge Extension is automatically installed per system via the Group Policy Online method, the equivalent of calling the /Edge-Chromium-PolicyGlobal command using the SetupExtensions tool.MANUALPERMACHINE - The Edge Extension is installed for all users, the equivalent of calling the /Edge-Chromium-Global command using the SetupExtensions tool.NATIVEHOSTONLY - Only the Native Messaging Host component (ChromeNativeMessaging.exe ) is installed, the equivalent of calling the /Edge-Chromium-NativeHostGlobal command using the SetupExtensions tool.Note: The old installation methods names ( STORE , GLOBAL ) are kept for backwards compatibility. |
DISABLE_SECURE_XAML | Allows you to disable security of XAML files for Robots installed as a Windows service. Unsecured XAML files allow users to read and modify the process files and logic.It supports the following options: 0 - The default option. When used, it enables security for XAML files for Windows service Robots.1 - Disables security for XAML files for Windows service Robots.Note: This parameter can only be used during a clean install or an update. |
SERVICE_URL | Allows you to define the URL of the Orchestrator instance users will connect to using Interactive Sign-In. The provided URL is saved in the uipath.config file, and it's only saved for user-mode Robots. For service-mode installations, the argument is ignored.When running the installer to update from an older version or change your existing installation, this parameter is supported if you are switching the Robot from service mode to user mode (the RegisterService option is not included). |
ORCHESTRATOR_URL | In a clean installation, you can specify the main Orchestrator URL, used for retrieving auto-update information (e.g. https://orchestrator.local/organizationName/tenantName ). |
TELEMETRY_ENABLED | Allows you to disable the usage data collection and can be done at install time for Studio and Robot. Note: This parameter can only be used during a clean install or an update. Telemetry is enabled by default for Studio and Robot. To disable it, use the following value for the parameter whenever you perform a clean installation or an update: TELEMETRY_ENABLED=0 Note: This disables telemetry for both Studio and Robot. If you want to enable telemetry, do not include the parameter, or include it with the following value: TELEMETRY_ENABLED=1 For more information about usage data collection and how to change telemetry settings, see the Opting Out of Telemetry document. |
ENABLE_PIP | Allows you to enable the Picture in Picture functionality of the machine during the UiPath command-line installation. To enable it, use the following parameter: ENABLE_PIP=1 Example: UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages ENABLE_PIP=1 |
INSTALLER_LANGUAGE | Enables you to select the display language of the installer. If not specified, the language settings in Windows determine the installer language. To specify the language, enter the parameter INSTALLER_LANGUAGE=<language_code> . The following options are available:Chinese (Simplified): INSTALLER_LANGUAGE=2052 French: INSTALLER_LANGUAGE=12 German: INSTALLER_LANGUAGE=7 Japanese: INSTALLER_LANGUAGE=17 Korean: INSTALLER_LANGUAGE=1 Portuguese (Portugal): INSTALLER_LANGUAGE=22 Portuguese (Brazil): INSTALLER_LANGUAGE=1046 Russian: INSTALLER_LANGUAGE=25 Spanish (Spain): INSTALLER_LANGUAGE=10 Spanish (Mexico): INSTALLER_LANGUAGE=2058 Turkish: INSTALLER_LANGUAGE=31 |
同期インストールを実行する
インストールの完了後に追加の設定を行う場合は、インストーラーを同期的に実行できます。これにより、インストーラーの完了後に実行する他のコマンドを追加できます。たとえば、インストールに続いて、ロボット接続の設定やフィードの設定ができます。
次のスクリプトでは、インストールを実行し、インストールが成功した場合に実行する他のコマンドを追加できます。
:: Runnning the MSI synchronously
start /wait /b UiPathStudio.msi /Q
:: Assert the exit code and continue accordingly
set "_isSuccess="
if %ERRORLEVEL% EQU 0 Set "_isSuccess=1"
if %ERRORLEVEL% EQU 1641 Set "_isSuccess=1"
if %ERRORLEVEL% EQU 3010 Set "_isSuccess=1"
:: test for success and run follow-up commands
if (%_isSuccess% EQU 1) (
echo "success"
) ELSE (
echo "fail"
)
# Runnning the MSI synchronously
$exitCode = (Start-Process msiexec.exe -ArgumentList "/i UiPathStudio.msi /Q" -Wait -PassThru).ExitCode
# Assert the exit code and continue accordingly
if ($exitCode -in 0,1641,3010) {
# success. run additional commands...
}
else {
# fail.
}
例
以下の例では、UiPathStudio.msi
インストーラーが置かれているディレクトリにいることを前提としています。たとえば、cd D:\UiPathInstaller
などのコマンドでこれを行うことができます。
- Studio のインストールと Robot の Windows サービスとしてのインストールを実行し、アクティビティ パッケージをインストールします。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages
- 現在のユーザーに対してのみ、Studio と Robot をユーザー モードでインストールします。 -
UiPathStudio.msi MSIINSTALLPERUSER=1 ADDLOCAL=DesktopFeature,Studio,Robot
- デスクトップ スイート全体をサイレント モードでインストールします。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages,StartupLauncher,JavaBridge /Q
- ポリシーを使用して、デスクトップ スイート全体と Chrome 拡張機能をサイレント モードでインストールします。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages,ChromeExtension CHROME_INSTALL_TYPE=POLICYONLINE /Q
- サイレント モードで、Studio をインストールし、Robot を Windows サービスとしてインストールし、アクティビティ パッケージをインストールする (すべてを
D:\UiPath
フォルダーにインストール) -UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages APPLICATIONFOLDER=D:\UiPath /Q
- サイレント モードで Robot を Windows サービスとしてインストールし、Orchestrator に接続する -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService CONNECTIONSTRING=https://demo.uipath.com/api/robotsservice/GetConnectionData?tenantId=1 /Q
- Studio のインストールと Robot の Windows サービスとしてのインストールと、2 つのカスタム アクティビティ フィードの追加をサイレント モードで実行します。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService CUSTOM_NUGET_FEEDS="Feed Name1,https://my.custom.nuget.feed; FeedName2,D:\RPA\Activities\Packages\" /Q
- Studio 、Windows サービスとして登録された Robot、ローカル アクティビティ フィードのインストールとライセンスの取得をサイレント モードで実行します。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages CODE=1234567890 /Q
- Robot を Windows サービスとしてインストールし、公式オンライン フィードを無効化します。 -
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService NUGET_OPTIONS=DisableOnlineFeeds
- Chrome 拡張機能をアンインストールします。 -
UiPathStudio.msi REMOVE=ChromeExtension /Q
- Attended ロボットのインストール中に自動更新接続を設定します。-
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService SERVICE_URL="https://demo.uipath.com/myorg/mytenant"
- Unattended ロボットのインストール中に自動更新接続を設定します。-
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,ORCHESTRATOR_URL="https://demo.uipath.com/myorg/mytenant"
- インストール済みの Attended ロボットに自動更新接続を設定します。-
Update the uipath.config or updateservice.json file.
- インストール済みの Unattended ロボットに自動更新接続を設定します。-
- クライアント資格情報を使用する -
UiRobot.exe --connect --url "https://demo.uipath.com/myorg/mytenant" --clientID <clientID> --clientSecret <clientSecret>
- マシン キーを使用する -
UiRobot.exe --connect -url "https://demo.uipath.com/myorg/mytenant" -key <machineKey>
- クライアント資格情報を使用する -
約 1 か月前に更新