Both Robots are running on Win2k12R2 fully patched. The first robot is running within an ESX cluster without any issue. The second robot however is acting weird.
I just created this second robot under Virtualbox on my local laptop. This robot I activated fine (basically that is …). It got a license but it doesn’t stay connected. Then it might be re-connected and get its license back. One thing that is weird is the CE Machine this Robot is tied to never updates its installed version. Attempting to run a simple test workflow to this Robot forever stays “Pending”.
I’m going to delete the machine and robot and try creating Win2k12R on VMware Player and see if the Robot behaves better.
Just curious if anyone has seen issues using VirtualBox Windows VMs as Robot VMs ??
The robot status on the VM itself is connected and licensed.
On the VM from the Robot Available Processes menu I can download defined processes and run them fine. However, if I define a Job on CE Orchestrator for that Robot VM, the job goes into a Pending state basically forever.
But just to reiterate about VirtualBox, as much as I love VirtualBox (I use it A LOT with Vagrant), it seems there is something about the networking side of VB that the UiPath Robot Agent doesn’t like. VMware Player is seems to be rock solid in relation to what the UiPath Robot wants/needs on the networking side.