Resource PC goes offline after logout (BP 7.3, Windows 11 non-domain)

[m.kupplich]

Hi all,

We’re running into a strange issue with our Blue Prism 7.3 setup and hoping someone here might have seen something similar.

Previously, we had our resource PCs running Windows 10 and joined to the same domain as the Blue Prism server. Everything worked fine. Even after logout, the Login Agent was still able to connect and log the machine back in.

Now we’ve started using Windows 11 resource PCs that are not joined to the domain. As long as someone is logged in, the machine appears online in Control Room, and we can run processes without any problems. However, as soon as the logout process runs, the resource immediately goes offline and cannot be reached anymore. As a result, the Login Agent is unable to reconnect or trigger a login.

All relevant ports (including 8181) are open on the firewall. On the older, domain-joined Windows 10 machines, we can still use telnet to reach port 8181 after logout. This tells us that the listener is still running. On the new Windows 11 machines, telnet fails after logout, which suggests that the listener is either no longer running or is not reachable.

Therefore, the problem doesn’t seem to be caused by the Login Agent itself. Instead, the machine becomes unreachable after logout, which prevents the Login Agent from working properly.

Has anyone come across this behavior before? Or found a way to keep non-domain Windows 11 resource PCs reachable after logout so that the Login Agent can still connect?

Thanks in advance for any suggestions!

Best,
Michael

[Afia]

Hi there,

We can check some points together and if they don't work tell me to try others.

Make sure the runtime resource is installed and running as a Windows service:

AutomateC /install /resourcepc

Then go to Services, find Blue Prism Runtime Resource, and ensure:

• Startup type = Automatic

• Log on as = Local System

• Status = Running

Also confirm:

• Port 8181 is open (check firewall rules).

• You're using local user credentials correctly in Login Agent config.

• You're not using Microsoft accounts (use standard local users).

This setup ensures the listener remains reachable after logout, even on non-domain machines.

[m.kupplich]

Thanks a lot for your response!
I’ll double-check the settings you mentioned and get back to you once I’ve gone through everything. I really appreciate your help!

[m.kupplich]

I checked the service setup — it’s all good:

• Startup type: Automatic

• Log on as: Local System

• Status: Running

But here’s the weird part:
On the Windows 11 machine, port 8181 is only open when the bot user is logged in. As soon as they log out, the port is closed — can’t reach it via telnet or anything.
On the Windows 10 machine, port 8181 stays open even after logout, which is why Login Agent works fine there.

So it looks like on Win11, either the listener stops running after logout, or the machine just isn’t accepting connections anymore.

Any idea what could be causing this? Maybe some extra config needed on Win11 to keep the resource PC “listening” even when no one’s logged in?

Appreciate any tips!
Thanks
Michael

[SayeedBinAbdullah]

Hi @m.kupplich

To ensure uninterrupted access to the resource PC, start by reviewing Windows Defender Firewall settings and confirming that an inbound rule allows connections on port 8181.

Firewalls often have security restrictions that block incoming requests when no user is logged in, so explicitly permitting this port can help maintain connectivity.

Additionally, examining Group Policy settings is crucial, as some Windows security policies may prevent network access after a user logs out, especially on Windows 11, where handling of background services differs from previous versions. Adjusting relevant policies to allow continuous network communication might resolve the issue.

Another important step is checking whether the listener process is tied to a user session rather than running as a system-wide service. If the listener stops functioning upon logout, reconfiguring it to run independently of user login—such as setting it up as a persistent background service—can ensure that it remains active and responsive. By addressing these key areas—firewall rules, group policy configurations, and service setup—you can improve the reliability of network connections and maintain seamless operations across different Windows versions.

You may also refer to the post below, as it appears that someone encountered a similar issue, though the specific Windows version is not mentioned.

https://community.blueprism.com/t5/Product-Forum/Login-Agent-in-BP-v-7-3/td-p/120509 

Best Regards,
Sayeed Bin Abdullah