Question
Coforge Limited
GB
Last activity: 12 Sep 2024 12:41 EDT
Pega Robotics v22.1, RM 8.24: Is Windows 365 cloud PC (Win 11 OS) supported ?
Hello,
Version: Pega Robotics v22.1.x, RM 8.24.x.
Could you let us know if Windows 365 cloud PC (Win 11 OS) can be used as Robots? Can we run Pega RDA and RPA using Windows 365 cloud PC? Is this tested and supported from Pega pls? If supported, what is the minimum compatible product version we should have?
Regards,
Manojanand Nayagam
***Edited by Moderator Rupashree S. to add Capability tags***
Accepted Solution
Updated: 5 Aug 2024 13:28 EDT
Pegasystems Inc.
US
@ManojanandNayagamAs long as your machine is running a supported Operating System (in this case Windows 11), then Pega Robotics V22 would be supported. Where the machine is hosted from is not really a concern.
One thing you will need to ensure is that the machine stays active and is not suspended if you are running unattended bots. Not all bot operations allow Windows to know a user is present, so depending on what processes you are automating, you may need to make sure your bots do not suspend themselves if they think they are idle.
Coforge Limited
GB
I am getting the following error when starting the robot from robot manager. This happens in both cases (starting by keeping the vdi open as well as closed)
Cloud PC uses MicroSoft Entra ID and not on the local domain. Could you let me know how to fix this?
Error in RPA Service log:
I am getting the following error when starting the robot from robot manager. This happens in both cases (starting by keeping the vdi open as well as closed)
Cloud PC uses MicroSoft Entra ID and not on the local domain. Could you let me know how to fix this?
Error in RPA Service log:
Info | 09/05/2024 04:41:14.755 PM | 14 | MTA | Service | Sending heartbeat. Info | 09/05/2024 04:41:14.755 PM | 14 | MTA | Service | Heartbeat request robot count '1'. Info | 09/05/2024 04:41:14.755 PM | 14 | MTA | Service | NetworkClient - sending POST request to URL 'https://xxx/prweb/api/robotics/v2/heartbeat?type=serviceoperator'. Info | 09/05/2024 04:41:14.880 PM | 14 | MTA | Service | Successfully sent heartbeat. Info | 09/05/2024 04:41:14.880 PM | 14 | MTA | Service | Starting processing START command for Operator ID 'CPC_MANOJ_XXXX'. Info | 09/05/2024 04:41:15.098 PM | 1 | MTA | Scheduler | *** Initializing *** Info | 09/05/2024 04:41:15.148 PM | 1 | MTA | Scheduler | CredentialManagerConfigHelper - 'ApplicationData' is not a folder. Checking for an environment variable. Info | 09/05/2024 04:41:15.148 PM | 1 | MTA | Scheduler | CredentialManagerConfigHelper - 'ApplicationData' is not an environment variable pointing to a folder. Checking for a special folder name. Info | 09/05/2024 04:41:15.148 PM | 1 | MTA | Scheduler | CredentialManagerConfigHelper - Configuration location: ApplicationData Info | 09/05/2024 04:41:15.148 PM | 1 | MTA | Scheduler | Successfully loaded configuration information from: 'C:\ProgramData\Pegasystems\RpaService\RpaService.config' Info | 09/05/2024 04:41:15.210 PM | 1 | MTA | Scheduler | CPC_MANOJ_XXXX - Initialized Info | 09/05/2024 04:41:15.210 PM | 1 | MTA | Scheduler | Combined user name is 'XXXX\XXXX'. Info | 09/05/2024 04:41:15.257 PM | 1 | MTA | Scheduler | Combined user name is 'XXXX\XXXX'. Error | 09/05/2024 04:41:15.288 PM | 1 | MTA | Scheduler | The server could not be contacted. System.DirectoryServices.AccountManagement.PrincipalServerDownException: The server could not be contacted. ---> System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable. at System.DirectoryServices.Protocols.LdapConnection.Connect() at System.DirectoryServices.Protocols.LdapConnection.SendRequestHelper(DirectoryRequest request, Int32& messageID) at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout) at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request) at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties) --- End of inner exception stack trace --- at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties) at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval() at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password) at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType) at Pega.RpaService.Common.UserHelper.GetDomainUserDisplayName(String userName) at Pega.RpaService.Scheduler.LogonEngine..ctor(Process logonProcess, String userName, SecureString password) at Pega.RpaService.Scheduler.LockScreenLogonProcessor.UnlockScreen(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.LockScreenLogonProcessor.Logon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.Main(String[] args)
Pegasystems Inc.
US
@ManojanandNayagam I think you might need to work with support on this issue, as it might be hard to diagnose in an open forum like this. There certainly seems like some access issue as the message is "The LDAP server is unavailable".