Before using Robotic Process Automation, there are a few things to check and configure inside of your desired bot environments.
Software Requirements
- Preferred Windows Operating System (64 Bit)
- Windows 10
NOTE: To have the bot closely simulate a typical end user’s environment, Windows 10 is highly preferred for bot deployments
- Windows 10
- Other Supported Operating Systems
- Windows 8.1
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2016
- Microsoft .NET Framework 4.6.2 or above
- Microsoft Windows Media Foundation Feature
Hardware Requirements
- Machines should either be physical standalone computers (laptops or desktops) or virtual machines
- Machines must be fully independent and able to be restarted on demand
Machines should not be running "Terminal Services" user sessions or other "Mission Critical" services. - Dual-Core CPU
NOTE: If using cloud-based virtual machines, CPU cores must be dedicated. - 8GB Memory or more depending on integrations
- 60GB available hard disk space
User Account Settings
A bot runs as a logged-in Windows user that will need a few specific settings configured.
- Elevated rights sufficient enough to perform system reboots
- A password that never expires
Windows and Group Policy Settings
The user account configured above is required to be logged in 24 hours a day, 7 days a week, so that it can perform tasks at any time. Due to this:
- All screensavers, inactivity timeouts, sleep, and hibernation settings are required to be disabled
Group Policy Settings for this Configuration
Configuring using the steps below will ensure your Windows group policy settings will not interfere with your bot performing work.
- Computer Configuration > Windows Settings > Security Settings >Local Policies > Security Options
- Interactive Login: Machine Inactivity Limit: 0 Seconds
- Network Security: Force logoff when logon hours expire: Disabled
- Computer Configuration > Administrative Templates > System > Power Management > Sleep Settings
- Allow Standby States (S1-S3) When Sleeping (plugged In): Disabled
- Specify the System Hibernate Timeout (plugged In): Enabled at 0 Seconds
- Specify the Unattended Sleep Timeout (plugged In): Enabled at 0 Seconds
- Computer Configuration > Administrative Templates > System > Power Management > Video and Display Settings
- Turn off the display (plugged in) : Enabled at 0 Seconds
- Computer Configuration > Administrative Templates > Windows Components >Windows Update
- Configure Automatic Updates: Enabled
- Configure automatic updating: 4 - Auto download and schedule install
- Install during automatic maintenance - Checked
- Scheduled install day: 0 - Every day
- Scheduled install time: Any time outside of business hours
- User Configuration > Administrative Templates > Control Panel > Personalization
- Screen Saver Timeout: Enabled at 0 Seconds
- Configure Automatic Updates: Enabled
Firewall Settings
Outbound access to the following addresses must be allowed.
- *.klake.io or *.knowledgelake.io (depending on your URL)
- *.servicebus.windows.net
- *.blob.core.windows.net
- *.table.core.windows.net
Security Applications
If you have a security application blocking newly installed programs, you must whitelist the KnowledgeLake Commander directory here:
- %programfiles(x86)% \Ratchet-X Desktop Integration
Additional Production Environment Requirements
These steps are not required for development environments but will be important to perform in production environments.
To encrypt your bot user's credentials to allow the bot to automatically log in after a reboot:
- Navigate to C:\Program Files (x86)\KnolwedgeLake Desktop Integration\Bot Gateway and run AutoLogon.exe
- Enter your Bot user's username and password.
To ensure user sessions are properly reset after a remote desktop session, configure the following scheduled task:
- Search for an open the Windows Task Scheduler.
- Click Action and Import Task at the top of the Task Scheduler window.
- Navigate to C:\Program Files (x86)\Ratchet-X Desktop Integration\BotGateway and select RedirectToConsole.xml.
- Click Open.
- Under the General tab, click Change User or Group...
- Enter the credentials for your bot user and click OK.
- Navigate to the Triggers tab and click Edit... on the trigger in the list
- Click the Change User... button and enter the same credentials as step 6.
- Click OK on all 3 windows to complete configuring the task.
Comments
0 comments
Please sign in to leave a comment.