UAC elevation/Administrator password prompting...
Posted: Tue Aug 06, 2013 6:45 pm
Hi,
Our company sells a product that is used by customers that may or may not use Group Policy (most probably don't); some customers are in big corporate environments but most are in smaller shops or indeed even single roaming users; some customers might be on WinXP, Win 7 (32 or 64-bit) or Win 8 (32 or 64-bit). The installers of our product might be folks that are Administrators within the domain all the way down to normal limited (non-Administrator) users. In other words, our app runs the full spectrum of install types. Our app doesn't use Windows Services, Administrative Tools, or any significant registry edits. The only registry edit we do currently is to the HKLM so our app appears in the Add/Remove Programs control panel applet.
Our full Setup exe might have a name like Setup_v110000.exe and our patch updates might have a name like Update_v110100.exe. We release a patch executable to some --but not all-- clients sometimes 2-3 times per month. Some clients would even like our update patches to occur silently once the user acknowledges that they would like to update to the latest release. We don't "require" any new data from the user during the installation of the update release, we only want to add or update our existing binary and flat-files. If we "add" a new files they are of the same class of files as what we installed during the full setup.
We want an installer product (we currently use Wise Installation System v9.02) that will allow for one of the following two scenarios, the 2nd would be the ideal, but the 1st would be entirely acceptable.
1) Require the Administrator to do the initial full setup install, and then allow that Administrator to say that future patch Update installations can be executed by the limited or standard user. Because our clients get frequent update releases they cannot be required ensure that an Administrator is available every time they get a new update. So our update releases should NOT do a UAC privilege elevation prompt. It can prompt with a Yes or No, but it cannot require the Administrator password.
Or,
2) Do NOT require the Administrator to do the initial full setup install; so a limited user account will do the initial and all subsequent update installs, without the need for an Administrator password.
Thanks.
Our company sells a product that is used by customers that may or may not use Group Policy (most probably don't); some customers are in big corporate environments but most are in smaller shops or indeed even single roaming users; some customers might be on WinXP, Win 7 (32 or 64-bit) or Win 8 (32 or 64-bit). The installers of our product might be folks that are Administrators within the domain all the way down to normal limited (non-Administrator) users. In other words, our app runs the full spectrum of install types. Our app doesn't use Windows Services, Administrative Tools, or any significant registry edits. The only registry edit we do currently is to the HKLM so our app appears in the Add/Remove Programs control panel applet.
Our full Setup exe might have a name like Setup_v110000.exe and our patch updates might have a name like Update_v110100.exe. We release a patch executable to some --but not all-- clients sometimes 2-3 times per month. Some clients would even like our update patches to occur silently once the user acknowledges that they would like to update to the latest release. We don't "require" any new data from the user during the installation of the update release, we only want to add or update our existing binary and flat-files. If we "add" a new files they are of the same class of files as what we installed during the full setup.
We want an installer product (we currently use Wise Installation System v9.02) that will allow for one of the following two scenarios, the 2nd would be the ideal, but the 1st would be entirely acceptable.
1) Require the Administrator to do the initial full setup install, and then allow that Administrator to say that future patch Update installations can be executed by the limited or standard user. Because our clients get frequent update releases they cannot be required ensure that an Administrator is available every time they get a new update. So our update releases should NOT do a UAC privilege elevation prompt. It can prompt with a Yes or No, but it cannot require the Administrator password.
Or,
2) Do NOT require the Administrator to do the initial full setup install; so a limited user account will do the initial and all subsequent update installs, without the need for an Administrator password.
Thanks.