Hello,
I have been developing robots for the past few months at a company for customer service. Long story short, we develop on our local machines and then deploy the process via orchestrator to the VMs. Thus, these robots llive in the VMs and are not citrix based. Anyways, I had a process running for a few days now, no issues, in the VM. Then suddenly today, it could not find a simple home menu selector. So I pull the exact code from the VM to my local machine, and it finds it just fine.
If anyone has any insight on this, it would be much appreciated. As we have had many inconsistency issues when pushing our processes to the VMs.
1 Like
Hi @developer120
Have you try this link ,Might be helpful to you!
Virtual Machine Automation =VM Automation
cheers 
Happy learning
2 Likes
Thanks for the reply, however we do not use citrix methods. We have the bot actually living in the VM! We develop the process on our local machines, publish the process to Orchestrator. We then have the robot tray in the VM download the most recent process, and then it runs the process in the VM through a schedule trigger of Orchestrator.
1 Like
Hello,
Is the VM locked after a while ?
If the session is locked, Windows don’t create user interface anymore, so the robot is “blind”…
I’m facing the same issue (with Citrix mainly in my case), I disabled all kind of automatic locking (screensaver, auto lock from Windows 10 and so on…) and redirected the mstsc session to the console to keep the session open.
But I don’t use Orchestrator, so it’s a little bit DIY… I think you can instruct Orchestrator to open a remote session automatically to avoid the session lock issue.
1 Like
Hello!
Not to my knowledge, as we have many other bots running for much longer periods of time without issue. Good thing for me to check though, I will look into it. Thanks!
1 Like