A full list of mandatory registry keys or GPO entries for overall Pega RPA infrastructure

Hi,

We are working with our IT team to setup and deploy our newly developed robots in production and searching for the list of mandatory registry keys or GPO entries for overall Pega RPA infrastructure like Robot Runtime, Robot Studio, unattended bots, credential manager, or synchronization components, etc.

I could only find information related to Windows Logon options and Browser extensions. But I believe there are other mandatory and good to have settings like messaging host, etc, but can’t find all of these information at one place. If you have such a list, could you please share, that would be really helpful. Thank you!

BR\Rajesh

@RajeshS17304030

For setting up a complete Pega RPA infrastructure, there’s no single “official” one-stop list from Pega, but you can compile it from documentation and field experience. At a minimum, ensure that the registry and GPO settings allow the Robot Runtime and Robot Studio to start without manual prompts, auto-logon for unattended bots, and proper interaction with applications. This usually means enabling Windows auto-logon keys for unattended VMs, setting registry entries for Pega Robot Runtime (HKEY_LOCAL_MACHINE\SOFTWARE\Pegasystems\Runtime for configuration paths), configuring MessagingHost (HKEY_LOCAL_MACHINE\SOFTWARE\Pegasystems\MessagingHost for ports and URLs), and ensuring the Credential Manager store location and encryption keys are accessible to the bot user account. GPO settings should allow scheduled tasks or services for OpenSpan.Runtime.exe and OpenSpan.Studio.exe to run without UAC interruptions, whitelisting these executables in antivirus policies, and enabling clipboard, drag/drop, and UI automation APIs. For browser automations, set the GPOs or registry keys for Chromium- or IE-based extensions (Chrome: ExtensionInstallForcelist, Edge: ExtensionInstallAllowlist, IE: Browser Helper Objects). Make sure Windows Remote Desktop settings allow console sessions for bots and disable lock screen timeouts. If you use Synchronization Server, its ports should be open in the firewall and the registry should hold correct connection strings. Credential Manager service should be set to automatic, with GPO allowing its access in unattended mode. Also, ensure Event Viewer logging is enabled for Pega services to support monitoring and troubleshooting. While this is the typical baseline, your final list may need to be tailored based on authentication method, bot hosting model (VM vs. physical), and security policy requirements.

@RajeshS17304030 I have not known any specific registry settings you’d need to update yourself. The installers may do so, but unless you fins a specific example, there isn’t a place I know of where you’d need to manually update them. There are group policy settings you need to implement for Pega Browser Extension as documented below, but that is all I am aware of. There isn’t a published list of the registry changes made by the installers that I am aware of. You’d have to speak with Pega support to see if that could be acquired if needed.

https://docs.pega.com/bundle/robotic-automation-r25/page/robotic-automation-r25/supported-technologies/automating-chromium-browsers.html

Thank you @Sairohith and @ThomasSasnett both suggestions were helped us alot.
Here I’m attaching the list that I prepared using the current setup and from the above suggestions. I request you to have a look and recommend if I’m missing any key settings. Thank you!

Pega RPA windows server GPO and Registry settings - Copy.docx (24.4 KB)

@RajeshS17304030I believe this is OK, except that you really should refer to the documentation rather than try to gather in a separate document. Some of the settings here are for the Server Bot Framework or are for the RPA Service. Both of which you may not be using. I do stand corrected however in that there are indeed manual registry settings to make for both Server Bot Framework and for the RPA Service. The group policy things for Chrome and/or Edge are not generally made manually, but instead through group policy.