We have a simple setup program that can install the program for the current user or machine. If they don't have admin rights, it's installed for the current user. If they have admin rights, they have the option to install for the machine or just themself. Based on their selection, our settings go into the HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER. WE use the HKEY_USER_SELECTABLE feature in IS to handle this automatically. That's great! However, we are running into a problem when people uninstall the program. Apparently, users (non-admin) can uninstall the program since it appears on their list of programs to add/remove. When they uninstall, the registry items in the HKEY_LOCAL_MACHINE registry can't be deleted because they don't have edit rights. 1. Is there a property we can set so that when it's installed for the machine, Admin rights are required to uninstall and non-Admin users never have see the program to uninstall? 2. Our setup program can detect if it's already installed on the machine or user. Is there a place in the script where we can check this when they try to uninstall with insufficient rights and stop them? If so, how? Thanks. ... View more

Is there a list of events and when and what order they are triggered? In particular, I'm interested in knowing when the setup is running in update mode (how can I tell?) so I can make some registry changes but I can't tell what events to add those adjustments. ... View more

I have a component I created for registry settings. It has its regstry settings in the HKEY_USER_SELECTABLE section so it can be installed for the user or machine. For machine installations on the 64-bit platform, it needs to be put in the root registry rather than the WOW3264Node. I learned I could change the registry component to a 64-bit component and that works. However, it then becomes a 64-bit components for the 32-bit build (setup). Is there a way to have the same component as 32 in one setup and 64 in another? Otherwise, I have to create two different components and manually keep them in sync forever. ... View more

I need to create a setup program that verifies the user has the latest version of their Office product (Access and Excel) installed on their machine and prompt them if they don't. For instance, Office 2007 has SP2. We've had some users get new machines and try to install our program and crashed because we weren't expecting them to have the original Office 2007 installed. A quick check in our setup program would tell them to update their version before installing ours. Thanks in advance. ... View more

I'm interested in distributing an Excel add-in. I see it involves adding an entry to the registry under: HKCU/software/Microsoft/Office/14.0/Excel/Options The entry is under OPEN, OPEN1, OPEN2, etc. depending on the other add-ins that are active. So I have a few questions: 1. I presume IS can't handle this without writing scripts. If there's a way to do this from the REGISTRY settings, that'd be great. How? 2. Programmatically, how do I determine and specify which OPEN entry to create? 3. How do I handle uninstall? The entry could change depending on the user adding or removing add-ins between when it's installed and uninstalled. What event should I use to detect and uninstall? Thanks. ... View more