Unable to Setup unattended Bot

Help Orchestrator
1

image
image1858×481 60.4 KB

i want to setup an unattended Bot, But unable to setup

2

@satyam_verma

Follow this step-by-step guide on how to set it up.

3

Hi @satyam_verma,

You can find detailed steps in this video to setup an unattended robot.

Cheers!

4

@satyam_verma Hi Satyam,

From the screenshot, it looks like you have already assigned 1 unattended runtime, but the License Status is still showing red. I would check that part first.

You can try the below steps:

  1. On the machine LCC45, open services.msc and make sure the UiPath Robot service is running.
  2. In Orchestrator, go to Tenant → Machines and verify that LCC45 is connected correctly with the right machine template.
  3. Check that the machine template has 1 Production/Unattended runtime assigned and that the tenant has an unattended license available.
  4. Go to Tenant → Manage Access and check the user/account that will run the bot. Make sure Unattended Robot is enabled for that account.
  5. Verify the Windows credentials configured for the unattended user. On the machine you can run:

whoami

This will help you confirm the correct domain/user name, for example:

LCC45\ADMIN

  1. Make sure both the machine and the unattended user/account are assigned to the same Orchestrator folder where your process is created.
  2. Then check Monitoring → Machines. The machine should be connected and licensed before you start the unattended job.

After that, publish the process and try starting it from Orchestrator → Jobs.

From your screenshot, I would mainly investigate the red License Status first.

If possible, share screenshots of Tenant → Machines and the unattended user configuration (Dont disclose password/machine key)

5

Hi @satyam_verma

that tutorial @ashokkarale shared covers the setup end to end, it was a great tutorial from Mukesh one of the easiest tutorial, worth following it in order rather than jumping around :slight_smile:

two things that usually trip people up and are easy to miss, the windows credentials on the machine have to be the exact account that logs into that machine (domain\user or machine\user), and if you get an error about the interactive session, thats about the machine being able to log in on its own, so RDP sessions left open or a locked screen will break it even with everything else configured right

if there are other issues besides the setup, tell us where exactly it is not working, and what error shows on the job, easier to point you to the right part

hope this helps as well with the other contributions in the topic