- Release notes
- Task Mining overview
- Setup and configuration
- Notifications
- Task Mining
- Additional resources
Command line parameters
You can install or update Task Mining using command lines if you have the task-mining-setup.msi installer. Below is an overview of the available parameters.
-
This package natively supports all
msiexec
commands. -
Administrator rights are required to execute these commands.
Command |
Description |
|
Used for normal installation. |
|
Used for administrative installation |
|
Used to uninstall the package |
|
Used to change the installation directory |
|
Used to install the application with the service URL preset. Default https://cloud.uipath.com (Not available in 22.10) |
|
Install for current user only (default per machine) |
|
List of extensions to install 22.10 - all extensions installed by default 23.4 - Chrome Extension, Edge Extension, Firefox Extension installed by default ADDLOCAL=ProductFeature to skip all extensions |
|
Allows you to choose the installation method for the Chrome extension. It supports the following options:
Refer to Install from Group Policy and SetupExtensions tool for details. Note: The
CHROME_INSTALL_TYPE parameter requires the installer to run with admin rights. If the CHROME_INSTALL_TYPE parameter is omitted, the most appropriate installation method is selected automatically.
|
|
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:
Note: The
EDGE_INSTALL_TYPE parameter requires the installer to run with admin rights. If the EDGE_INSTALL_TYPE parameter is omitted, the most appropriate installation method is selected automatically.
|
Command | Description |
|
The machine will not be restarted after the installation is completed. |
|
The user will be prompted if a reboot is required |
|
The machine will be restarted after the installation is complete |
Below are some examples of adding CLI parameters for the unified installer:
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":false,""useProxyServer"":true}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":false,""useProxyServer"":true}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":true,""username"":""user"",""password"":""pass"",""domain"":""domain"",""useProxyServer"":true}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":true,""username"":""user"",""password"":""pass"",""domain"":""domain"",""useProxyServer"":true}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""usePacScript"":true,""pacScriptAddress"":""localhost:8888/proxy.pac""}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""usePacScript"":true,""pacScriptAddress"":""localhost:8888/proxy.pac""}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":false,""useProxyServer"":true,""bypassList"":""google.com""}"
msiexec /i UiPathTaskMining.msi /qr MSIINSTALLPERUSER=1 PROXY_SETTINGS="{""host"":""localhost"",""port"":12345,""authIsEnabled"":false,""useProxyServer"":true,""bypassList"":""google.com""}"
proxySettings
property in the <installation_directory>/config.json
configuration file.
Below is an example.
{
"serverURL": "https://cloud.uipath.com",
"telemetryEnabled": "1",
"applicationLanguage": "",
"proxySettings": "{\"host\":\"localhost\",\"port\":12345,\"authIsEnabled\":true,\"username\":\"user\",\"password\":\"pass\",\"domain\":\"domain\",\"useProxyServer\":true}",
}
{
"serverURL": "https://cloud.uipath.com",
"telemetryEnabled": "1",
"applicationLanguage": "",
"proxySettings": "{\"host\":\"localhost\",\"port\":12345,\"authIsEnabled\":true,\"username\":\"user\",\"password\":\"pass\",\"domain\":\"domain\",\"useProxyServer\":true}",
}
You can also install the extension for Chrome or the extension for Edge by using Group Policies. This method silently installs the extension and enables it, without requiring user confirmation.
The Group Policy Offline installation method requires that the target machine is joined to a Microsoft Active Directory domain or Azure Active Directory.
It does not require access to the Chrome Web Store/Edge Web Store so it can be used for machines that have restricted Internet access.
If your organization uses Group Policies for browser extension management then the following changes are also required:
-
In the ExtensionInstallForceList policy, add the value for Chrome:
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/ChromeExtension_SelfHosted/extension_manifest_chrome.xml
, or for Edge:ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/EdgeExtension_SelfHosted/extension_manifest_edge.xml
. -
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2
https://clients2.google.com/service/update2/crx
and https://clients2.googleusercontent.com/crx
).
UiPathTaskMining.msi
uses this installation method if its requirements are met and the machine is not joined to a Microsoft Active Directory.
If your organization uses Group Policies for browser extension management then the following changes are also required:
-
In the ExtensionInstallForceList policy, add the value for Chrome:
jfcmnbofjlffnejneillkgbniiidiigd;https://clients2.google.com/service/update2/crx
, or for Edge:aolkfhjgbinoablafekggeglohbacjih;https://edge.microsoft.com/extensionwebstorebase/v1/crx
. -
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2
Refer to ExtensionInstallForceList in the the official Chrome enterprise documentation for more information on the ExtensionInstallForceList policy.
Refer to NativeMessagingAllowList in the official Chrome enterprise documentation for more information on the NativeMessagingAllowList policy.