when installing an agent via Automation Studio it does show the step "waiting for agent to connect" in the progress bar and then it hangs there.
I can see the agent already in ROC.
Is this "normal"?
We haven't done this very often so far, as we had another issue doing that, but it works now with some infrastructure changes, so we started using this feature.
In the past I saw this issue when the agent node id and the host name was not the same (even if the node id was server1 and the host name was server1.domain.com)
Can this be the case here?
yeah, this might be it, as I entered in the dialog for installing the agent the full qualified name, so "serverA.domain.com" and the hostname has become only "serverA".
I will try it next without the domain in the dialog :-)
ah no sorry, misread your answer haha.
I will check the nimi.conf
hm nope, node id and hostname are the same...but still might be an issue with the domain maybe or the CN, that differs, although only the hostname should be relevant...I keep an eye on it