Thank-you pm67310 for SEP 14.3 RU1 for WIN!! Does anyone have SEP 14.3 RU1 for MAC & Linux? Thanks in advance!
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.
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.
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
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
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..!)
I had issue upgrading from 14.3 MP1 (14.3.1169.0100) to 3384, no matter how many times I tried installing, at the end it always did a "rollback". I had to run an uninstaller tool (the OS default did not work), but still it didnt go, then I ran "CleanWipe" (newest version), sitll didn't work, then, the "Cloud Endpoint Diagnostic and Removal (CEDAR)" tool, but still, and finally, I ran the "Norton Remove and Reinstall Tool (NRnR)", and then, it finally install, but because it did as "fresh" new installation, I had to setup (customize) all again. In my case the "exception" option was good, but on that same tab (Change Settings), as the window (program) size kept the same, I had to scroll down so to get into "Client Management", as there is a new option called "Network Traffic Redirection".
Hmmm.. Pasting a bunch of Symantec articles doesn't necessarily invalidate my point. I know there are different types of releases (been using SEP ever since if was taken over from Norton). But I still feel anything with the word "preview" implies incomplete or not-yet-foolproof. PS: I did run it in a VM and also saw the new Network Traffic Redirection feature. But it only works with Win8+ with a configured WSS (Symantec Web Security Service). /x13