Hi Dears,
I have a little problem. We are implementing Solarwinds in our Datacenters, and we already discover all our VMWare Vcenters via VMAN on a specific Remote Poller.
Then we need to manage all our virtual machines (depending of the customer, the agent (initiated) will communicate to different Remote Pollers)
We have no way to push the agent to the servers, the only flow open is : VM --> TCP17778 --> Remote Poller
I install manually some agents (in the futur, it will be deployed via Symantec Altiris) on different virtual machines, but we always have the same problem :
Agent installation :
manually
Agent appear in this strange status:
the node is automatically created, but state is DOWN
On the node, i try to list ressources :
and also tried via MSI/MST file on another VM and another Remote Poller
I need to go on the agent configuration, and SET AGAIN the user / password
ONLY THEN, the agent status become green, the AGENT/Node name change to the name of the VM, and Node status is green
I don't know, looks like the agent register after installation, but need a second registration to run properly? or maybe the user/password is not correctly send to my different Remote Pollers ?
I hope am not the only customer with VMAN Vcenter who need to manage the node.
I hope anyone can suggest anything about this problem, i will still have some thousand of VMs to manage, and i dont really want to reconfigure each of them 
Solarwinds version 2018.4 SP2, VMAN 8.4, NPM 12.4 agents 2.1.0.666
FWI : i already have a case open with support but it take some time, so hope to find some help here.
Thanks in advance
EDIT : little update, exactly SAME problem with LINUX agents (here on a RHEL server)
EDIT2 :
Once the agent is installed on my server (but in this unknown status, and node created but down), this agent create the all the 10mb log files in less than 5 seconds (really), so happy that the number of logs is limited to 10
(and even after i reconfigure the agent and everything is green, the agent keep writing log file like a crazy with always the same patern (block of +-50 lines))
at the end of this pattern :
19/03/14 17:01:31.028 PID: 6872 TID: 560 [INFO] ewAsyncRpcCommon::ProcessConfigBase::ApplyPolicyXml - failed to get child nodes [version] from policy XML]
19/03/14 17:01:31.028 PID: 6872 TID: 560 [INFO] ewAsyncRpcCommon::ProcessConfigBase::ApplyPolicyXml - config XML was NOT modified by the policy XML
I attached the log file in case of ...
Edit3 : The problem occurs from 3 different Remote pollers (in different vlan etc ...) but everything work FINE if i install an agent that need to connect to the main Solarwinds Orion VIP (we have 2 main pollers in HA)
