This content has been marked as final. Show 5 replies
Just posted above your entry. Cnn't help you with an answer but..
See the same thing and for me found the computer reports back to the old 3.6 server that is still online. I could delete the agent, send agent install from 4.0 server and have the box show up on the 3.6 server.
Can you hit the logs http:\\name:8081 ? If so then an agent exists even if it is not reporting back to the 4.0 server. I even took down the 3.6 server but the agent still tries to contact it rather then the new 4.0 server
Just got off the phone/webex with McAfee about my problem.
After quite some time checking all the obvious things, it turned out to be a corrupted Framepkg file created on the new server; it had some weird IP address that some clients were trying to contact. Not the IP address of the old server, but something else entirely.
Not sure why some clients were OK with the Framepkg and others were not, but after shutting down all the McAfee services, deleting the Frampkg files, and restarting the services (ePO recreates the Framepkg files), then trying the whole "sent the agent, wake up the agent" for my problem clients, that seems to have fixed the problem. They can now communicate with the server fine.
I'm going to try moving another "test group" of 20 or so clients tomorrow, from the old server to the new one...we'll see how this goes.
Can I know what version of virtual machine you are using? Thanks
on Virtual machine VMWARE v. 4
What will be the problem?