Installing TAP Studio and Assistant

Installation

To install the custom build, follow these steps:

1. The TAP Bundle installation kit needs to be unzipped in a location where all Windows users that plan to run unattended bots have full read/write privileges (for reference, we'll assume that we'll be installing to C:\Tailent\TAP for this exercise). This can be downloaded here: https://tailent-share.s3.eu-central-1.amazonaws.com/Orch/TAP_Studio_24.10.1016.zip Note: This only needs to be done once for all users.

2. Orchestration under TGA requires that TAP Assistant be running under each target Windows users' session. This can be achieved by setting up a Windows Scheduled Task:

   a. Start Task Scheduler with Administrative rights b. Right click "Task Scheduler (Local)" and select "Create Task..." c. Set the name to "TAP Assistant Automated Startup" d. Provide a description (something like "Scheduled task to start TAP Assistant when a user logs on.") e. Click on Change User or Group -> Type "Users" under "Enter the object name to select" and click Check Names -> Click OK

   

   f. Confirm the "General" tab looks like this:

   

   g. Jump to the "Triggers" tab -> Click "New" -> Select "At log on" under "Begin the task:" and make sure that "Any user" is selected.

   

   h. Jump to the "Actions" Tab -> Click "New" -> Select "Start a program" under Action -> Specify the following settings:

   

   Note: Make sure that "Start in" is set without quotation marks and without the last backslash, like in the picture above. TAP Assistant will fail to start if the startup folder is not correctly set. i. Jump to the "Conditions" tab and replicate these settings:

   

   j. Jump to the "Settings" tab and replicate these settings:

   

   Note: it's important to set the "Run a new instance in parallel" as this will enable TAP Assistant to start individually for each user.

1. Log on with each target Windows User to make sure the scheduled task runs correctly and use this to also login into your TAP Account:

   

   Note: TAP Gateway Agent relies on each users TAP credentials being set on their respective users' account. If a particular TAP credential is not set, the TAP Assistant will not be logged in into the TAP services and even though the Windows session will be started, the target automation will not run.

2. Under a user with Administrator rights, start "gpedit.msc" and navigate to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> "Create global objects" -> Click Add User or Group You will need to add each of the target Windows users accounts that you plan to use these features on. This is required so that proper communication between the TAP Gateway Agent and the target TAP Assistant process running on that particular user be able to communicate.

   

   In the example above, the user which will be used for this installation scenario is called "Test", and can be seen under RPA-PROD-APP01\Test.