Hand on heart, if you want to go to Server 2012/ePO5.3, I'd say if you can, just build a new server, install 5.3 and then import the settings over from 4.6.
But if you have no other option than to go through the process, I'd go for updating the to 2012 first, get all config/updates/patches out of the way and then do the ePO upgrade.
McAfee's product download pages that you can access with your grant number have great install and best practice guides for ePO, helped me a lot when getting our new server up and running.
Thanks a bunch, chrisakinika! That does sound like the best solution. If I could just ask a few more questions...
It looks like this might be the article I need for moving computers to the new server. Do the agents get updated with the new server after they've been migrated?
Also, will I need to migrate the SQL database to a new one? Or can the old one be used?
That first guide works well if you have both old and new server booting working side-by-side, which may not be relevant in the case of an upgrade.
I can only really talk of my experience, but when I did the upgrade here I basically started from scratch; new ePO server build, new SQL database, and then deployed new agents to all the endpoints. It took a few days post-install for tweaking and catching straggler endpoints, but meant that everything was on the same level and there were no hang-over setttings from the previous ePO that may have caused issues further down the line.
As far as I'm aware you can use the old SQL database and just migrate it, but again, given circumstance, it may be better to create new.
do you have your steps documented? Would you mind sharing your infomations? - I'm about to going the same way: New OS. New ePO. New DB. But keeping my old settings, policies, structure and tasks
Would be great.