Endpoint Protection

Running Server 2003 with IIS 6.0
We had an issue with IIS so had to reinstall that. Side effect was all the sites were gone and this was anticipated.
Uninstalled SEP MR4 leaving the database and the other file.
Figured was a good time to upgrade to MR4 MP2 Went throught the install process as normal got to the point where it wanted to build a database, the application says there is already a file with this name and if I would like to overwrite, of course I say no, and the installed will not continue, I canceled all the way out of it and the SEP site is now listed in IIS.
Tried running the Management console and it just says failed to connect.
The Symantec services are running.

Navigating to ---------                http://Serveripaddress/Reporting/   --------------  
Gives me an error message -

PHP Warning: Cannot open 'D:\Program Files\extra\php_browscap.ini' for reading in Unknown on line 0

-- This directory does not exist. BTW


My Question --

Is there a proper way to uninstall the management console and reinstall it then having it reconnect to an existing database? If so anyone know the procedure or a link to some documentation?

Any help would be much appreciated.


ThatDude~

Hi,

       You asked "Is there a proper way to uninstall the management console and reinstall it then having it reconnect to an existing database?"...the answer to this is

Before uninstalling the SEPM we need to follow a procedure commonly known as the "Disaster Recovery Document" so that we can take a proper Backup of the database and then restore it after a fresh installation of SEPM. Please follow the link given below.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008081906512748

Since the procedure mentioned in this document is probably not followed we are getting this error.

Please do revert in case of any assistance

Correct.

This procedure was not followed. The database still exists however and was functioning.

Please advice on steps now to recover.


Thanks

ThatDude~

Hi,

       Since the database was not backed up it would be difficult to restore it. You will have to uninstall the SEPM and when prompted remove the database as well. Do a fresh installation of SEPM. Create a new package and deploy it to the clients.

As in difficult then it is possiable.


I reinstalled SEP same version as originally installed. Changed new database name to db.old and then copied my original database to its location. The Embedded database now fails to stay running. How would we restore this.


Restore perhapes is the wrong term.

Since I have the original database I do not understand why it cannot be used.

We would restore from a backup, but I do not have a backup I have the real thing. Having a hard time following why this is not usable.


Please advise

What is your database?

Integrated SEP Database

The only recovery method I am aware of when uninstalling the policy manager is with a backup as the previous post mentioned. Then when the policy manager is reinstalled along and the new database base schema is created, the previous backup from C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\backup can then be applied. Without a backup, I am not aware of any methods to recover in this particular situation. You mentioned that you do not have a backup. I would check the path "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\backup" just to be sure. During the install process, you are allowed to point the backup to another location, so you could have a different path configured. Database backups are in the form of a zip file with a month and date.
 

I have looked and am sure there is no backup. Seems odd that when uninstalling it asks you if you want to leave the database and data files even if they are totally useless.....

It should either not allow you the option to save them or inform you that a backup will be required if the database is intended to be used again. Then you can creat a backup at that point then finish the uninstall.

I agree with you that it does "seem odd that when uninstalling it asks you if you want to leave the database and data files even if they are totally useless".  I'll continue looking into this and let you know  my findings. 

First I installed the Policy Manager using MR4 MP1a and created a sem5 database on SQL Server 2005, created a couple of groups and then uninstalled the PM leaving the sem5 database intact. Upon reinstalling the PM, I was able to reconnect to the same sem5 database on SQL Server 2005 and verfied that the two groups I created earlier still existed.

Next, I did the exact same steps, but this time I created an embedded database, added two new groups, uninstalled the PM and attempted to reconnect to the sem5.db embedded database using the same process I used for reconnecting to the SQL Server 2005 database. There does not appear to be any options for reconnecting to the embedded database. It appears that the "Management Server Configuration Wizard"  is coded to reconnect to the SQL Server and not the Sybase Embedded database.

In fact, in the 5.x version of the product, when you un-installed the PM, it would automatically uninstall the embedded database as well with asking.

I agree that the uninstallation should warn or force the removal of the embedded database.  Maybe you could submit a feature request.

I think you have to look at the bigger picture.  If you grew up with SAV, you had to install the SAV server and a management console.  With SEPM, you're installing both with one setup file.  The console is integrated into the SEPM installation so there is no management console to uninstall (installing a remote management console on another server or client is another story).

I bet that you could restore it.

I bet that if you created a new database using the install manager, then moved the old database overwriting the new database your zshi would work.