Recreating session without service username

Help Orchestrator
1

Hi all,

I am trying to recreate a machine template we have in Orchestrator. It does not have a service username and when we run automations on it, the hostname is the same machine template name.

however, when I create another machine template, get the machine key and connect the new server, it gets associated with one of our NPA.

how can I prevent that to happen?

2

Hello @Giraldo_Juan_P,

What you’re seeing is usually due to either account-machine mappings or the way the robot is connected to Orchestrator.

A machine template itself isn’t tied to a specific user, so if your new server is getting associated with an NPA, it typically comes down to one of these:

1. Account-machine mapping restrictions
Check your machine template settings:

  • Go to Tenant → Machines → Edit Machine Template
  • Look at Account-Machine Mappings
  • If it’s set to “Specific accounts only”, then your NPA is likely mapped there
  • Change it to “Any account can use this machine”

Also, make sure to check at the folder level:

  • Folder → Settings → Machines
    Folder-level mappings can override what you set at the tenant level.

2. Robot connected in user mode instead of service mode
If the robot is connected while a user is logged in, it will associate with that user (your NPA in this case).

For unattended setups like your existing machine:

  • Use Service Mode
  • Connect using Client Credentials
  • Avoid interactive/user-based sign-in on that server

3. Hostname behavior
Normally:

  • Machine = Machine Template
  • Hostname = Actual server name

If both appear the same in your older setup, that’s likely due to how that machine was configured or named, rather than standard behavior.

Thanks,
Karthik

3

Hi @Giraldo_Juan_P

Remove the unattended robot mapping for that NPA from the folder, so the machine template has no user or unattended account linked. Then reconnect the server with the machine key; Orchestrator will not auto‑assign the NPA if no unattended account exists in that folder.

Happy Automation

4

Hii @Giraldo_Juan_P,

Create a fresh machine template and avoid assigning it to any folder initially.
Also double check that the user/robot isn’t already part of the NPA folder.

5

Hi All,

I received the answer offline. During the installation, the target machine was not configured as a Windows Service machine, so Orchestrator automatically associated it with the account I initially used to connect to Orchestrator.

I reinstalled the robot and made sure to select the Windows Service option, which resolved the issue.