[TIP] Download Symantec Endpoint Protection from direct links

Discussion in 'Application Software' started by CHEF-KOCH, Dec 14, 2013.

  1. pm67310

    pm67310 MDL Senior Member

    Sep 6, 2011
    397
    142
    10
  2. pm67310

    pm67310 MDL Senior Member

    Sep 6, 2011
    397
    142
    10
  3. Sajjo

    Sajjo MDL Expert

    Feb 6, 2018
    1,539
    2,081
    60
  4. MoMDL

    MoMDL MDL Novice

    Jun 30, 2015
    4
    2
    0
    Thank-you pm67310 for SEP 14.3 RU1 for WIN!!
    Does anyone have SEP 14.3 RU1 for MAC & Linux? Thanks in advance!
     
  5. LostED

    LostED SVF Patch Lover

    Jul 30, 2009
    6,386
    17,166
    210
  6. MoMDL

    MoMDL MDL Novice

    Jun 30, 2015
    4
    2
    0
    Thank-you pm67310 for the quick response!! have fun/safe weekend.
    Thank-you LostEd, i was unaware, I will def pursue the SEPM installer moving forward for the various OS packages. have a fun/safe weekend.
     
  7. MoMDL

    MoMDL MDL Novice

    Jun 30, 2015
    4
    2
    0
    Anyone else having an issue where the imported reg Exceptions does not populate in SEP 14.3 RU1 Windows10 x64 unmanaged client? Tried it twice on 2 different VMs same results; the Exceptions are populated in the Registry but not in the sep client. Have permanently disabled Defender as well to ensure that was not blocking the Exception reg import. Have not had this issue on previous SEP builds; ie: merge the exception list via reg, reboot, then install the sep client. I’m able to manually Add Exceptions in the SEP client so that module does function.
     
  8. Foomanchoo

    Foomanchoo MDL Novice

    May 15, 2020
    38
    18
    0
  9. x90126

    x90126 MDL Novice

    Mar 16, 2019
    7
    1
    0
    Those are preview builds. (so I assume beta)

    Here is Setup.ini from archive :

    [General]
    Name=Setup.exe
    Version=1.0.0

    [Startup]
    CmdLine=/l*v "%TEMP%\SEP_INST.log"
    ProductName=Symantec Endpoint Protection
    ProductCode={D2DF790F-FA74-46BB-B250-8B494599BCEB}
    ProductVersion=14.3.3384.1000
    PackageName=Setup.dat
    PackageName2=Sep64.msi
    PackageCode={49B40FF7-FB26-4243-B06E-09DD759C16D0}
    ProductBuildType=Preview Build


    /x13
     
  10. x90126

    x90126 MDL Novice

    Mar 16, 2019
    7
    1
    0
    Ola Shortyportuguese.

    From what I gather, a preview build is sort of an RTM (so stable) which =also= relies on community feedback (so a beta).

    It seems the files 3 messages back are somewhere between the two: "Beta++" or "RTM--".

    I've checked my current SEP files and the ProductBuildType line in SETUP.INI is missing.
    This means either the previous releases were not preview builds (I'm tempted to say Beta again)...

    ** OR **

    Brocadcom changed the way the files are packaged and new releases will always contain "ProductBuildType=Preview Build" from now on.
    I don't know.


    PS: It's not because it's listed as a releases (with releases notes) on the site that it can't also be a beta. ;)


    /x13
     
  11. Mks1440

    Mks1440 MDL Novice

    Jul 9, 2018
    4
    0
    0
    Had the same issue and it only work after clean install of SEP and any traces of SEP in windows registery then enter the new exceptions manually. (import the keys into registery on safe mode or before installing SEP will not work........the data are there but somehow SEP doesnot see it......Exception window is empty..!)
     
  12. hyperstriker

    hyperstriker MDL Novice

    Nov 24, 2017
    16
    9
    0
    #960 hyperstriker, Dec 8, 2020
    Last edited: Dec 8, 2020