Hello,

Here are few Articles which may help you.

Installing client software using third-party tools

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

About installing clients with Microsoft SMS 2003

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

Installing clients with Microsoft SMS 2003

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

Check these Threads with a Similar Issue - 

https://www-secure.symantec.com/connect/forums/problem-installing-endpoint-protection-11-12-through-sms-andor-sccm

https://www-secure.symantec.com/connect/forums/sep-121-any-tips-sccm-deployment

Hi,

I was trying to avoid such a reply, but Thanks for your reply :-)  I have read these articles before, but does not answer my question.

To be clear, I am asking the command line that will execute the sep.msi in conjuntion with setup.ini and setAID.ini that have been created.  I don't want to reivent the week, but I want to deply the msi using these predefined settings.  I only know how to specify one.

 Msiexec [parameters] USEINI="setup.ini/setaid.ini"

Do I need to specifiy one or both ini's?  What order do they need to run?  How can I define 2 in a commandline?

Alternatively, if anyone else knows how to deploy the setup.exe and NOT report as a fail in SCCM, please let me know!

Thank You Greatly!

Hi

Check page 1095 in the installation document to see all featureset commands.

Here is the line to install all components execept the E-mail plugins.

msiexec /i "Sep64.msi" /qb! ADDLOCAL=Core,SAVMain,Download,PTPMain,TruScan,DCMain,NTPMain,ITPMain,Firewall,LANG1033 DISABLEDEFENDER=1 RUNLIVEUPDATE=0 /l*v  %temp%\SEP64.log

Regards

Torb

Thank You Torb,

How does it know to put in a SEP group as well?

Can it be used in conjucntion with setup.ini or setaid.ini?  Or is later only for exe?

during the first install , the preferrred group mode will be inside the sylink.xml file

if you open the sylink.xml in a word pad you will see the preferred group name.

here is the list of switches.

http://www.symantec.com/business/support/index?pag...

Thank You Rafeeq,

reviewing article now.

does anyone else use SCCM for SEP12.1 - seems a lot of effort and re-engineering to get it to report as a success, when the created setup.exe works perfect.

The only way I have EVER achieved a "succeeded" task in a SCCM TS or App Deployment for SEP 12.x is to do the following:

(Currently deploying SEP 12.1.1 MP1 using SCCM 2007 Sp2 R3 but it "should work" for other versions too)

1. Open the SEP Manager and go to the Admin section
2. Select the Install Packages section
3. Select on Client Install Settings (Default Client Installation Settings is there by default but you do NOT want that one)
4. Under tasks, click on Add Client Install Settings
5. Name you new Client Install Settings something like "Task Sequence Installation" to differentiate it and leave the Install Tab settings as the defaults.
6. On the Scheduled Reboot tab, set the Restart method to "No restart" (this is key because the commandline methods never work appropriately) and click OK to save.
7. Now you have 2 Client Install Settings available to you
8. If you want to modify any Feature Sets, do the same via Add Client Install Feature Set and save it as something appriately descriptive.
9. Go to the SEPM home page and in the top right hand corner next to Common Tasks, use the pulldown menu to select "Install protection client to computers"
10. Select New Package Deployment
11. Select the Install Package you wish to use
12. Select the SEPM Managed Client Group you wish to assign
13. Use the pulldown menus to now select your new Install Feature Sets (if you have one) and your new "Task Sequence Installation" Install Settings.
14. Leave the rest the defaults and then click Next
15. Select Save Package
16. Specify a network share path for it to copy the packages to
17. Specify a single .exe or Separate files (MSI) - I chose the MSI so that I could immediately create my new SEP client package using the SMS Defintion task in SCCM
18. Click Next, review your settings and click Next to begin the copies (x32 and x64) in my case.
19. Be patient and allow wizard to complete.
20. Once complete, create your packages in SCCM (again, I use the SCCM method of "New - Package from definition" and browse to my new MSI to build the SCCM package.
21. Once your SCCM package is created, add your DPs and then modify the program that you will be using for the TS or deployment.
22. Set your SCCM package program (per-system unattended in my case) to "ConfigMgr restarts computer" (this is key). 
23. Now test your deployment... 

What happens is...

1. The SEP client installation truely supresses the reboot after the install has completed
2. SCCM then waits for msiexec to complete and a "pending reboot" event is tracked in your deployment log or report
3. SCCM then restarts the computer for you
4. Any pending actions of the SEP installation complete at computer startup
5. Once the SCCM Client loads back up, a succeeded task is reported!!!!!!!!!!

-Cheers and good luck.  Works for me now all the time.