Issue
This is as of April 2022.
Overview of RPA Central Domain support
- Which do we support?
- AAD - Azure Active Directory?
- NO
- This is a Cloud service that resides natively in Azure (NOT on an Azure VM)
- It is intended to manage Cloud applications. There is NO Group Policy and you can't join a Server or VMs to it.
- User permissions are given to Cloud applications directly (instead of machines).
-
- AADDS - Azure Active Directory Domain Services?
- YES
- This must be deployed on an Azure VM.
- This is better suited to manage On-Prem servers and applications. It is the traditional on-prem Active Directory that is deployed on an Azure VM Domain controller.
- You can also add Group Policy and client VMs to join it.
- Active Directory?
- YES
- This is for traditional on-prem Domain Servers and networks
- AAD - Azure Active Directory?
Additional Information
If using Windows 10 Enterprise multi-session
As long as your VMs are Windows 10 VMs, that are connected to Active Directory or AADDS (but not AAD), it should work correctly.
What is required for individual Windows sessions is that each session must have a UNIQUE combination of UserName + MachineName as that is what constitutes a unique RPA Bot from RPA Central's perspective.
Please see the links below for more information:
https://help.nintex.com/en-US/rpa/Central/Preinstallationchecklist.htm#Review_the_pre-installation_checklist
https://help.nintex.com/en-US/rpa/Central/RPACentralQuickStart.htm
https://help.nintex.com/en-US/rpa/Troubleshooting/Troubleshooting.htm
https://help.nintex.com/en-US/rpa/Central/Installation.htm