The procedure would remain same as before. You might want to check the following
- Remove the SEPM from any replication setup with other SEPMs
- Backup the SEPM server certificate
- Backup the existing SQL database using SEPM backup and Restore wizard
- Install an instance of Microsoft SQL Server 2008
- Uninstall the Symantec Endpoint Protection Manager
- Reinstall the Symantec Endpoint Protection Manager configured to use a new Microsoft SQL Server 2008 database
- Restore the SEPM server certificate
- Restore the backup copy of the database
- Reconfigure the Symantec Endpoint Protection Manager database to recognize Microsoft SQL Server 2008 by running Management Server Configuration Wizard
Reference: Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007092722095248
Thanks :-)
The Security Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Security community. Any authenticated Connect member can contribute to this blog.
Comments
One of these days we'll get
One of these days we'll get around to migrating to SQL 2008 and Server 2008 for SEPM. Is there any advantage to doing so--other then the advantages of the new OS and SQL itself?
Eric C. Lukens IT Security Policy and Risk Assessment Analyst University of Northern Iowa
good one
good one
Would you like to reply?
Login or Register to post your comment.