/build/static/layout/Breadcrumb_cap_w.png

Hide in add/remove programs

Hi all, this is my second time here to seek help, the first I got what I want, hope this time I could also.

Now I am packaging Microsft Office 2007, if the package is done, it will be deployed by CA DSM to clients, in order to trace the records for the software, we want to recieve a note if this software is uninstalled in the client, so what we want is, if the user uninstalls the software from add/remove progarams entry, our uninstall program will be executed. In a word, when user click repair or remove button, we want our program executed.

I think there must be some way to implement it.

Another workground is hidding the entry from add/remove programs, then create our own entry.

Any help, very appereicated

0 Comments   [ + ] Show comments

Answers (14)

Posted by: Bobo 14 years ago
Orange Belt
0
These setings are found in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Application GUID}

UninstallString = "C:\OurOwnUninstallScript.vbs" (REG_EXPAND_SZ)

For hiding:
SystemComponent = 1 (REG_DWORD)
Posted by: my44186680 14 years ago
Senior Yellow Belt
0
Hello Bobo,

Really really thanks for your information, this question bothers me for a long time!

For hiding the item, it really did work.

For our own uninstall script, if the package is an msi package, this method seems not working.

Thanks again!
Posted by: pjgeutjens 14 years ago
Red Belt
0
For our own uninstall script, if the package is an msi package, this method seems not working.

If you made your own MSI you could always include a custom action in it (in your MSI or with MST) that sends the message. To make sure it only runs on uninstall add condition REMOVE=~"All" OR MaintenanceMode="Remove"

PJ
Posted by: anonymous_9363 14 years ago
Red Belt
0
These setings are found in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Application GUID}

UninstallString = "C:\OurOwnUninstallScript.vbs" (REG_EXPAND_SZ)

For hiding:
SystemComponent = 1 (REG_DWORD)
Use the built-in property ARPSYSTEMCOMPONENT instead. Its mere presence - i.e. it doesn't need a particular value, although most people set it to '1' - will create this registry entry for you.
Posted by: my44186680 14 years ago
Senior Yellow Belt
0
To VBScab: You mean I can create a new value ARPSYSTEMCOMPONENT under uninstall\{GUID}, and I don't need set value for it? This property will implement the same fuction as
SystemComponent = 1 (REG_DWORD)

Am I correct? Thank you

To pjgeutjens:

I do not really follow you, now I just package the office 2007, after install, there will be an entry in add/remove, any way to let our script executed when user click Remove/Repair?
Posted by: pjgeutjens 14 years ago
Red Belt
0
To pjgeutjens:

I do not really follow you, now I just package the office 2007, after install, there will be an entry in add/remove, any way to let our script executed when user click Remove/Repair?


I misunderstood your intentions, disregard my answer :)
Posted by: anonymous_9363 14 years ago
Red Belt
0
You mean I can create a new value ARPSYSTEMCOMPONENT under uninstall\{GUID}, and I don't need set value for it?No. The property would normally goes into the Property table of the MSI. However, we don't mess with vendor MSIs, we use a transform. But, Office 2007 doesn't use transforms but patches. So, the easiest route is to specify it on the command line, ARPSYSTEMCOMPONENT=1.

I'm really not sure about the wisdom of doing that for Office, though...
Posted by: aogilmor 14 years ago
9th Degree Black Belt
0
Yes, thank you. Finally somebody jumps in and saves the day!

the rest of you really should read Pounding A Nail: Old Shoe or Glass Bottle?
and read Ian's sig.
I often find the domain qualifier (e.g. site:microsoft.com ) to be useful in google searches to find quality information on supported tool sets.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Pounding A Nail: Old Shoe or Glass Bottle?If ever there were the perfect candidate for a "sticky", this is a major contender. Thanks, Owen.
Posted by: my44186680 14 years ago
Senior Yellow Belt
0
Hello, everyone.

Unfortunately, I still can not hide the information for office 2007 access or visio or project in the add/remove programs, here is the info for access in the registry hive,

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-0015-0000-0000-0000000FF1CE}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-0015-0000-0000-0000000FF1CE}_Access_{059C8094-BA5F-4091-8685-6EB296DBF214}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-0015-0804-0000-0000000FF1CE}

I've add SystemComponent = 1 (REG_DWORD) under every branch, but in the add/remove, still have the record, how could I do?
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
I do not think those entries are coming because these hives. check 2 things.
1) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products entry can be coming because of this hive or
2) It is coming from same uninstaller registry but not because of product code. Itmay be coming from below reg.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ENTERPRISE (depend on your type of office installation)
3) still if no luck then, the name which you are getting in arp, copy that exact name and search in the registry, definitely you will get the answer.
Posted by: aogilmor 14 years ago
9th Degree Black Belt
0
ORIGINAL: VBScab
Pounding A Nail: Old Shoe or Glass Bottle?If ever there were the perfect candidate for a "sticky", this is a major contender. Thanks, Owen.

You're welcome. Unfortunately, judging from the posts following, your advice was not heeded and they're persisting in glass bottles and old shoes.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Horses...water...
Posted by: my44186680 14 years ago
Senior Yellow Belt
0
Got it, another branch under uninstall!

Access, that's the root cause, thanks everyone.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ