ePO Agent on custom port?

[mordrin]

Is it possible to run the ePO agent on a custom port number instead of the default 8081?

During our deployment of the agent, we encountered a port conflict on a few servers running Interwoven OpenDeploy.

The server in question is running Windows NT 4.0 SP6a and using ePO Agent v2.5.1.213.

 

[Eyas]

Hi

There is an option in your ePO-server under server settings that allows you to control the port of the agent wake-up calls. I'm uncertian how it works but it might be worth a shot. I would think that the setting will affect all of the computers controlled by the ePO so tread carefully.
I had a look in the manual but it only refers to it as an wake-up setting. Documentation is however not what NAI do best;-)

HIH

/EYAS

 

[AVChap]

Yes you can. In the server settings (as mentioned) once you change this, the information will be taken in by the agents once they connect back. You can now do a wake-up call on the new port.

HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation

 

[FCCC]

I have the same problem, but my Server Settings is grayed out. Any help why mine was grayed out.

Thanks.

 

[AVChap]

For you to do this, you need to be logged in as Admin first, then you can change the Agent-Wake-Up-Call (AWUC) port, NOT the Agent-to-Server-Communication (ASC) port.

AWUC, by default is port 8081, which you can change anytime. ASC, which runs on port 80 by default, CANNOT be changed on the interface. You can only change this DURING INSTALLATION.

Just to clear some confusion ...

HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation

 

[sunt]

I have done a test on changing the HTTP port from 80 to something else after the installation.
What I did is look for files *.ini somewhere in the the epo dir and change the httpport=80 to whatever you like, after restart the service the epo server will be listening on the port you just specified. However, in the epo console -> server setting the http port is still appearing as 80.
This is the way I found to change the http port after installation. Make sure all the agent's siteinfo.ini has change to the correct http port.