Microsoft does not support running an MSI from a mapped network drive when you 
are connect to a server via remote desktop to terminal server.

If you were at the consol trying to install it from the mapped network drive it 
would have worked. Or, if you run it from the UNC (i.e start | run | 
\\Server\Install\setup.exe).

I opened a call with MS about this many years ago and the said it was working 
designed.  This was one of the first things I tested when Windows 2003 came 
out.  Guess what the problem doesn't exist there so it looks like they changed 
the design.

"Gilmore,Mindy" <gilmorem AT OCLC DOT ORG> wrote:
I copied it locally and ran it from there. I am running 5.1.6.7 client

-----Original Message-----
From: Stapleton, Mark [mailto:mark.stapleton AT BERBEE DOT COM]
Sent: Friday, July 16, 2004 9:17 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: .msi

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
>I have a corrupted Tivoli Storage Manager Client.msi. Not
>matter what I
>do the client will not install on my Windows 2000 server. I
>keep getting the error message
>
>This installation package could not be opened. Verify that the package
>exists and that you can access it.
>
>Has anyone run into this?

Several questions:

What version of the client are you running? If it's an older version (<
5.2), are you trying to run it from a network share? If so, the Windows
Installer technology is finicky about that; try running it from a local
drive.

Are you using original media, or something that was burned onto CD locally?
You may have had a bad burn; I used to run across that occasionally.

--
Mark Stapleton


---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!