1 of 1 people found this helpful
1) Assuming you're talking about a push agent install, this is normal: the ePO server copies the installation package to the target machine using the standard windows admin$ share. If an agent that was being updated by a deployment task - i.e. one where the agent on the client is pulling the install package - the port used will depend on the settings of the repository being used (FTP, HTTP, etc.)
2) At the moment, assuming you're talking about pulling updates and deployment packages from the master repository, then I don't believe this is possible. If you want strict control over the port usage, you could create a distributed repository configured the way you want and configure the agents to update from there instead of from the master.
Thanks a lot for your fast answer!
1) solved then, thanks.
2) What exactly goes through the Server-to-Agent secure communication port then? Because what I see from the logs is when I try to deploy VSE 8.7i over ePO he's always trying port 80 which is the Server-to-Agent communication port and he doesn't seem to try the secure port at all?
Secure port will be used to send the machine's confidential info like name, IP address, domain etc to the ePO server through SSL.
Alright, thanks Hem!
Strictly speaking this is a bit simplistic. All agent-to-server communications (apart from items being pulled from the master repository, and wakeup calls) will take place over either the agent-to-server port, or the agent-to-server secure port, depending on which you have configured. This means all properties, tasks, events and everything else. There is no distinction between "confidential" information and anything else - it all uses whichever port you have configured.