What I have done:
I have configured an unattended tempalte and got the client id / sec id. Installed unattended assistant with studio.
I always get the same error with the errorcode 1002 (on new machine, new template, new client id, etc).
The olny solution was to log in to the windows machine with another (unattended) user account and try to connect (as service).
I wonder as: Robot Service will never know “who” populated the credentials for an unattended assitant.
What we have not checked, if the user realy needs to an user which is configured in the orchestrator, or if the big change was, that the AD administrator was not able to obtain a token, but a local admin was. What I mean is: why user A can get the yellow light, saying: connected as service, and user B gets this error message?
If this is something with firewall or proxy: we can with both user accounts get a licence for using studio (via the logon button).
The version we tried is 25.10 (where we again use proxy.json)
This is on the orchestrator:
