Whitelisting Requirements for UiPath Studio and UiPath Robot

Whitelisting Requirements for UiPath Studio and UiPath Robot

Reason and Intention 

The purpose of this guide is to document the whitelisting requirements for UiPath Studio and UiPath Robot in desktop environments where there is strict enforcement of Group Policies that prevent UiPath Studio and UiPath Robot from functioning properly. This document aims to highlight the whitelisting requirements when the following restrictions are put in place: 

 

1. Prevention of any executable (.exe) file from being executed when the file is not residing in “C:\Program Files” or “C:\Program Files (x86)”. 

2. Prevention of extensions from being loaded on Google Chrome and Microsoft Edge (Chromium) 

 

The whitelisting is not something that UiPath Studio and UiPath Robot users are able to perform on their own. Please involve your Desktop Support Team and/or Active Directory Admins as these whitelisting requirements would need to be applied in your Windows Domain Controllers. 

 

Whitelisting Instructions to Allow UiPath Executables 

 

Some IT departments would enforce a Group Policy that prevents any executable from being executed when the file is not residing in “C:\Program Files” or “C:\Program Files (x86)”. This policy prevents UiPath Studio and UiPath Robot from functioning properly because there are required executables that are stored in the User Profile folder (e.g. C:\Users\<username>).  

Listed below are the files that need to be whitelisted so that UiPath Studio and UiPath Robot will have the ability to run the required executables when necessary. 

Some Important Notes 

1. There might be multiple versions of the same executable depending on the number of <package version> subfolders present for each Package on the UiPath Studio/Robot machine. The first screenshot below show that there are 6 versions of the UiPath.OmniPage.Activities package and each of folder representing a version will contain the UiPath.OmniPage.Host32.exe file. The second screenshot, on the other hand, show that there are 5 versions of the UiPath.OCR.Activities package and each of the folder will have the UiPath.OCR.Host32.exe file. 

 

 2. Do note that the list of executables to be whitelisted may need to be expanded if Packages not listed above are used to build an automation project. 

 

Whitelisting Instructions to Allow the UiPath Extension to Run on Google Chrome 

Some IT departments would enforce a Group Policy to restrict any Google Chrome extension from being installed by users. However, since the UiPath Extension needs to be installed and enabled for any automation to be developed for business processes that uses Google Chrome, whitelisting of the UiPath Extension needs to be done. 

The following settings need to be introduced in the Group Policy settings to configure the whitelisting: 

  • Administrative Templates -> Google Chrome -> Extensions -> Configure extension installation whitelist 

                     o Value: dkgencfabioofgdmhhjljpkbbchbikbh 

  • Administrative Templates->Google Chrome -> Native Messaging -> Configure native messaging whitelist 

                     o Value: com.uipath.chromenativemsg_v2 

 

Whitelisting Instructions to Allow the UiPath Extension to Run on Microsoft Edge (Chromium) 

Some IT departments would enforce a Group Policy to restrict any Microsoft Edge extension from being installed by users. However, since the UiPath Extension needs to be installed and enabled for any automation to be developed for business processes that uses Microsoft Edge, whitelisting of the UiPath Extension needs to be done. 

The following settings need to be introduced in the Group Policy settings to configure the whitelisting: 

  • Administrative Templates -> Microsoft Edge -> Extensions -> Allow specific extensions to be installed 

                   o Value: dkgencfabioofgdmhhjljpkbbchbikbh 

  • Administrative Templates -> Microsoft Edge -> Native Messaging -> Control which native messaging hosts users can use 

                    o Value: com.uipath.chromenativemsg_v2