Endpoint Protection

 View Only
  • 1.  Symantec Endpoint Protection Manager install on XP

    Posted Mar 07, 2011 12:36 PM

    I've tried to install SEPM serveral times on XP, but it does not appear to be working.

    I can install it, but when I try to login I get "failed to connect to server". 

    The semsrv service is stopped and will not start.

    When I check IIS I can see that there was no custom website created (which I specified in the install). Also there was not change made to the default website.

    How can I fix this?



  • 2.  RE: Symantec Endpoint Protection Manager install on XP

    Broadcom Employee
    Posted Mar 07, 2011 12:40 PM

    Hi,

    Please confirm few details :

    XP with service pack ?

    IIS version ?

    Which SEPM version you are trying to install ?

    Any specific error in event viewer ? 



  • 3.  RE: Symantec Endpoint Protection Manager install on XP

    Posted Mar 07, 2011 12:44 PM

    in xp you can have only one website, either your default or your custom website

    install it on default website...mode..make sure you select port 8014, in some cases port 80 wil be used by other application

    in the iis under directory security, check integrated windows authen ( not sure if this is present)

    this should work



  • 4.  RE: Symantec Endpoint Protection Manager install on XP

    Posted Mar 07, 2011 01:05 PM

    Be sure to check out the -

    Best practices guide for installing the Symantec Endpoint Protection Manager (SEPM) on a Windows XP operating system.

     

    http://www.symantec.com/business/support/index?page=content&id=TECH91694&actp=search&viewlocale=en_US&searchid=1299521029853

     

    Regards,

    Thomas



  • 5.  RE: Symantec Endpoint Protection Manager install on XP

    Posted Mar 07, 2011 02:28 PM

    I'll uninstall and reinstall using the default website (I also checked integrated windows auth which was not check).



  • 6.  RE: Symantec Endpoint Protection Manager install on XP

    Posted Mar 08, 2011 09:09 AM

    I tried this and it is still not working. I can also see that no change was made to the default website. Why would the install continue like it was sucessful if it wasn't able to create a website?



  • 7.  RE: Symantec Endpoint Protection Manager install on XP

    Posted Mar 08, 2011 09:13 AM

    hmm that strange, there should be five virtual directories created under symantec web server..do you see any?

    are u local to the xp box or remote desktop? if you are remote use the console session

    start-run

    mstsc /console.



  • 8.  RE: Symantec Endpoint Protection Manager install on XP

    Trusted Advisor
    Posted Mar 08, 2011 09:40 AM

    Hello,

    Check the Following Knowledgebase article which speaks of the exact issue and would help you as well.

    "Failed to connect to server" when attempting to log into the Symantec Endpoint Protection Manager console after install

    http://www.symantec.com/business/support/index?page=content&id=TECH96262&actp=search&viewlocale=en_US&searchid=1299594376082

     

    Additional Important tips:

    • Always check that you are always abiding to the Minimum system requirements of the Product.

    System requirements for Symantec Endpoint Protection and Symantec Network Access Control 11.0.6

    http://www.symantec.com/business/support/index?page=content&id=TECH131642&actp=search&viewlocale=en_US&searchid=1299594602577

    • You are installing the Symantec Endpoint Protection Manager (SEPM) on a Windows XP machine. Windows XP has a 10 concurrent connection limitation that has been built in by Microsoft. This guide contains the configuration changes that are necessary to work around this limitation. This is supported for up to 100 clients managed from a single XP SEPM


  • 9.  RE: Symantec Endpoint Protection Manager install on XP
    Best Answer

    Posted Mar 17, 2011 04:55 PM

    I tried this install again on a PC with a fresh (or fresher so to speak) XP install and it just worked. I just followed the best practices and its good with no issues.  I have a lot of crap/goofy configs going on with my PC so I'm not really surprised. Thanks for the many responses, but knowing I probably broken something, I have no real desire to figure how to fix it- I'll just start with a fresh XP install.

    Just to sumarize: it appeared that SEPM was not able to configure IIS properly (it wasn't making any changes to the default website) which I believe was why the service was not starting. On a fresh XP install it worked with no probs.