This document applies to your situation:

Title: 'Symantec Endpoint Protection clients do not update definitions or signatures with Windows Server Update Services (WSUS) installed on the Symantec Endpoint Protection Manager'
Document ID: 2007110813315548
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007110813315548?Open&seg=ent

Hope that helps!

This document applies to your situation:

Title: 'Symantec Endpoint Protection clients do not update definitions or signatures with Windows Server Update Services (WSUS) installed on the Symantec Endpoint Protection Manager'
Document ID: 2007110813315548
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007110813315548?Open&seg=ent

Hope that helps!

the default website (SEPM) has the symantec folder in the content vdir . . . some WSUS forums are sying to verwrite that w/one pointing to the wsus content folder . . . will that break SEPM?

If we are installed to the Default Website and you overwrite our "Content" virtual directory with one pointing to the WSUS content folder then "yes" the SEPM will no longer be able to provide updates to your clients. A better option (as indicated in the document I linked you) would be to move us to a custom website so there are no conflicts.

Hope that helps!

If we are installed to the Default Website and you overwrite our "Content" virtual directory with one pointing to the WSUS content folder then "yes" the SEPM will no longer be able to provide updates to your clients. A better option (as indicated in the document I linked you) would be to move us to a custom website so there are no conflicts.

Hope that helps!

Followed directions . . . it then said to follow: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111212591048?Open&docid=2008052809491248&nsf=ent-security.nsf&view=docid&seg=ent (How to configure the Symantec Endpoint Protection Manager to run with a custom HTTP port)
"Configuring Symantec Endpoint Protection Manager to use a custom HTTP port

1. Stop the "Symantec Endpoint Protection Manager" service.
2. Open IIS.
3. Right-click the Web site on which Symantec Endpoint Protection Manager resides.
4. Click Properties.
5. Under TCP port, enter the HTTP port number you want to use.
6. Click OK.
7. In a text editor such as Notepad, open the following file:

   C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\etc\conf.properties
    

8. Check for the following line in the conf.properties file. Add the line to the bottom of the file if it does not already exist. Replace <port> with your chosen port number:

   scm.iis.http.port=<port>"

in step 7 . . . I don't have a Tomcat folder under C:\Program Files\Symantec\Symantec Endpoint Protection Manager . . . any thoughts?

If we are installed to the Default Website and you overwrite our "Content" virtual directory with one pointing to the WSUS content folder then "yes" the SEPM will no longer be able to provide updates to your clients. A better option (as indicated in the document I linked you) would be to move us to a custom website so there are no conflicts.

Hope that helps!

Followed directions . . . it then said to follow: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111212591048?Open&docid=2008052809491248&nsf=ent-security.nsf&view=docid&seg=ent (How to configure the Symantec Endpoint Protection Manager to run with a custom HTTP port)
"Configuring Symantec Endpoint Protection Manager to use a custom HTTP port

1. Stop the "Symantec Endpoint Protection Manager" service.
2. Open IIS.
3. Right-click the Web site on which Symantec Endpoint Protection Manager resides.
4. Click Properties.
5. Under TCP port, enter the HTTP port number you want to use.
6. Click OK.
7. In a text editor such as Notepad, open the following file:

   C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\etc\conf.properties
    

8. Check for the following line in the conf.properties file. Add the line to the bottom of the file if it does not already exist. Replace <port> with your chosen port number:

   scm.iis.http.port=<port>"

in step 7 . . . I don't have a Tomcat folder under C:\Program Files\Symantec\Symantec Endpoint Protection Manager . . . any thoughts?

Please ignore the comment above - I found it on the D drive!
Sorry!!