Yuk.

That means that a reboot WILL ALWAYS be forced.  I don't like that.  Is
there anyway around the auto-reboot?  Is the "problem" with scripting a
"feature" or WAD component of terminal services?

I can use Tivoli Remote Control to get into the box, and run the scripts,
but it is WAY slower than the terminal service console.

Thanks very much for your help.

(BTW- was this documented somewhere and I missed it?)

lisa



                      Karel Bos <Karel.
                      Bos AT NUON DOT COM>            To:       ADSM-L AT 
VM.MARIST DOT EDU
                      Sent by: "ADSM:          cc:
                      Dist Stor                Subject:  Re: MSI install error 
on 2K server, but not on 2k pro or NT??
                      Manager" <ADSM-
                      L AT VM.MARIST DOT EDU>


                      08/14/2002 08:30
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






Use add/remove programs to do your installation. Scripting or manual setup
isn't working when using terminal service.

Greetings,

Karel Bos

-----Oorspronkelijk bericht-----
Van: Lisa Cabanas [mailto:CABANL AT MODOT DOT NET]
Verzonden: woensdag 14 augustus 2002 15:09
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: MSI install error on 2K server, but not on 2k pro or NT??


Has anyone encountered this one?

I had scripted the TSM client install to use the MSI package.  I had been
given a 2k pro box to do my testing on, and there haven't been any issues
on any subsequent installs on the same OS.  The script works on NT, too.
But now that the Windows 2000 Server boxes are going out into production, I
can not get the same script (or command line, or manual install of
4.2.1.20) to run on them.  (Gee, I wish I coulda got a 2000 Server box to
test on....)

I get the error message that "The installation package could not be opened.
Verify that the package exists and that you can access it, or contact the
application vendor to verify that this is a valid Windows Installer
package." I have done the /l*v option, and this is all I get

=== Verbose logging started: 8/14/2002  6:23:42  Build type: SHIP UNICODE
2.00.2600.00  Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (AC:DC): Resetting cached policy values
MSI (c) (AC:DC): Machine policy value 'Debug' is 0
MSI (c) (AC:DC): ******* RunEngine:
           ******* Product: P:
\tsm_install_nt\42120_nt_install\TSM_BA_Client\baclient\Tivoli Storage
Manager Client.MSI
           ******* Action:
           ******* CommandLine: **********
MSI (c) (AC:DC): Client-side and UI is none or basic: Running entire
install on the server.
MSI (c) (AC:DC): Grabbed execution mutex.
MSI (c) (AC:DC): Cloaking enabled.
MSI (c) (AC:DC): Incrementing counter to disable shutdown. Counter after
increment: 0
MSI (c) (AC:DC): Decrementing counter to disable shutdown. If counter >= 0,
shutdown will be denied.  Counter after decrement: -1
MSI (c) (AC:DC): MainEngineThread is returning 3
=== Verbose logging stopped: 8/14/2002  6:23:43 ===

I have looked thru the readmes and msdn.microsoft and support.microsoft and
come up with zilch.

Does anyone have any insight??

(p.s.-- I am reaching the 2000 server boxes via the terminal services
window snap-in.)

TIA
lisa