Endpoint Protection

 View Only
  • 1.  SEPM installation automation

    Posted Feb 25, 2016 05:33 PM

    I have a compute stack (up to 42 servers - some clients are RHEL, some are Windows Server) where we also setup a SEPM in that stack (as it will ship as a set to a customer).
    There are several configurations of clients, but always the same set of host names / IPs for them, depending on how large of a set the customer purchased).

    I know there exists some options for client clone options / deployment packages, etc - we are looking to reduce deployment times of the compute stack as a whole.

    Obviously, it has to be prepped for it's individual licensing....

    From my research it appears there isn't a silent installer option for SEPM (not the client, the master for that set of servers).
    I know on Veritas products there exists a "responsefile", to automate installations.


    You had to run the installer once to generate that file, but from there on, could use that file to get through all that would have been prompted (save the licensing, of course)

    Are there any options like a responsefile, or like a clone prep that could be done for the SEPM?
    (or would that be a Request For Enhancement (RFE).

    I appreciate your response.

    Thanks!



  • 2.  RE: SEPM installation automation

    Posted Feb 26, 2016 11:11 AM

    There is a silent install option that you can use. Another option would be to export the MSI file (or EXE) which can be used for the install.

    MSI command line reference for Symantec Endpoint Protection

    About the Windows client installation settings



  • 3.  RE: SEPM installation automation

    Posted Feb 26, 2016 12:25 PM

    Brian-

    Thanks for your response.

    So to confirm, the basic overview of the process could be:

    1) Export settings from a SEPM server that is setup as desired per the Install / Admin guide

    2) Login to the system as Administrator and run the installer in silent mode for any new Management Server with the following command:

    setup /s /v"/l*v SEPM_log.txt /qn RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS"

    3) Import the settings from step #1

    4) Input / Activate licensing

    5) Reboot and run liveupdate at next earliest convenience to enable all features (as the guide indicates some features won't be available until reboot).

    I appreciate your guidance / confirmation.

    Thanks again!



  • 4.  RE: SEPM installation automation

    Posted Feb 26, 2016 12:29 PM

    Yes, you can export a package with the silent install option.

    You can either run it manually or push via something like Altiris or SCCM

    A new license will automatically pulled down when the client connects to the SEPM.

    Yes you will need to reboot to finish the install



  • 5.  RE: SEPM installation automation

    Posted Feb 26, 2016 01:08 PM

    There is no silent switch for SEPM, few exists for only SEP

    Endpoint Protection fails to install or abide by switch parameters when using Microsoft Installer (MSI) commands
     

    https://support.symantec.com/en_US/article.TECH177946.html



    • 6.  RE: SEPM installation automation

      Posted Feb 26, 2016 01:13 PM

      @djtbs1

      You can create a silent install package for SEP clients from within the SEPM:

      Capture_150.JPG



    • 7.  RE: SEPM installation automation

      Broadcom Employee
      Posted Feb 26, 2016 01:48 PM

      There isn't any option like responsefile, or like a clone prep that could be done for the SEPM. You can place Request For Enhancement (RFE) here: https://www-secure.symantec.com/connect/security/ideas



    • 8.  RE: SEPM installation automation

      Posted Mar 02, 2016 04:39 PM

      Gentlemen-

      Thanks for the input.

      After all the responses, and weighing the options, since SEPM doesn't have silent, those above me have instead requested I setup for unmanaged clients...including RHEL clients.
      So my thought is to:
      1) setup SEPM 1 time then set the Reports, Notifications,  Policies, license, etc as desired (we have a documented process for the desired settings).

      2) Create unmanaged client packages for the Win and Linux clients once the policies are set.

      3) Deploy via script to the hosts in the compute stack.

      If the above works out, great.
      If not- I will determine our customer ID and start a support case with Enterprise Customer Care.

      Thanks for your time!