Host id is changing when i run in unattended mode

Help Orchestrator
,
1

Hi Team,

Host id is changing when i run the job from orchestrator to
NT Authority/Local service

Regards
Anusha

2

@anusha2

Did you select any host id? If not it would choose automatically
Cheers

3

  • To use credentials specified in Orchestrator, you need to configure the UIPATH_HEADLESS_WITH_USER system environment variable on the robot machine and set the value to True .

  • Then you need to restart the UiPath Robot service from Start → services.msc.

  • Log out from the Robot account.

  • Schedule the process from Orchestrator.

More details here: https://docs.uipath.com/robot/standalone/2023.4/user-guide/background-process-automation#running-background-processes

1 Like
4

Hi Marian,

Will setting UIPATH_HEADLESS_WITH_USER to ‘True’ impact foreground processes that interact with the UI?

Thanks

5

I didn’t hear this parameter to impact the foreground processes.
Double check by yourself.
Add that env variable, restart the robot VM.
Try to run the foreground process.

Let us know the behavior.

1 Like
6

Hi Marian,

I implemented the approach you suggested, where the Orchestrator credential is configured as the host identity. However, I am still unable to access files within Session 1 (the user’s session); instead, the files need to reside in Session 0 (Windows session). Some of the functionalities through the configured account are working as expected (Ex: Send outlook mail), but activating this variable does not appear to affect the foreground processes.

I have two questions regarding these background processes:

  1. Given that files need to remain in the Windows session, will there be issues if I select the robot from a pool? Specifically, do background processes require scheduling on a particular machine under a designated robot account to ensure consistent access?

  2. I scheduled both foreground and background processes simultaneously in Orchestrator, but the background process remained pending until the foreground process completed. Shouldn’t the background process be able to run concurrently with the foreground process?

Thank you

7
  1. Check if that file is having Full Control to Everyone and is accessible by the robots. Also, accessing the same file at the same time, it may be locked.
  2. No. Only one at a time. You can run multiple background jobs at the same time.
8

Hi Marian,

Thanks for your response.

I think I didn’t make my first question clear. I should clarify that I am currently not specifying a machine in the “Execution Target” in Orchestrator, allowing the robot to pick any available machine from the pool. However, since the configuration file needs to remain in a specific Windows session directory (e.g., C:\Program Files (x86) or C:\Windows), it seems I’d need to assign the process to a specific machine to ensure consistent file access.

Also I’m not going to run the same process concurrently on other machines which access same file

9

In your case, you will need to provide at the execution the VM hostname also.
If that config file ( e.g., C:\Program Files (x86) or C:\Windows) is not changed during the execution and is static, you can place it on all the machines and then you are not locked only with one machine.

Also, if you don’t need all the data from that config file, maybe you need to reconsider the approach and use Assets and Data Service while storing and retrieving needed values from the config file.

1 Like