Skip to main content

Hi everyone,

We’re experiencing an issue in our Control Room where the Deployment Settings for some devices are automatically switching from "RDP" to "Regular".

We haven’t made any manual changes, but this setting seems to revert on its own quite frequently. Due to this change, bots that rely on the RDP configuration are failing to execute properly.

  • Why this automatic switch might be happening?

  • Any suggestions to lock or enforce the deployment type to RDP?

Any help would be greatly appreciated! Thanks in advance.

 

 

That’s an interesting question, Charan 3219 !

I think the following community members may be able to help 

@Tamil Arasu10 

@SakthiVel 

​

​@Charan 3219 

I wanted to share a finding that might help those experiencing issues where the Deployment Type in the Control Room keeps switching from "RDP" to "Regular" unexpectedly.

What’s Happening?

If your Bot Agent is installed with the "User-specific" installation type (e.g., installed under C:\Users\<Username>\AppData\Local\AutomationAnywhere), the Control Room automatically sets the following:

  • Device Type: "Single User" (since the installation is tied to a specific user profile).
  • Deployment Type: "Regular" (bots run in the user’s active session using the device’s native resolution, without RDP).

This can cause the deployment type to revert to "Regular" even if you manually set it to "RDP", as the user-specific setup doesn’t support RDP sessions by default.

Why This Matters

  • Bots will execute only in the context of the installed user’s session.
  • If your bot requires an RDP session (e.g., for consistent resolution or unattended execution), this setup will cause execution failures.

How to Fix It

  1. Check Your Installation Type:
    • On the device, verify the Bot Agent installation path. If it’s under C:\Users\<Username>, it’s user-specific.
  2. Reinstall Bot Agent for All Users:
    • Uninstall the Bot Agent.
    • Run the Bot Agent installer as Administrator and select "Install for All Users" (this will install it under C:\Program Files\Automation Anywhere\Bot Agent).
    • Re-register the device with the Control Room.
  3. Update Control Room Settings:
    • Go to Control Room > Devices > Edit Device.
    • Set the Device Type to "Multiple Users" if your device supports multiple RDP sessions.
    • Set the Deployment Type to "RDP".

Let us know if this helps; otherwise, we will further investigate to identify the root cause of the issue

 

Reply


Terms & ConditionsCookie settings