stierankaQ: RDP automation
Hi, I'm testing Robomotion for a real RDP (Windows Remote Desktop) automation task. Once a week I update cusom IS for 4 customers. Manually I connect to each Windows server via RDP, log in, start IS as Administrator, open its Store in IS, install the latest update, go through several dialogs, update database tables, wait for completion and confirm the result (all in IS). I want to automate this unattended on a schedule, with credentials stored securely in Vault. Is this scenario reliably supported? What is the recommended approach: WindowsAutomation StartSession/inRemoteServer, automating mstsc.exe, or installing a Robot directly on each remote server? I would prefer not to install software on customer servers if reliable RDP automation from my PC is possible.
Faik_Robomotion
Sep 9, 2026A: Hi,
Yes, this scenario is supported, but for reliable unattended automation we recommend installing a Robomotion Robot directly on each Windows server.
Windows UI Automation cannot see controls inside an RDP window from the client machine, so automating mstsc.exe means the remote application must be controlled using image recognition/OCR. That can work, but it is more sensitive to resolution, scaling, session state, and UI changes.
With a Robot running on each server, Robomotion can interact directly with the application's Windows controls, wait for dialogs and completion states reliably, and use credentials securely from Vault.
So our recommendation is:
* Best reliability: Robot installed on each remote server.
* No-install alternative: RDP + Image Automation, but with lower reliability and more maintenance.
For a weekly production update process across four servers, we would strongly recommend the first option.
Best,
Thanks, that makes sense. One more question regarding the recommended setup: if I have 4 separate customer Windows servers and install Robomotion Robot directly on each server, do I need 4 separate Robots, or can all 4 Robots be connected and managed under a single Robomotion license/account? They would only run the weekly IS update workflows and would not normally need to run simultaneously.
Yes, you need 4 robots installed.
Technically, 1 robot - a named license entity from Admin Console -> Robots - can be reused, but only from one machine at a time. You would need to disconnect it from one machine before connecting it to another and running the next flow.