cancel
Showing results for 
Search instead for 
Did you mean: 

Blue Prism Next Gen

GAVIN.RUDLING
Level 7

Good day Team.

We are new to Next Gen and are battling along moving forward but slowly.

I am bus creating an Automation Task to Logout and Login to a digital worker on Next Gen.

Somehow I got the automation tasks to work, I.E Log Out and Log In. but...

When the digital worker logs in Although the NM can visibly be seen as logged in. In the Monitor, Digital Worker Health, the machine stays offline, until I reboot the digital worker again.

Are there any configurations we have missed or suggestions we can follow?

 

Kind regards

Gavin

3 REPLIES 3

chris.strong
Staff
Staff

Hello @GAVIN.RUDLING

I would expect the execution machine to be logged in, then the Digital Worker software is automatically launched to make the Digital Worker Online, then it can run your RPA processes.

So, if the machine is logging, but you need to manually start the Digital Worker software, then I'd suggest to look at: 

 

Do you have you Digital Worker software setup to automatically start when the execution machine is logged in?

Depending on you IT setup, there are multiple ways to achieve this: 

  • Use a login script.
  • Create a scheduled task using the Windows Task Scheduler to start when you log in to Windows.
  • Add a batch file to the start-up folder.

We have more detailed guidance: Configure Digital Worker to start automatically

Our expert support team are on hand to guide you too.

 

Hope this helps

Kind regards

Chris Strong

SS&C Blue Prism Senior Product Manager

 

Hi Chris, Thank you so much for the info. I believe one of our guys got it working with a workaround, while I was away, But I have concerns with the work around. We had to include credentials into the script of the config file. I will have to investigate this further.

chris.strong
Staff
Staff

Hi @GAVIN.RUDLING 

Credentials within a login script, it's not something specifically required by our software.

Our digital worker software typically runs in the user context of the logged in Windows desktop session.

I.e. Login to the machine as ChrisStrong, the Digital Worker software runs as user ChrisStrong, inheriting the user profile permissions to machine, network, SSO etc,

Snippet of me logging into a machine as user Admin: 

chrisstrong_0-1763142505422.png

Our support team are on hand should you need them.