Part of our installation process includes starting the scheduler to create the
dsmsched.log and dsmerror.log files, then creating shortcuts to them and placing
the shortcuts into the ADSM program group in the Start menu.  Does anyone have
extensions to the Installshield process that would put shortcuts to the logs
into the program group?  I do have an Installshield license, though not the
latest one that includes a script decompiler.

Would IBM consider such an upgrade?  Using the procedure below and this upgrade
we could do our complete installation process automatically . . . assuming as we
do that the computer name is the node name.

Eric Lewis UW-Madison



______________________________ Reply Separator _________________________________
Subject: Re: Automating the Installation of ADSM
Author:  <dthorneycroft AT lacsd DOT org > at IPNET
Date:    10/7/98 12:05 PM


David Beardsley wrote:
>
> I am about to roll out 1200 ADSM servers. We need a way to automate the
> installation procedure. Does anyone have any references to this or be able
> to provide me some help.?
>
> Your help would be greatly appreciated.
>
> Thanks
> David Beardsley
> Sr. Technical Programmer
> Winn Dixie Stores Inc.
> WWW.WINNDIXIE.COM <http://WWW.WINNDIXIE.Com>
> "Good judgment comes from experience, and a lot of that comes from bad
> judgment."

One tip if installing on NT:
If you run a standard setup that will be used in all installations,
run it once with the -r option. (setup -r)
This will record your answers to the setup process in a response file
called setup.iss (I don't recall what directory this file is created in,
if you can't find it after the install, you'll need to run a search)

Once you have this file, you can run a silent unattended install by
placing
the setup.iss file in the same directory as the install files and run
setup
with the -s parameter. (setup -s).

At the end of the install, a file called ADSM.OK is created in the ADSM
sub
directory to let you know the installation was sucessfull.
that the process ran OK

(We used method along with NT's AT scheduler and a few batch files to
install ADSM clients on half a dozen remote NT servers without any
problems.)