Nathan,

I'm not certain where all of the 'silentinstall' doc is located (other than the
readme's).

However, a 'silentinstall' preparation is nothing more than running the SETUP
program using a special parameter (/r or -r) on a server/workstation whose ADSM
configuration pretty well matches up with that where you will eventually be
doing the actual silentinstall.  Then you walk through all the prompts for the
different ADSM installation configuration options.    The SETUP program records
those choices and saves them in a file called C:\WINNT\SETUP.ISS (the
drive/directory may vary depending on your NT installation conventions).  Copy
that file to the V3.1.0.7 \ADSMCLI\WIN32\INTEL\DISK1 directory.  Then, on your
target servers/workstations, run SETUP /s (or -s).  It will install the ADSM
client with the same options on the target.

You may need to build multiple SETUP.ISS files.  For example, I don't install
the Administrative Client feature on most of my servers but I do on some
administrator's workstations.  There is an option (-F1, I think) to select the
silentinstall setup file you want to use on any given installation.  I'm not an
expert at 'silentinstall' but will probably become one as we upgrade our V2
clients to V3 on 150+servers over the next few months.

Regarding SP4, what version of ADSM client are you running now?  The word on the
forum seemed to be that the problem was limited to growing memory (probably
working set) at V3.1.0.6; some people down-leveled to V3.1.0.5.  No one owned up
to reporting a problem to IBM and I never have heard whether there was a fix or
if this was someone's imagination.

Please let me know if you have more questions and if you have any further SP4
feedback.

Thanks,
Dennis






Nathan King <nathan.king AT USAA DOT COM> on 06/02/99 04:43:07 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Dennis Schaffer/MutualOMA)
Subject:  Re: ADSM/NT Client V3.1.0.7 and Custom SilientInstall - Success!!




Are there any docs available on how to create a silent install? How do I get
started?

We intend to start testing 3.1.0.7 on some of our test cluster servers
shortly. They'll be at SP4. I'll let you know how it goes.

For your information we haven't had any problems with SP4 & ADSM at all and
we have it installed on over 300servers so far.
Nathan

        -----Original Message-----
        From:   Dennis Schaffer [SMTP:Dennis.Schaffer AT MUTUALOFOMAHA DOT COM]
        Sent:   Wednesday, June 02, 1999 4:33 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        ADSM/NT Client V3.1.0.7 and Custom SilientInstall -
Success!!

        I wanted to let everyone who might me interested know that I've done
some
        testing with the new ADSM/NT V3.1.0.7 client and its installation
with the
        "silentinstall" option.

        I'm trying to install V3.1.0.x on top of an uninstalled V2.1.0.6
client as an
        effective upgrade.  We install to a custom directory, we don't
install the admin
        client and multimedia files.  I didn't try V3.1.0.6 because of the
problems
        reported on this forum and I couldn't get a silent install to work
with the
        V3.10.6Q fixtest.

        However, I'm happy to report that I was able to run a silentinstall
with
        V3.1.0.7 the first time, and so far, every time.

        I haven't done any additional testing yet and I specifically want to
see how it
        works with NT Service Pack 4 (because I've seen lots of complaints
on this forum
        with no apparent results).

        If anyone else does any testing with this client level, please let
me know.

        Dennis Schaffer
        Mutual of Omaha