1 of 1 people found this helpful
Is your new server name same as the old ePO server? If not, the clients would ofcourse fail to communicate even after importing the keys from 4.0 server.
If the new server name is the same and you would disjoin the old ePO server before putting your new server online - this should work.
Alternatively, try creating a DNS Alias so that any queries to the old server would resolve to the new server. Once the agents try to connect with the old server, they would resolve to the new server and recieve an updated sitelist.xml containing the spipe entry for the new server.
If you do not have the custom policies on the new 4.5 server the agents would receive the McAfee default policy during their ASCI. So, make sure that you configure the 4.5 server with the appropriate policies before attempting the above.
All said, keep in mind that this is not an officially supported way of doing things.
What is the officially supported method of doing this properly Sailendra?