Endpoint Protection

Hi,

I've installed The SEPM, I already have a cluster of SQL 2008 and my DBA's configured a DB for me (do the database already exists). I let them know of the required file groups and special permissions mentioned in the documentation.
When I try to setup the SEPM, it fails with the "initialization of database error", I tryed looking for the log file the message mentioned in ...\tomcat\logs\install_log.err and the log file was empty.I thought there might be some sort of a problem with the file, so I deleted it and when I retry the process it does not create the log file at all.
I'm not certain what's wrong, but I think the permissions on the directory are O.K. - not certain what to do next?

What version of SEPM are you trying to install Make sure you are using RU6MP1 (11.0.6100.xxxx )

Are you doing this through RDP session?

If yes then try to install through console session.


Product corruption or failure appears during an installation or migration while using an improperly configured remote session.

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

Is the Database on the same Machine where you are trying to install SEPM?

Check the following article

Title: 'Best Practices guide for Installing the Symantec Endpoint Protection Manager 11 RU5 with a SQL Server 2008 Database'
Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009093006181448

Yes 11.0.6MP1, After restart I found that the file-groups are missing associated files.
I thought the setup will create those, now how should I know which files, size & parameters should be defined for each filegroup.
Is there a scripts that generate it?

BTW, I can't use the New database as my DBA won't allow the application to touch the master database & the rest of the databases (only this specific database).

No RDP session involved, and I mentioned this already - restart solved the log issue.

Try this

Login to the SQL Server Management Studio using Windows Authentication

Right Click on the Server Name/Instance name click properties

Select Security and Change the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)"
to "Mixed Mode (Windows Authentication and SQL Server Authentication)".

Click OK

Under the SQL Server Management Studio expand Security and then expand Logins.

Right Click on "sa" click properties go to Status and change it to Enabled.

Click OK

Again right click on Server name\Instance Name and click Restart.

It will restart the SQLSERVER service and you should be able to install SEPM.

My DBA won't allow it and I've been told that it is not a seperate instance, only a seperate DB (so it will shut the rest of the DB's down).
Beyond that, allowing sa is prohibited by my admin.
In other words, I need to get a script or something to run on the SQL to associate files to those filegroups with the right parameters.
Is there such a script?

How many workstations do you have in the network on which you will be installing SEP Client?

this doc is for SQL 2005 but it should be helpful
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/2fee74b8d1c0cef188257451007a7ded?OpenDocument

~4000 worksations

Any specific reason you want to use SQL?

You can also use Embedded Database that comes with SEPM, which can be used for 5000 Client. This is a suggestion as there are few limitations you using the SQL Server.

~4000 worksations

Since Symantec representative highly recommended us to use SQL, that's what we do.
In the future we might setup 2 server that will backup one each other - and this will be a preperation.

I did the mentioned steps, but still there were no files associated to the filegroup.

Here is the error message:

If that is the case then is it possible to install SQL only for SEPM on the same machine where you have to install SEPM

As of now the cause for this issue is not knwon. You can try install SQL DB locally on the same machine as SEPM.

The user account for database access must have privileges db_ddladmin, db_datareader, and db_datawriter.

If these requirements are not met, your installation fails. A best practice is to define a new database.


http://seer.entsupport.symantec.com/docs/330748.htm

To create the database you have to be logged in as DBA ..using SA..If using Windows Authentication then login as Domain Admin

The privileges for the DB user where already given and the filegroups where defined.
For some reason it is not enough.

How the SQL server installed?Is it in windows authentication mode or in Mixed authentication mode?

Also go tho start--->programs--->Microsoft SQL 2008--->SQL server management studio and try to login to SQL server with the given credentials.Are you able to login here?

SQL server is installed with mixed mode and the authentication I was given is SQL authentication.
And Yes, I'm capable of performing login with my user & password.

Is there any issue in installing the database locally?

Can you try to install SQL locally on the same machine and then try ?

What is the OS of your SEPM?

TCP Offload Engine may be the culprit here.Disable it.have a look at this KB
Symantec Endpoint Protection appears to cause networking problems with NICs using a TCP Offload Engine

Hi Guys,
I just followed the below parameters when configured the file groups and everything seems to be working just fine.

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

Thanks for your assistance,
Shalom Cohen

Happy to hear your problem got rectified