1 of 1 people found this helpful
I believe that Agent port (80 and 443) ports are conflicting with IIS. Please confirm this and if it's conflciting then please change as per KBs #: KB51559 and KB66929.
If the problem is conflict with ports 80 and 443 of the IIS, as I can fix it?
thank you very much
You can add a new IP that IIS is not allowed to bind to and then bind apache to it via the apache conf file.
If you're using only 443 on IIS (like we have a WSUS server on the same machine) you can disable usage of port 443 in the apache conf file.
El Archivo se encuentra en Archivos de programa\McAfee\ePolicy Orchestrator\Apache2\conf y son estos dos?
The file is located in Program Files \ McAfee \ ePolicy Orchestrator \ Apache2 \ conf and are these two?
httpd.conf is the file you want
To remove the ability to listen to port 443 do the following;
- In ePO Menu -> Configuration -> Server Settings -> Ports -> Edit
- Change "Agent-to-server communication secure port:" to Disable and click save
- Edit the httpd.conf file locate the line "Listen 443" and change it to "#Listen 443" and then restart all ePO services
To bind Apache to a new IP you need to make sure your DNS name for the ePO server resolves to that IP because you can not change your ePO name & IP without redeploying the agent to all systems.
- Edit the httpd.conf file locate the line "Listen 80" and change it to "Listen 188.8.131.52:80" (184.108.40.206 being the new IP)
- Edit the httpd.conf file locate the line "Listen 443" and change it to "Listen 220.127.116.11:443"(18.104.22.168 being the new IP)
- Restart all of the ePO services and let ePO rebuild the MA files & XML data which will then propigate out to your systems
- This is where the DNS name resolving to the new IP must be the same (or a new DNS name resolving to the old IP) because user machines need to be able to find your ePO server still which it will try to do via name resolution and if that fails IP resolution