1. AD orchestration, the cx is getting the error below

com.freshworks.freshorchestrator.core.exceptions.FlintBitRunException: Exception occurred for connector: winrm with message: Timed out after waiting 240000(ms) for a reply. address: __vertex.reply.a2d015bc-116b-4531-9f98-48542b20e748, repliedAddress: com.freshworks.freshorchestrator.connector.run.winrm

Sol: Historically, we've had another customer with a similar issue using PowerShell, where we saw that the responses were taking 5 mins for the command that's run. We don't accept anything post the 4 minute mark. Support ticket for reference: https://support.freshdesk.com/a/tickets/13329693

The customer had made changes to their infrastructure that lead to a faster response time, resulting in the orch node working. We're not sure what change the customer did, but it was on their server and network infrastructure that it was done. You can see that they've mentioned the same here: https://support.freshdesk.com/a/tickets/13185085

As a debugging step, please check if the OSR is installed on a server with the recommended specs. Setting up the Orchestration Server : Freshservice. 

Also ensure the OSR server and the AD are connected to the same network with good internet connection speeds between them. Installation Guide for Microsoft On-Premise Active Directory Orchestration App : Freshservice

2. Unable to install the orchestration server using local and domain admin credentials.

Sol:

3. Orchestration Server is Offline

Unable to contact the Server, Please make sure the  Server is Up and running and not offline.

https://support.freshservice.com/en/support/solutions/articles/50000003393-troubleshooting-guide-for-orchestration-server-issues#:~:text=Common%20Issues%20when%20Orchestration%20Server%20is%20Offline&text=You%20need%20to%20restart%20the,was%20generated%20on%20Freshservice%20Instance.

Sol:

All the other issues are mentioned in the article: https://support.freshservice.com/en/support/solutions/articles/50000003393-troubleshooting-guide-for-orchestration-server-issues