Endpoint Protection

 View Only
  • 1.  How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 10:07 AM

    I have downloaded the Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe, just to test it out. I do not want to upgrade my SEPM server until the next release of SEP comes out. How can I make this a managed client package that I can push out with my current SEPM server which is hosting SEPM 12.1.2015 2015. The server is Windows 2008 and the clients are Windows 7 64 Bit clients.

     



  • 2.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 10:11 AM

    Just replace the sylink file with the one from the SEPM. Use can use a few different methods. Easiest is to push from the SEPM using the Communication Update Package Deployment

    Restoring client-server communications with Communication Update Package Deployment

    Article:HOWTO81109  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL http://www.symantec.com/docs/HOWTO81109

    Converting an unmanaged client to a managed client

    Article:HOWTO54804  |  Created: 2011-06-29  |  Updated: 2011-12-20  |  Article URL http://www.symantec.com/docs/HOWTO54804

     



  • 3.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 10:17 AM

    I want to be able to add it to SEPM so I can push it from there. Replacing the Sylink means I have to have SEP already installed, I want to eliminate this step. I just want to add the newest package to the SEPM so I can push it out as a managed client.



  • 4.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 10:24 AM

    My fault. misunderstood. Add per this KB article:

    Adding client installation package updates

    Article:HOWTO81175  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL http://www.symantec.com/docs/HOWTO81175

     



  • 5.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 10:29 AM
      |   view attached

    This article tells you how to import a newer client into your SEPM:

    http://www.symantec.com/docs/HOWTO81175

    Essentially, you need to download the SEPM install from Fileconnect (see attached screenie) and import the .dat file(s) in from the below folder:

    <DownloadLocation>\SEPM\Packages

    Into the ADMIN -> Install Packages section of your SEPM

    #EDIT#

    Brian beat me to it smiley



  • 6.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Trusted Advisor
    Posted Apr 26, 2013 10:38 AM

    Hello,

    Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe is for unmanaged SEP clients.

    In your case, you may have to download the "Symantec_Endpoint_Protection_12.1.2_MP1_SEPM_EN.exe"

    OR

    Symantec_Endpoint_Protection_12.1.2_MP1_Part1_Installation_EN.exe

    which includes the packages which you would have to import to the SEPM.

    Symantec sends you client installation package updates, and then you add them to the Symantec Endpoint Protection database to distribute them from the Symantec Endpoint Protection Manager.

    You can optionally export the packages during this procedure to make the package available for deployment to computers that do not contain client software.

    Symantec_Endpoint_Protection_12.1_RU1_MP1_SEPM_EN\Packages

    OR

    Symantec_Endpoint_Protection_12.1_RU1_MP1_Part1_Installation_EN\SEPM\Packages

    An installation package that you import consists of two files. One file is namedproduct_name.dat, and the other file is named product_name.info.

    Adding client installation package updates

    http://www.symantec.com/docs/HOWTO81175

    Hope that helps!!



  • 7.  RE: How do I make Symantec_Endpoint_Protection_12.1.2_MP1_Win64-bit_Client_EN.exe into a package

    Posted Apr 26, 2013 11:06 AM

    Thank you, if not for this I would have been going crazy trying to find the .info file(s)