I've never used, but in Installshield MSI project you can do this through Component Services or with: http://msdn.microsoft.com/en-us/library/aa242178(v=vs.60).aspx regards Markus ... View more

Start->Adminstrative Tools->Component Services. There Component Services->Computers->My Computer->DCOM config. Select the appropriate com server, properties->general. There you can select the activation level. ... View more

Take a look at installsite.org, there you find this code snippet: http://www.installsite.org/files/NetShareRul.zip regards Markus ... View more

See here for information: http://helpnet.installshield.com/installshield21helplib/installshield21helplib.htm#StartTopic=helplibrary/CompilingA5xScriptInDevStudio.htm regards Markus ... View more

May be a stupid question, but why use a "regedit" to write to the registry. Why not using basic MSI registry functionality in a component, or installscript in a custom action. And if "active setup" is through windows activated on 64-Bit and you call "regedit", which version is used from windows ? "%systemroot%\system32\regedit" (64-bit process) or "%systemroot%\syswow64\regedit" (32-bit process) regards Markus ... View more

Dan, here is also a very helpful article, especially the comment from Christopher Painter ! http://blogs.flexerasoftware.com/installtalk/2011/11/using-active-setup-to-repair-user-settings.html will try your area51.msi later. regards Markus ... View more

Never tried myself but STANDARD_RIGHTS_ALL or GENERIC_ALL should do this. ... View more

When I create new prerequisites I use a virtual machine, create a snapshot of my c-drive and a snapshot of the registry. Then install the i.e. VC 2013 runtime. Then compare the snapshots with the current state of your files and registry. Then you can create new "exit conditions". I use BeyondCompare, but there are also tools from Microsoft to do this. regards Markus ... View more

search in the InstallShield Help Library for "SetObjectPermissions" ... View more

Hello Marco, I think the -6038 error comes from the release setting in IS12 Setup Launcher see below. Before you upgrade your project open in IS12 and select an option without the Windows 9x MSI engine included. Save and if you upgrade to IS2014 this warning should be solved. The next one -7235 from the software identification tag could be resolved if you disable this in the general information "Use Software Identification Tag" -> No. hope that helps you a little bit. ... View more

You need the "REGDB_OPTION_WOW64_64KEY"-Option to read the 64-Bit part of the registry´. Read the section: http://helpnet.flexerasoftware.com/installshield20helplib/Content/helplibrary/Targeting64Bit-IS.htm regards Markus ... View more

Try to take a look at the user's guide and search for Disable(WOW64FSREDIRECTION). May be this solves your problem. ... View more

What project type is it Installscript, Basic MSI or InstallScript MSI ? ... View more

I had a similar problem in the past when I moved from 32-bit host to 64-bit host machine. This thread solved my problem: http://community.flexerasoftware.com/showthread.php?192471-COM-extract-problem-32-bit-vs-64-bit-OS&highlight=OAPERUSERTLIBREG ... View more

Have you tried to set the "Required Execution Level" to "Administrator". Then you can only execute the setup.exe if you have Admin rights. Not exactly what you want, but eventually sufficient. regards Markus ... View more