Hi, Any reason you're using a batch file? I see no benefit of using it when I look at the content of it.
We deploy SEP simply using this: [cid:image002.png@01CFECB0.8FC9F3D0] If I wanted to limit the application to x64 OS's only, I'd select that in the properties menu as shown above. However since we don't deploy x86 systems, I don't need to limit the OS's where it can be executed on. If you don't want to run the setup.exe (gets it's parameters from setup.exe and setAid.ini) you can simply execute the msiexec command from right there as well. Here's a small example: [cid:image001.png@01CFECB0.FA196040] Kind regards, Stephan Schwarz System Administrator @ Leiden University Medical Center [social-facebook-box-blue-icon]<http://www.facebook.com/stephan.schwarz.0>[social-linkedin-box-blue-icon]<http://www.linkedin.com/pub/stephan-schwarz/23/911/695>[social-twitter-box-blue-icon]<http://twitter.com/#!/Schwarz_Stephan>[RSS-icon]<http://www.stephan-schwarz.net/?feed=rss2>[www-page-icon]<http://www.stephan-schwarz.net/> Tel.: +31 (0)6-4662-8977 Email: m...@stephan-schwarz.net<mailto:m...@stephan-schwarz.net> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of it's mike Sent: Monday, October 20, 2014 9:27 PM To: scripting@lists.myitforum.com Subject: RE: [scripting] MDT scripting / command line issue Can you run the msiexec from a command prompt? I'm not an msiexec giant, but as written (and ignoring 'smart' quotes using only the straight ones) - assuming it's running from C:\temp, the msiexec command line would expanded as (for the 32 bit one): msiexec /i "C:\temp\SSEP_12.1.4013.4013_32bit\Sep.msi" /qn /L*V log.txt SYMREBOOT=Suppress Is this correct? (the %~dp0 gets turned into the path where your script is; it includes a trailing back-slash) From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry Sent: Monday, October 20, 2014 12:15 pm To: scripting@lists.myitforum.com<mailto:scripting@lists.myitforum.com> Subject: [scripting] MDT scripting / command line issue Hi All, I know almost nothing about scripting, so I just wanted to get that out there. I have an MDT server where I want to set up SEP in application Deployment. Below is the scripts I have tried: @echo off IF "%ProgramFiles(x86)%"=="C:\Program Files (x86)" goto x64 else goto x86 :x86 ECHO System is x86 msiexec /i "%~dp0SSEP_12.1.4013.4013_32bit\Sep.msi" /qn /L*V log.txt SYMREBOOT=Suppress goto exit :x64 ECHO System is x64 msiexec /i "%~dp0SSEP_12.1.4013.4013_64bit\Sep64.msi" /qn /L*V log.txt SYMREBOOT=Suppress goto exit :exit -------------and------------ @echo off IF "%ProgramFiles(x86)%"=="C:\Program Files (x86)" goto x64 else goto x86 :x86 ECHO System is x86 msiexec /i SEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt SYMREBOOT=Suppress goto exit :x64 ECHO System is x64 msiexec /i SEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt SYMREBOOT=Suppress goto exit :exit The command lines have varied quite a bit. But I started with: Cmd.exe /c sep_install.bat The source/working directory in MDT on the software package is: .\Applications\Symantec_Endpoint_Protection The best I have been able to do is get the script to start (it opens a DOS window) then identifies the OS, but it dies right there. Sometimes with no error or return code, sometimes with a return code: 1. I am totally at my wits end here as no combination of commands is working. (Lack of knowledge is the problem) Any help would sure be appreciated. Thanks in advance, Dave Landry Site Support Administrator Laird Technologies 1 Perimeter Road - Suite 700 Manchester, NH 03103 +1 603-935-7857 [LairdLogo]
