Date:         Mon, 19 Jul 2010 10:53:33 -0400
Reply-To:     Michael Raithel <michaelraithel@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Michael Raithel <michaelraithel@WESTAT.COM>
Subject:      Re: Windows SAS Install script wanted
In-Reply-To:  <331C5406E0EC64408B07D6B74516BE1710133112@BD01MSXMB018.US.Cingular.Net>
Content-Type: text/plain; charset="us-ascii"

Dear SAS-L-ers,

Bob Duell posted the following:

> 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, we may not be Jedi Masters, but we do have an automated SAS for Windows installation script that keeps SAS Mecca staff from going to the Dark Side while performing SAS v9.2 installations.  We use a fairly inexpensive product called WinBatch (http://winbatch.com/ ) to script the installations; including telling the installer to wait and letting the installer know when the process has completed.  This has been pretty successful in our organization in executing pre-recorded silent SAS installation files.  Check it out!

Bob, best of luck in all your SAS installation endeavors!


I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel@westat.com

Author: Tuning SAS Applications in the MVS Environment

Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172

Author: The Complete Guide to SAS Indexes
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There are times when silence has the loudest voice. - Leroy Brownlow
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++