Endpoint Protection

well i have my test machine working fairly well now.  updates are current,etc.

now, i'm wondering what the best way is to implement this.  i read on the docs that it is NOT recommend to run it on a WinXP box.  due to lack of connections.

i have a 2003 DC here but am reluctant to use it.  it already has a default website on it that is used for training.   

Hello
yes xp has limited concurrent connection in IIS
you can install sepm on your dc
when you install sepm
it will ask you to install on default website or custom
just select custom website port 8014
your default website will not be disturbed
can support larger number of clients without any problem

 Well it depends on how many clients you have..
XP supports 10 concurrent connections however there is a workaround with the help of which you can run 100 machines without an issue.

To change the communication settings..

However your DC would be the Ideal SEPM server..no need to worry about the websites..
SEPM does not touch the default website..

i'm confused about these ports.

when i look at the IIS Symantec Site on my little test box it says TCP 8014... when i connect through a web session(java) it will connect to the ip and then the port is :8443.

it seems to me that the Server connections go through 8443.  i'm looking through the admin guides to see what i can find.

 Port 8443 is used for Internal communication via Apache
Port 8014 is used for General communication via IIS

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

would it be recommended to support AD integration?  users don't really match on the workstations.  i wasn't planning on using it.
i thought about replication to the other sites but the bandwidth is VERY low and after reading the docs, it sounds like it will be too much load on the connection.  will keep them separate.

thanks

AD integration is recommended for big AD structures and for people who want everything to be like their AD.

Well..go for GUPs for definition distribution for remote sites..

Won't suggest going for replication/load balancing if your remote sites have less than 50 clients.

well i've installed it and now i've got MAJOR problems.

unable to connect to reporting component error....  now my BackupExec does NOT work, the Server hung overnight and now is building the RAID parity now.

i am full of hate now.  i thought i had done my homework on this but obviously this software doesn't work well with others.

 If you use Microsoft Clustering services for the Symantec Endpoint Protection Manager server, you must install the Symantec Endpoint Protection Manager on the local volume.

i'm wondering if i need to change both ports on the Server.  looks like the BE Recovery manager uses the 8443 but i don't know about the database port 2638

 port 8443 is a common port that BE might be using..
However port 2638 is only used by Sybase database so if you have any then it would be using it..

you can change 8443 from server.xml
check this
http://seer.entsupport.symantec.com/docs/279226.htm

2638 is used in BackupExec as well.... recommend to change to 2639 and change the Server port to 8440.  i wonder if that will solve the reporting errors or hopefully just get BackupExec working again.

 It can solve both..

As its already suggested, you just have to change the webserver port from 8443 to something else...  To do so, you have to re run the management server configuration wizard and change the port number after choosing "Reconfigure my site"..

You actually don't have to worry about the Sybase port 2638, only dbsrv9.exe will listen on it.. If you are stull concerned, you can change that too.. But you just cannot change it in the Management server configuarion wizard.. you will have to first change in the registry..

* Stop Symantec Embedded database service...
* Navigate to HKLM\System\CurrentControSet\Services\ASANY_Sem5 

Edit the parameters key and at the end you will find the port TCP port = 2638, change it to desired port..

* Close down the registry and start back the Embedded database service and run thorugh the management server configuration wizard... and now you can change both the 8443 and 2638 .. :)

I would also like you to give us one small information... What do you see or what happens when you right-click and browse 'Reporting' under symantec webserver in the IIS?

Cheers,
Visu.

well, i've run the reconfig and selected 8440 as per a document i have.  still have the reporting error?

i see 'unexpected error' when i right-click and browse reporting.

I guess this is some permissions stuff... :) .. try this...

1. Change the identity level of 'DefaultAppPool' from NETWORK SERVICE to LOCAL SYSTEM restart IIS and try browsing.

If that dint help, lets do this..

1. Open Domain controller security settings...  and navigate to .. Local policies -> User rights assignment..

2. To your right, you will have many keys.... we will be editing only two... Adjust memory quotas for a process .... Replace a process level token...

3. Add NETWORK SERVICE and LOCAL SERVICE to both these values.... and close down the policy editor..

4. Force a policy update by running GPUPDATE /FORCE .... restart IIS ..

If things are set, reporting should work fine now... :) .. Let me know... :)

OK, all i changed was the Local System setting.  i didn't even restart IIS and i was able to login remotely :9090.  we'll see if BackupExec is still happy and the server doesn't crash.  
i'm still very leery of this now.  i have never had that Server crash in 3 years and within 1/2hr. of installing SEP it was down.  frozen and only a hard reset would bring it alive.
i'm hoping things will be OK.
thank you

So, to review i changed the Server port to 8440 and left the database port as default at 2638.  then changed the DefaultAppPool setting to Local System.

i'm thinking i'll leave the system run a big longer and see if something else shows up.

That's bad to hear that installation of SEP mde you cold reboot the server... Unfornate matey.. Anyway, good to know that things are fine now... I am hoping the same that things *should* work as expected.. :) .. I believe BackupExec is breathing fine now... :) ... Let us know if something happens... :)

What is the workaround in XP to run 100 machines without an issue?

Follow the link:

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