Scribd
Upload
32 views

Client Install

This document provides an installation readiness checklist for an Automation Anywhere workshop. It outlines the system requirements and software that needs to be verified 1-2 weeks prior and at the start of the workshop, including having the correct version of Windows and .NET installed on the control room VM, plugins installed on the client, and access to target systems and test data. It also includes optional items like installing a bot runner if it will be used.

Uploaded by

jose cardozo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
32 views

Client Install

This document provides an installation readiness checklist for an Automation Anywhere workshop. It outlines the system requirements and software that needs to be verified 1-2 weeks prior and at the start of the workshop, including having the correct version of Windows and .NET installed on the control room VM, plugins installed on the client, and access to target systems and test data. It also includes optional items like installing a bot runner if it will be used.

Uploaded by

jose cardozo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

INSTALLATION READINESS CHECKLIST

The following are verified 1-2 weeks prior and again at the start of the Automation Workshop.
• Control Room installation
 VM meets or exceeds (specs are less than minimimum required as there is minimal load on the Control
Room for a POC)
▪ OS – Windows Server 2012 R2
▪ Memory – 4GB
▪ CPU – 2 Core
 .NET 4.6.1 installed (pre-requisite for AA installation)
 POC Evaluation license installed
 “Developer” security role with development permissions including full permissions for all Tasks, Docs,
Metabots and other development features
 User with Developer role and Development license assigned
• AAE Client installed on VDI or Laptop
 VDI or Laptop meets or exceeds technical specifications as defined in the product Client Installation
Guide
• User
 Must be logged in to the VDI as the user who will login during the POC; typically a new account
created just for bots
 User logged into the VDI has Admin access to install plugins
• Settings
▪ If user does not have Admin access
 Run AA as Admin
 Change Application Path to the user’s directory
 Close AA from the System Tray (lower right corner icons)
 Open AA and login
 Verify plugins are installed under the AA user and Windows user that will be used during
the POC
 JRE path specified
 Advanced Settings – Edit task on double-click is checked
 All plugins installed including
 IE11 (if using IE11)
 Silverlight
 Flex
 Chrome Plugin (Drag & Drop “C:\Program Files (x86)\Automation Anywhere Enterprise
10.5\Client\ChromeExtension.crx” to an open Chrome Browser Window)
 SAP Plugin (if using SAP) – installed from the Installaton Files directory of the
Automation Anywhere software download
▪ Display Settings
 Windows Display Settings in the Control Panel - Scaling is 100% - if larger text is
needed, decrease resolution
 Browser Zoom level is 100%
• Metabots installed including
 Outlook
 SAP
 DateTime
 Arrays
 Excel
 CyberArk
• Applications Installed
 Microsoft Excel
 Microsoft Word
• (Optional) Bot Runner installed on VDI
 VDI meets meets all requirements for the AAE Client noted above.
 AA User is licensed as a Bot Runner
 Create a bot, upload to Control Room, and trigger the bot to run on the Bot Runner from the Control
Room
 Dedicated computer for Sales Engineer to use while on-site (on-site only)
• Target Systems and Test Data
 Login to all Target Systems and click through the process to ensure bot access including the following
systems:
▪ <TARGET SYSTEM A>
▪ <TARGET SYSTEM B>
▪ <LIST ADDITIONAL SYSTEMS AS NEEDED>
 Verify data is available across all systems
• Test systems interaction using
 Web Recorder
 Smart Recorder
 Manage Windows Controls
 Create a bot that captures login credentials for all target systems
o Additional Systems – If using any of the following features, verify the corresponding elements of the checklist
• OCR
 Tesseract installed and working on development client VDI/laptop
 ABBYY installed on development client
• Citrix
 Clipboard Sharing enabled
 Citrix Automation is able to connect to Citrix environment – verify able to send keystrokes to two
or more windows using the window titles
• Terminal
 Connect to each terminal instance using the built-in terminal emulator
• SAP
 Scripting is enabled
 SAP Metabot
• Installed
• Interaction verified
• Microsoft Outlook
 If client is sending/receiving email and uses Outlook as their email client, ensure Outlook is
installed on the development (and bot runner) clients
 Bot has an Active Directory account with email enabled (send a test email and ensure bot receives
it in Outlook)
 Test Outlook integration by running a sample task using the Outlook Metabot

You might also like