UiRobot Service not licensing to Orchestrator (19.10.18) using Modern Robot (Auto provisioned)

Hello!

I wanted to see if anyone has run into this issue before or might have some suggestions on some debugging configuration that could be enabled to troubleshoot it more effectively.

A bit of background I have a private instance (Orchestrator 19.10.18 & Studio/Robot 19.10.4) that is working as expected with a mix of Classic and Modern Robots for Unattended, NonProduction, & Studio connected to a domain using Domain Groups/Users. I’ll refer to this one as the Legacy instance as I am working to migrate to some new infrastructure.

For the migration to the New instance, the design mostly stays the same, the only thing that has been retained from Legacy has been the database as a backup. The database has been restored to a new SQL Server and Orchestrator 19.10.18 is freshly installed.

The issue I am running into when using a Modern Robot is it not being able to license the Robot. The following status are seen.

Connected, Licensing
Acquiring license from Orchestrator...

followed by

Connected, Unlicensed
The operation has timed out.

New

and the Modern Robot is never displayed under Monitoring > Robots

If I go ahead and make an Classic Robot for the same user, The robot is licensed immediately

Connected, Licensed
Robot is connected to Orchestrator

I can switch the same client UiRobot to the Legacy Orchestrator using a Modern Robot, Same Machine Template Key, etc and it connects and licenses without issue.

Legacy

There are no errors that standout in the Event Viewer for Orchestrator or Robot that are not already present whether the Robot connects successfully or not.

I’ve opened a Support Case and waiting to hear back, but thought I would check with the community as well. The only major difference between the Legacy and New instance is the move from Windows Server 2016 to 2019, but as I can connect with a Classic Robot I wouldn’t think there is a change between OS versions that would cause any issues.

Cheers