FYI, according to the ePO 4.5 system requirements, SQL Server 2005 or 2008 is required. SQL Server 2005 Express is included and can be installed during the ePO installation if desired.
These aren't step-by-step for your exact scenario, but here's some articles that might be helpful.
Also look at the install guide and release notes for ePO 4.5.
Doesn't look like it will be a "quick and easy" upgrade. You'll also have to consider which versions of the agent and other installed products each version of ePO will support as you consider how to migrate.
It looks like the starting point would be to move ePO 3.6 to the new server, then move the ePO db to a newer version of SQL Server, then upgrade to ePO 4.5.
Message was edited by: jguenrdc : added additional suggestion. on 8/30/10 11:45:10 AM CDT
Yeeesh - I was afraid of this. How about if I just run a completely new installation up, get all my policies & stuff exported from the old one then import them - is there a simple way to change all the agents I have installed out there to report back into a new EPO server?
1 of 1 people found this helpful
I went through the same. I had (still have kicking about) a 3.6.1 ePO.
I setup a new server and deployed the agent via ConfigMgr (SCCM) and now have a Group Policy in place to check the version and install the agent for new machines on the domain. this way i got to upgrade my agents from 3.6 to 4 as well as them appearing in the new ePO (just mentioning some options) (check out the distributing agents to manage systems section in the product guide)
There is also a bit in the ePO product guide that mentions transferring systems to another ePO server- search in the document for "transfer systems" and see if that helps.
Another thing to check is your agent version. It needs to be at least v4.0 and if you have plan to migrate your policies to 8.7, then do it on the 3.6.1 server and export and import those policies into 4.5. I tried on ePO 4.5 (RTM) to migrate the 8.5 policies to 8.7 (if you don't know what i'm talking about search for epopolicymigration.exe) and it didn't work. (may have changed now)
Not sure about the export/import stuff. My suggestions so far are basically educated guesses. We have a very small company and when I went from ProtectionPilot to ePO 4.5, I just did a clean install and set up everything from there.
Thanks for this help guys, much appreciated. I'm way ahead on the client/agent front - every single system I have is Agent 4 patch 3 and VS 8.7i patch 3, so I won't need to do any redeployment - but I would definitely like not to have redeploy the agents if possible.
So, in the end I just did a side-by-side install on a new VM in the correct subnet, manually recreated policies & tasks then pushed the agent out over the top of the old one. Most of them took this fine, a few systems I had to force an install over the top (30 or so) , and even fewer (around 20) I had to manually log on and run the agent install from the framepkg copied to a local drive and forced from the CLI. All in all not too bad - but would have been a major PITA if I'd had a complex environment.#