This article provides information about how to change the system information listed below:
- IP Address
- NetBIOS name
- Fully Qualified Domain Name (FQDN)
McAfee Agent (MA) uses any of the above to communicate with the ePO Server. If you change any one of the settings, the agents communicate with the ePO server using one of the properties that hasn't changed.
Example
- If you change the client IP address, the agent continues to communicate with the ePO Server through the NetBIOS Name or FQDN.
- After the agent successfully connects to the ePO server, it downloads an updated SiteList.xml from ePO. The file contains the current information and contains the new IP address from the ePO Server.
- But, if you change the Hostname of the ePO Server, the Agent connects to the ePO Server using the IP Address. The agent downloads an updated SiteList.xml file with the new Hostname.
To change all agent-contact information
- If you need to change all of the agent-contact information, we recommend that you change the FQDN first.
- Use the same IP address so the MA on the end nodes can communicate to the Agent Handler (AH) or the ePO server using the last known IP address. After successful communication, MA will update the new FQDN of the server. After all systems communicate successfully using the IP address, you can change the IP address of the ePO Server, because MA communicates through the new FQDN.
To update ePO with the new property information, restart the ePO services:
- Click Start, Run, type services.msc, and click OK.
- Right-click the service below, and select Restart:
McAfee ePolicy Orchestrator Server
- Close the services window.
NOTES:
- If you change all three items at the same time, the client-server communication fails because there's no method to contact the ePO Server. To restore communication, revert either of the properties to the previous value or modify the DNS records to redirect the traffic. This action allows the agents to connect to the ePO server and download the updated sitelist.xml file.
- After you change the NetBIOS name and FQDN, you must regenerate the ePO Server Certificate. For details, see KB90760 - How to regenerate the certificates used by the ePO server service.
Changes on the SQL Server:
- No additional changes on the SQL Server are required.
- If you have the SQL Server on the same server as ePO, review the Database Server Name.
IMPORTANT: Make sure that this field is updated so ePO can connect to SQL.
Changes on Remote AHs:
If you change all server property information, the AH can't connect to the ePO Server.
To update the ePO server information for the AH, modify the following Remote AH settings:
- On the AH server, find the AH folder you extracted from the ePO software installation package.
- Double-click Setup.exe. The AH InstallShield wizard runs.
- Click Next.
- On the Program Maintenance dialog box, click Modify.
- Configure the following settings:
- Type the new Computer name or IP Address of the ePO server with which the AH must communicate.
- Specify which port to use for the agent handler-to-server communication. The default port is 8444.
NOTES:
- When you use the default port, it enables the AH-to-server communication to be performed using only port 8444.
- You can optionally specify port 8443. Port 8843 is the console-to-application server communication port. But, doing so requires that port 8444 remains available for the AH communication.
- Type the ePO administrator username and ePO administrator password. The user must have global administrator rights.
- Click Next to use the ePO administrator credentials to access the database.
NOTE: The credentials you use must be assigned the appropriate SQL Server role and permissions.
- Configure the credentials to access the database, and then click Next.
- Click Install.
- After installation completes, enable your remote AH from within the ePO interface.