Timeout when deploying Windows Agents from Agent Manager

Question

When I use the "deploy agent" wizard to select Windows server to deploy agents to, the process works find all the up until I press "deploy agents', I see the words "connecting" in the status bar, but eventually it times out.

This symptom occurs almost every time. It worked once when I selected 4 nodes, but generally I'm selecting 40 - 70 hosts to deploy the agent to. To recap
 Select "Manage Agent" 
 Select "add agent"
 Select "Deploy the agent on my network" 
 Select 20 servers currently monitored with WMI polling method.
 Click Next
 Wait for credential test to complete successfully
 Select "Deploy Agents" 
 Browser says "Connecting"
 Browser returns message
 Unexpected Website Error

Request timed out.

Web console banner:
 Orion Platform 2016.2.100, WPM 2.2.1, IPAM 4.3.2, SRM 6.3.0, VNQM 4.2.4, NCM 7.5.1, NPM 12.0.1, DPA 10.2.0, QoE 2.2.0, NTA 4.2.1, IVIM 2.1.2, SAM 6.3.0, NetPath 1.0.1

aLTeReGo · Answer

ikomrad​, the 'test' button simply validates the credentials provided. It cannot verify the permissions without actually trying to deploy the agent itself. If you're having intermittent success deploying the agent I wonder if you might be deploying the agent over a WAN connection that may be timing out. The 'push' process uses SMB/CIFS and WMI to deploy the agent to Windows hosts. Unfortunately neither of these protocols are very latency friendly, and WMI itself doesn't handle NAT very well at all.

I would recommend reducing the number of simultaneous agent deployments to see if that improves reliability. If it does not, you may need to use alternate means of deploying the agent en masse, such as Group Policy or a package management solution like SCCM or Patch Manager. While the least efficient, you can also manually install the Agent.

FormerMember · Answer

I'm not having any problems with permissions or access as I only deploy to system that pass the access test. The process times out most of the time, completes successfully on occasion.

amarnath_r · Answer

Please verify the below,

The account used for remote deployment must have access to the administrative share on the target computer: \<hostname_or_ip>\admin$	emp

User Account Control (UAC) must either be disabled, or the built in Administrator account must be used (not a domain account!)

Open Ports Requirements for Remote Deployment from the Orion Server:

135: Microsoft EPMAP (DCE/RPC Locator service). This port is required to be open on the client computer (Inbound) for remote deployment.

445: Microsoft-DS SMB file sharing. This port is required to be open on the client computer (Inbound) for remote deployment

I always use to deploy up to only 10 agents max each time.