Hi Keith,

Your script worked like a charm. My apologies for not trying this when you 
first suggested it. My lack of understanding what you were doing was 
responsible for my hesitation.

Thank you so much for your assistance.

Also, I am interested if anyone knows any easy to understand books on scripting 
for novices or internet courses that will help with learning how to create 
scripts?

Regards,

Dave



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Keith Garner (Hotmail)
Sent: Monday, October 20, 2014 4:47 PM
To: scripting@lists.myitforum.com
Subject: RE: [scripting] MDT scripting / command line issue

As I mentioned earlier, be aware of smart quotes, your first example below will 
fail due to that problem.

This is one of the concerns about writing custom batch scripts, is how to 
gather debugging information from a production installation

Additionally, I would modify the batch script to have the log file written to a 
writable location, rather than the current network share:

@if not defined debug echo off

if /i "%PROCESSOR_ARCHITECTURE%%PROCESSOR_ARCHITEW6432%"=="x86" (
       msiexec /i "%~dps0SEP_12.1.4013.4013_32bit\Sep.msi" /qn /L*V 
%temp%\SEP.log SYMREBOOT=Suppress
) else (
       msiexec /i "%~dps0SEP_12.1.4013.4013_64bit\Sep64.msi" /qn /L*V 
%temp%\SEP.log SYMREBOOT=Suppress
)


Then... check the %temp%\SEP.log file for what *REALLY* failed. Is the package 
really there? Are the relative paths wrong? Etc...

-k

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]






Reply via email to