We have installed ePO 4.5 P3 on a new server and trying to push agents out to existing machines, which have agents installed from a previous ePO server.
I understand why we're getting the problems we're getting (failed to associate IP address and the fact that 'only allow comms from the ePO server in the Agents settings), but what are our options to fix these problems.
I have tried:
Manually copy the SiteList.xml file from a working machine to a non-working machine = fails
Deleting the system from ePO and adding by IP address = fails (as it resolves it to it's DNS name anyway)
Removing the Agent completely and re-installing from the new ePO server = fails
I don't really want to have to re-build all our machines to fix this problem!
Did you export the agent-to-server keys form the old server and import them into the new one? If not, then the old agents will not be able to talk to the new server. Importing the new sitelist is not enough - you need to import the new keys as well.
You can either install the agent package from the new server, which will replace the sitelist and keys, or you can import them locally on the clients by exporting the srpubkey.bin, reqseckey.bin and sitelist.xml from the server, putting them all in the same folder, and then running frminst.exe /siteinfo=<path_to_sitelist.xml>
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.