I've tried these (or more) on both regular and the silent setup.exe installers. I'm afraid a half-install is screwing up further testing. Unless I come up with something new, I'll probably do that. I can restore it to its previous non-SEP state so testing is clean. I'm not sure after this half-install thing happens, if it's botching up the machine for future installs. I also made a new installer yesterday that's supposed to run silently. I've tried setup.exe, our normal client installer. Halfway through that log I see a string of failures. I finally caught a log with the /v msi command line (I'll type it below).

I've watched the program files x86 Symantec folder fill up, and then at the end it's just got a folder or two and some script files. I keep having it run, and it seems to install something. I need to intsall the SEP setup.exe from a command line, eventually without a user logged in, but for now, I'm logged in running a batch file. I've tried multiple ways of installing this but I must be doing something wrong.

Symantec sep 14