TSM - Tivoli Storage Manager - Uninstall - Windows
0 Votes |
Collections (part of 1 collection)
Description
Property Details
686 | |
TSM - Tivoli Storage Manager - Uninstall - Windows | |
BESC | |
Uninstall | |
0 | |
Internal | |
11/19/2012 12:00:00 AM | |
TSM, Tivoli Storage Manager, Backup, Uninstall | |
True | |
jgstew on 12/4/2012 10:04:37 AM | |
jgstew on 12/4/2012 10:04:37 AM | |
6391 Views / 39 Downloads | |
![]() ![]() ![]() ![]() ![]() |
Relevance
isWindows (Relevance 1172)

windows of operating system
Used in 1 fixlet | * Results in a true/false |

exists key whose (value "displayname" of it as string contains "IBM Tivoli Storage Manager Client" of it and value "uninstallstring" of it as string as lowercase contains "msiexec") of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of native registry
Actions
Action 1 (default)
Action Link Click
here to deploy this action.
Script Type
BigFix Action Script
Wait msiexec.exe /X {name of key whose (value "displayname" of it as string contains "IBM Tivoli Storage Manager Client" of it and value "uninstallstring" of it as string as lowercase contains "msiexec") of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of native registry} /qnSuccess Criteria
This action will be considered successful when the applicability relevance evaluates to false.
Sharing
Social Media: |
Comments
![]() |
|
Definitely a good idea to test something like this on a few systems to make sure it works as expected first before deploying widely, though even then this might not have poped up until it was used in production. Definitely a bummer. |
![]() |
|
I used the fixlet on ~100 sql servers to upgrade to the latest TSM/TDP clients using Server Automation, and only the active node of our 2008 R2 SQL cluster triggered the reboot on the uninstall somehow. It was slightly problematic, but it's done now. The exit code was 1641, which is successful uninstall with reboot triggered. |
![]() |
|
Thanks for letting me know. The `/qn` at the end should have handled that, but it is possible that some versions of TSM require `/norestart` as well to prevent this from happening. I didn't see this in testing when I created this originally. |
![]() |
|
I needed to add a /norestart flag at the end due to it rebooting a server unintentionally. |
![]() |
|
Because this relevance uses "native registry" this one uninstaller will uninstall both the 32bit or 64bit version on the respective 32bit or 64bit system. Because this is a backup application you cannot install the 32bit version on a 64bit system. |