You can install a new ePO server on the new OS with a new DB.
Then link the server together with the connected server option.
You then can easily transfer policies with the share policy option and transfer clients with the transfer client option.
This will allow you to migrate machines to the new server and migrate them back when things go wrong.
This way you keep your current server almost untouched...
I was not aware of this possibility, but it does not seem to address what I'm trying to achieve. The new server would have to have a new name and IP address to coexist with the old server. I'm probably missing something here...how does this method allow me to retire the old server? As I understand it, all the agents are expecting to see the old server by name and IP address. My intent is to retire the old server. I had assumed that I woul have to build the new server off network and then go through the steps as if it were a "disaster recovery" scenario in order to get a new server up and running. How does this method contribute?
Once all clients are transferred to the new server, you can retire the old server. The only thing that you won't migrate this way is the history reports. Please check the product guide for more information regarding the server linking and the client migration.