If we install TSM Client 4.1.3 on machines (2K and NT so far), then run the 5.1.1 install everything seems to go okay. If you go to [Program Files]\Tivoli\TSM\baclient\dsm.exe, it runs fine. However, if you attempt to launch it via the desktop or start menu shortcuts, it attempts to open the installation MSI in maintenance mode. Annoying, but since we are using Self-Extractor to deploy, it deletes the installation files after first install. Since a proper maintenance-mode should be running from the System copy, this is improper, but it shouldn't be doing it at all! A clean install of 5.1.1 works fine.
I captured the changes during this maintenance install, and it installs about 15 files to the baclient directory and elsewhere.
Any thoughts? I'd hate to bypass the MSI functionality by brute-forcing an uninstall via Custom Action, but I wonder if anyone else has run into this..
thanks,
Atticus
[email protected]
I captured the changes during this maintenance install, and it installs about 15 files to the baclient directory and elsewhere.
Any thoughts? I'd hate to bypass the MSI functionality by brute-forcing an uninstall via Custom Action, but I wonder if anyone else has run into this..
thanks,
Atticus
[email protected]
