Symantec endpoint protection 14 silent install
![symantec endpoint protection 14 silent install symantec endpoint protection 14 silent install](https://i1.wp.com/i.postimg.cc/J0NSWC0T/Client-Control-Settings-Change.png)
- Symantec endpoint protection 14 silent install how to#
- Symantec endpoint protection 14 silent install install#
- Symantec endpoint protection 14 silent install 64 Bit#
- Symantec endpoint protection 14 silent install download#
Symantec endpoint protection 14 silent install install#
Install was still the usual half-install, but I got a log. Then I realized the stuff I've got in quotes here is msiexec switches. I read that you need to have no space between the first /v and next part. This I thought was successful when I saw the log actually generated. The test machine is Windows 10, Threshold 2, 64-bit.Ĭ:\SEP\setup.exe /s /v"/QN /L*V c:\sep_log.txt" This is the client installer, 12.1.6_MP3. I've invested a lot of time on it this week. I'm just not sure why this won't install and won't install silently. So it's actually connecting to that during these install tests. I also noticed an entry yesterday for this test machine in the SEP manager on the server. I've got a batch file now that copies the setup.exe file down to the machine to run it, in case installing off a network is an issue. How do you install SEP silent and unattended though from command line? I'm going to restore it back to the non-SEP state and just try installing the usual setup.exe client installer we've used (not silent) to see if SEP will install at all. Running it manually though I'm still getting this half-install sitatuion. I thought this one would work, that I'd finally figured out the /v switch. Setup.exe /s /v"/qn /norestart /V*L c:\sep_log.txt" <- This one finally gave me the log. 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.
![symantec endpoint protection 14 silent install symantec endpoint protection 14 silent install](https://biztechmagazine.com/sites/biztechmagazine.com/files/styles/cdw_hero/public/articles/2012/02/symantec_ep12_400.jpg)
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. You can see that the package has been successfully created.I'm not having any luck. Click on Next again to start creating the.MSI) and Browse to the right path where you want to save the package and then click Next Click on Seperate Files (required for.Click Save Package, and then click Next.Select installation mode (Computer / User) and then click Next.Select the feature set, the client group and content options.
Symantec endpoint protection 14 silent install 64 Bit#
Select the Platform (Windows or Mac ), If you select the Windows that package includes for both 32 bit and 64 bit machines.In the Welcome to the Client Deployment Wizard pane, choose "New Package Deployment" and click Next.On the Home page, in the Common Tasks menu, select Install protection client to computers.On the Symantec Endpoint Protection Manager console, click the Home tab at left.
Symantec endpoint protection 14 silent install how to#
To know more about how to recommendations refer to this: