Building a new EPO server

[nosrevlah]

I am planning on building a new server for EPO. This time I am going to have EPO and the database on the same box wereas before I had the database residing on a different box. My question is, If I build this new server and name it the same as the old one, will I still have to re-deploy the agents to all my machines or will they communicate with the new server?? I am not sure if the agents use the GUID from the server for communications. Any help on this would be greatly appreciated. Thanks!

 

[cixelsydmai]

From my experience, if you build the new server, give it the same IP address and the same name as the old server, same ports for agent communication and so on, you should see the software pick up the agents slowly as they try to communicate with the server.
To speed this process up, make sure you export your EPO database from the old server, and import it into the new one, once you have it all set up.
Reimporting the database will save you all policy and task creation time, along with restoring any OUs you may have created in your directory. The only thing I found you have to recreate are your distributed repositories, if you use those.

To Back up you current ePo database, log into your ePo server, and go into the ePo folder (usually C:\program files\network associates\epo\3), then run the dbbak.exe, to create the backup file. Once you got the new server all set up, simply import the database with the same program, and that should restore it to what it was before.

Hope that helps,

Sven

 

[nosrevlah]

Thanks for the quick response. I will build this thing and let you know how it went. Thanks again.