Login to participate
Endpoint Management & Virtualization BlogsRSS

Hiding the Add/Remove Entry

Deepanshu's picture
Deepanshu
November 12th, 2008
Filed under: , ,

This is something different thean what you think. I was working on a package for which I want to hide the Add\Remove Program entry but when I look into the following registry hive for systemcomponent entry it was not there:

HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}

Now what to do? I thought, I will make an entry at this hive with my product code, then I will create a Registry Key As follows: 

SystemComponent=1

And it works! If you face the same type of issue it may be useful for you.

+1 (1 vote)
R-Vijay's picture
R-Vijay
1 year 2 weeks ago

ARP component is needed..

I don't think its feasible and a right away to remove a ARP component from the package. Infact, its a better practice to add a ADd/Remove entry to the package, so that it would reduce the adminstrators intervention if the end-user wants to repair the package.

I would prefer giving a ARP entry for every package which is installed on the machine.

Cheers'
Vijay

Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com

0 votes
Saurabh Kumar's picture
Saurabh Kumar
1 year 5 days ago

Other ways to get rid of entry in ARP

The two ways to completely remove the registration of application from the system is, if you are using WPS.

1. In Add/Remove Program (Installation Expert) select "Do Not Display in Add/Remove Program List"
2. In MSI Script>Execute Immediate, comment out the following CA's.
Register Product, Publish Components, MsiPublishAssemblies, Publish Features, RegisterUser, Publish Product.
This is also a way to hide off your application listing from any tool which takes the inventory of your machine.

Bangalore

0 votes
piyushnasa's picture
piyushnasa
1 year 2 weeks ago

ARPSYSTEMCOMPONENT

By placing ARPSYSTEMCOMPONENT=1 in property table also helps to remove the ADD/REMOVE entry from the package.
If you just want the user should be able to repair the package not able to remove it then you can give ARPNOREMOVE=1 property in your package.

Hope this is little knowledge addition :)

-Piyush

Piyush Nasa
Altiris Certified Professional (ACP)

0 votes
Eshwar's picture
Eshwar
1 year 1 week ago

I don't think so

I completely agree with vijay.

You should have an entry of the application in the Add/Remove programs, untill and unless the client is specifically asking for it.

Most commonly used properties for Add/Remove programs:

ARPSYSTEMCOMPONENT
ARPNOMODIFY
ARPNOREMOVE
ARPNOREPAIR

Depending upon the client's request, you can decide on which one go off from the above properties.

Thanks,
Eshwar

Thanks,
Eshwar

+3 (3 votes)
Deepanshu's picture
Deepanshu
1 year 1 week ago

I dont agree with you all in specific situations

Here is a situation where we use wrapper for MSI.Our packaged msi will be in wrapper and only wrapper entry should be visible in ARP not the vendor entry. So this solution specifically i have given for this type of situation where you dont want to show ARP vendor entry.

0 votes
Eshwar's picture
Eshwar
1 year 1 week ago

Wrapper on MSI?

Deepanshu,
Help me to understand the context.

Are you trying to create a wrapper [dummy MSI] to install your packaged MSI?

Coz i've created wrappers to install Security Patches [not MSIs]. The wrapper MSI will copy patch to the machine and executes it.
In that case there shouldn't be wrapper MSI's entry in Add/Remove programs, coz its a wrapper.

Thanks,
Eshwar

Thanks,
Eshwar

+3 (3 votes)
Deepanshu's picture
Deepanshu
1 year 5 days ago

Eshwer

here wrapper means we have a template. after creating the MSI we will execute the MSI through this template and in ADD\Remove only wrapper entry should visible not MSI so this concept is useful for this type of scenarios.

Cheers
Deepanshu

0 votes