Take a look at this McAfee Knowledgebase article. I think it is what you are looking for.
Please post back if it helps.
Hi Mike, and thanks a lot for your link. I have seen this post already, and unfortunately, it doesn't really answer my question. In this article they write, that you have to change a DNS record to redirect connections from the old server to the new one. On another website I heard, that after transfering the agents and a wakeup call, the clients automatically connect to the new server. Does anyone know what's true?
Plus, I would like to start from scratch on the new server and just export/import all the things I need from the old one, so that I can clean the whole ePO and skip the upgrade step to 4.6.6 which is necessary in order to update to 5.0
Are you wanting to keep your existing agents then?
If you bring up a new server it, by its nature, will have a new IP address so the agents will not know about it. If you change the DNS record to point to the new server and it has the correct Agent to Server key then it will connect and download a new Sitelist.xml with the new server details in it, then you should be able to do away with the domain name redirect and the agents will still talk to the new server via IP or NetBIOS at first then it will, I think receive a new sitelist.xml with the correct DNS entry, if it has not already got it in the previous one, which I believe it should have, either way it will be able to communicater.
As far as the transfering of the agents, I do believe this is possible also, as long as your two ePO servers can see each other, as, as you say when you transfer them over to the new ePO Server they will get the new Sitelist.xml telling them the info of the new server, then on the next ASCI they will start talking to that one instead. I believe thats how it works. Hopefully someone else will post correcting me if i'm wrong.
The third option, if feesable is to have both servers running and slowly deploy the new agent via the new server via the $ share credentials if you have them.
Let me know if thast answers your question.
I have serveral recommendations for this migration but I would make it simple and easy for you as I have tested it bymyself.
ePo 5.0 bundled with a Compatibility tool.This tool does the trick of this whole KB article.
Run this tool on 32 bit machine where you have your old ePO server.
It will creat a zip file on C:\root. This is the file that includes everything you need .
Copy this file on your new 64 bit machine.
Run Compatibility tool again and browse to this file, after it finishes
Run epo 5.0 setup wizard and follow on screen prompts.
Please let me know if this suits to you???
@Mike: Thanks a lot. Yes exactly that's the question, if it would work like you said, this way should work for me.
If there are no problems with it, I would like to keep the old 4.6 agents, if that works with epo 5.0. Does it?
@Alex: Thanks a lot, this tool sounds amazing and I definitely want to try it. And do I have to make this DNS change thing which Mike wrote, or do the clients see the new server and start connecting to it as soon as this installation is finished? I really don't want to make any changes about networking, because I really don't know much about it.
Hi netik, if you still want to transfer computers from the old epo server to the new one I would suggest to de the folowwing:
- From the old ePO server go to system tree->my organization and click on system tree actions->export systems (this group and all subgroups)
- From the new ePO server go to system tree->my organization and click on system tree actions->new systems->
so you'll have all your computers (unmanaged) in your new ePO server using the same tree structure as the old one.
Now you'll have to export/import all your policies to the new ePO server:
- Check all product extensions on the new ePO server as you have in the old server
- From the old ePO server go to system tree->assigned policies->export all assignments
- From the new ePO server go to system tree->assigned policies->import assignments
so you'll have all policies applied to groups/computers on the new ePO server.
Now you'll have to register the olfd ePO server to the new server so you can transfer systems:
- From the old ePO server go to menu->configuration->server settings->security keys and export the master key (the one that usually does not have a 0 next to it)
- From the new ePO server go to menu->configuration->server settings->security keys and import the key
- From the old ePO server go to menu->configuration->registered servers and set a new ePO server (this will be the new ePO server).
Finally you can try to transfer some computers from the old ePO to the new one and see if they are transferred as they should (action->agent->transfer systems).
This worked for me on different servers so it should also work for you.
Agent attempts to connect ePO via
if any one of them is similliar to the previous old epo server then agent will surely make a connection and will download sitelist.xml file.
and Yes Agent 4.6 is compatible with ePO 5.0
migrated zip file will have all the info required by server to locate its Agents.
Above all and it is best practice as well
in ePO under server settings you will find Agent to server communication keys and Repository keys.
Export them and save them.If after upgrade communication fails import these keys into your new epo and it will establish communication with all agents.
There are many options, just dive into the sea and you will learn how to swim
Hi Laszlo G and alex, Thanks a lot.
Ok I think now I'm prepared for that challenge and next week I'll try to do it
The only thing which I just hardly understand is still this whole IP/DNS thing. Call me stupid...but, I'm still not sure how I should do it. So, after I installed the new server, I have to give it the IP address OR DNS Hostname of the old server and turn the old server off, right?