Date:         Fri, 16 Jul 2010 17:43:49 -0500
Reply-To:     Kevin Myers <KevinMyers@AUSTIN.RR.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Kevin Myers <KevinMyers@AUSTIN.RR.COM>
Subject:      Re: Windows SAS Install script wanted
Comments: To: "DUELL, BOB (ATTCINW)" <BD9439@ATT.COM>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=response

Oops, one correction:


@echo off

echo.SAS is being installed, please wait.

"path-to-depot\setup.exe" -quiet -responsefile
"path-to-response-file\userID_sdwresponse.properties"

if %ERRORLEVEL% equ 0 (
    echo.SAS installed successfully.
) else (
    echo.A SAS installation problem occurred, call Bob.
)

pause


Also, once you have put this in a .cmd file, then it can be executed by:
"PathToFile\FileName.cmd"

or, if PathToFile is in your system's PATH environment variable, then just:
FileName


----- Original Message -----
From: "Kevin Myers" <KevinMyers@austin.rr.com>
To: "DUELL, BOB (ATTCINW)" <BD9439@ATT.COM>; <SAS-L@LISTSERV.UGA.EDU>
Sent: Friday, July 16, 2010 17:37
Subject: Re: Windows SAS Install script wanted


> Bob -
>
> Although there are other approaches, the easiest way to do most of what
> you want would lie in simply leaving the console window open while the
> installation script is running.  If you are willing to do that, then you
> could simply use something like this (put it in a .cmd file):
>
>
> @echo off
>
> echo.SAS is being installed, please wait.
>
> "path-to-depot\setup.exe" -quiet -responsefile
> "path-to-response-file\userID_sdwresponse.properties"
>
> if %ERRORLEVEL% equ 0 (
>    echo.SAS installed successfully.
> ) else (
>    A SAS installation problem occurred, call Bob.
> )
>
> pause
>
>
> Note that the "pause" command will automatically display "Press any key to
> continue."  The above script should work in any recent 32 bit version of
> Windows (i.e. Windows 2000 and later).
>
> If you *really* want dialogue boxes instead of a console window, then you
> will need to use something like vbscript, but that can get a bit more
> complicated.
>
> Hope that helps.
>
> s/KAM
>
>
> ----- Original Message -----
> From: "DUELL, BOB (ATTCINW)" <BD9439@ATT.COM>
> To: <SAS-L@LISTSERV.UGA.EDU>
> Sent: Friday, July 16, 2010 17:17
> Subject: Windows SAS Install script wanted
>
>
>> Hi all,
>>
>> In the spirit of the recent "Make SAS-L better" thread where we
>> discussed how we often dive into subjects only tangentially related to
>> SAS, I'd like to ask for some help.
>>
>> I support a rather large group of SAS users all over the United States.
>> To deploy the new version of SAS (9.2M3), I plan to create customized
>> scripts to install the specific mix of products appropriate for each
>> user.  We have one corporate license, but we license various modules in
>> different quantities.  Plus, some users access our UNIX BI server and
>> need certain other "products". All our users must "self-install" SAS;
>> support from our "real" IT organization is nil, so solutions like SMS
>> are not available.
>>
>> The new SAS Deployment Wizard makes this very easy to do.  I recorded an
>> install session that selected all products and all modules into a single
>> "response file".  Using that as a template, I can create unique install
>> scripts for each user with only the products and modules they need.
>>
>> Next, I created a little Windows "batch file" that contains the DOS
>> command to run the install program in "quiet" mode.  This prevents the
>> user from being faced with all the dialogs about what to install and
>> where.  I store the batch file on another file server and email them
>> some simple instructions, plus a hyperlink to their file.  All they have
>> to do is double-click the link and the install program takes off in the
>> background.
>>
>> This is works well as long as there are no problems during the install.
>> However, if the install fails (and there have been several failures
>> various reasons), the user has no idea.  In fact, there is no way that
>> the user even knows that the install is working at all.
>>
>> The SAS Institute suggested solution is to include the -wait option on
>> the setup command.  This leaves a process named "setup.exe" running in
>> the Windows Task Manager.  As long as that process exists, the install
>> is taking place.  Although useful for technically savvy users, this is
>> confusing to many.
>>
>> All of this is a prologue to my request:  Can anyone help me create a
>> Windows script to do the following:
>>
>> 1. Display a little dialog box saying "SAS is being installed, please
>> wait".
>> 2. Execute the install program ("path-to-depot\setup.exe" -quiet
>> -responsefile "path-to-response-file\userID_sdwresponse.properties").
>> 3. Check return code from setup.exe.
>> 4. If return code says SAS was installed okay, display message "SAS
>> Installed, click OK to exit"
>> 5. If return code says SAS was NOT installed okay, display message "A
>> problem occurred, call Bob.  Click OK to exit".
>>
>> I have exactly zero experience with Windows scripting and don't know how
>> to start.  Web searches have led to many alternatives, but I don't know
>> which to consider.  I'm hoping there is a relatively simple solution
>> (not involving new purchased software); perhaps someone has already
>> dealt with this and can share as example.
>>
>> Help me SAS-L-Kenobi, you're my only hope!
>>
>> Bob
>