Installations to run on VISTA and the ALLUSERS property.... Superfreak3 <Matt.Walker[ at ]synergis.com> 12.07.2007 14:10:28 I've read in several places that for installations that run on VISTA, ALLUSERS should be set to 1 and the User Information dialog bypassed on Vista. I just want to examine what I should do in prepping for VISTA. Currently with our installation, if a Standard User tries to install with UAC disabled, the installation fails due to lack of privileges to \Program Files, etc. During the UI, the controls on the User Information dialog are not displayed as the installing user is not Privileged. This seems to be an out-of-the-box condition in our authoring tool Wise for Windows Installer. If I install as Admin, all OK, or if UAC is enabled all is OK if Admin or if credentials are supplied. It's easy enough to do I would think. I could possibly condition the dialog with VersionNT<>600 and set the property with a Custom Action or possibly on the next button on the install dialog. If I do set ALLUSERS to 1, that would basically suggest that all would have to be Admin to install. When I tested this as a Standard User, no UAC, ALLUSERS=1, the install errored and none too gracefully. The log didn't really point to anything much either. I would have suspected a permissions message of some kind. Any thoughts, pointers would be Greatly Appreciated!

Re: Installations to run on VISTA and the ALLUSERS property.... "Phil Wilson" <phil.wilson[ at ]wonderware.something.com> 12.07.2007 17:27:53 Inline...... -- Phil Wilson [MVP Windows Installer] "Superfreak3" <Matt.Walker[ at ]synergis.com> wrote in message news:1184249428.586154.39180[ at ]r34g2000hsd.googlegroups.com... [Quoted Text] > I've read in several places that for installations that run on VISTA, > ALLUSERS > should be set to 1 and the User Information dialog bypassed on Vista. > I just want to examine what I should do in prepping for VISTA. [[This is a general recommendation, not just for Vista. ]] > Currently with our installation, if a Standard User tries to install > with UAC disabled, the installation fails due to lack of privileges > to > \Program Files, etc. During the UI, the controls on the User > Information dialog are not displayed as the installing user is not > Privileged. This seems to be an out-of-the-box condition in our > authoring tool Wise for Windows Installer. > > If I install as Admin, all OK, or if UAC is enabled all is OK if > Admin > or if credentials are supplied. [[ Limited users can't write to the ProgramFiles folder. This is not related to Vista except when administrators are running as limited and then get the same security limitations as limited users. ]] > It's easy enough to do I would think. I could possibly condition the > dialog with VersionNT<>600 and set the property with a Custom Action > or possibly on the next button on the install dialog. If I do set > ALLUSERS to 1, that would basically suggest that all would have to be > Admin to install. When I tested this as a Standard User, no UAC, > ALLUSERS=1, the install errored and none too gracefully. The log > didn't really point to anything much either. I would have suspected a > permissions message of some kind. > > Any thoughts, pointers would be Greatly Appreciated! > [[Using per-machine installs at all times is reasonable, no need to condition it on Vista. ]]

Re: Installations to run on VISTA and the ALLUSERS property.... Superfreak3 <Matt.Walker[ at ]synergis.com> 13.07.2007 13:24:28 On Jul 12, 1:27 pm, "Phil Wilson" <phil.wil...[ at ]wonderware.something.com> wrote: [Quoted Text] > Inline...... > > -- > Phil Wilson > [MVP Windows Installer] > > "Superfreak3" <Matt.Wal...[ at ]synergis.com> wrote in message > > news:1184249428.586154.39180[ at ]r34g2000hsd.googlegroups.com... > > > I've read in several places that for installations that run on VISTA, > > ALLUSERS > > should be set to 1 and the User Information dialog bypassed on Vista. > > I just want to examine what I should do in prepping for VISTA. > > [[This is a general recommendation, not just for Vista. ]] > > > Currently with our installation, if a Standard User tries to install > > with UAC disabled, the installation fails due to lack of privileges > > to > > \Program Files, etc. During the UI, the controls on the User > > Information dialog are not displayed as the installing user is not > > Privileged. This seems to be an out-of-the-box condition in our > > authoring tool Wise for Windows Installer. > > > If I install as Admin, all OK, or if UAC is enabled all is OK if > > Admin > > or if credentials are supplied. > > [[ Limited users can't write to the ProgramFiles folder. This is not related > to Vista except when administrators are running as limited and then get the > same security limitations as limited users. ]] > > > It's easy enough to do I would think. I could possibly condition the > > dialog with VersionNT<>600 and set the property with a Custom Action > > or possibly on the next button on the install dialog. If I do set > > ALLUSERS to 1, that would basically suggest that all would have to be > > Admin to install. When I tested this as a Standard User, no UAC, > > ALLUSERS=1, the install errored and none too gracefully. The log > > didn't really point to anything much either. I would have suspected a > > permissions message of some kind. > > > Any thoughts, pointers would be Greatly Appreciated! > > [[Using per-machine installs at all times is reasonable, no need to > condition it on Vista. ]] OK, so I'll set ALLUSERS=1, but in thinking about this, I don't know that I should only make the changes in the UI sequence. Our upgrade process executes the .msi silently so I guess I would have to set it in the Execute Immediate sequence as well. Where would be the best place to set this property? Would immediately after CostFinalize be OK?

Re: Installations to run on VISTA and the ALLUSERS property.... Superfreak3 <Matt.Walker[ at ]synergis.com> 13.07.2007 13:27:53 On Jul 12, 1:27 pm, "Phil Wilson" <phil.wil...[ at ]wonderware.something.com> wrote: [Quoted Text] > Inline...... > > -- > Phil Wilson > [MVP Windows Installer] > > "Superfreak3" <Matt.Wal...[ at ]synergis.com> wrote in message > > news:1184249428.586154.39180[ at ]r34g2000hsd.googlegroups.com... > > > I've read in several places that for installations that run on VISTA, > > ALLUSERS > > should be set to 1 and the User Information dialog bypassed on Vista. > > I just want to examine what I should do in prepping for VISTA. > > [[This is a general recommendation, not just for Vista. ]] > > > Currently with our installation, if a Standard User tries to install > > with UAC disabled, the installation fails due to lack of privileges > > to > > \Program Files, etc. During the UI, the controls on the User > > Information dialog are not displayed as the installing user is not > > Privileged. This seems to be an out-of-the-box condition in our > > authoring tool Wise for Windows Installer. > > > If I install as Admin, all OK, or if UAC is enabled all is OK if > > Admin > > or if credentials are supplied. > > [[ Limited users can't write to the ProgramFiles folder. This is not related > to Vista except when administrators are running as limited and then get the > same security limitations as limited users. ]] > > > It's easy enough to do I would think. I could possibly condition the > > dialog with VersionNT<>600 and set the property with a Custom Action > > or possibly on the next button on the install dialog. If I do set > > ALLUSERS to 1, that would basically suggest that all would have to be > > Admin to install. When I tested this as a Standard User, no UAC, > > ALLUSERS=1, the install errored and none too gracefully. The log > > didn't really point to anything much either. I would have suspected a > > permissions message of some kind. > > > Any thoughts, pointers would be Greatly Appreciated! > > [[Using per-machine installs at all times is reasonable, no need to > condition it on Vista. ]] OK, I'll set ALLUSERS by one of the means mentioned above, but I guess I should set it in the Execute Immediate sequence as well since our update/upgrade mechanism fires the .msi with silent parameters so the UI won't be traversed. Where would be the best place to set this? Would immediately following CostFinalize be OK?

Re: Installations to run on VISTA and the ALLUSERS property.... "Phil Wilson" <phil.wilson[ at ]wonderware.something.com> 13.07.2007 20:01:47 If you're forcing ALLUSERS to 1 all the time, you can just set it in the Property table with that vale. -- Phil Wilson [MVP Windows Installer] "Superfreak3" <Matt.Walker[ at ]synergis.com> wrote in message news:1184333068.196463.55520[ at ]22g2000hsm.googlegroups.com... [Quoted Text] > On Jul 12, 1:27 pm, "Phil Wilson" > <phil.wil...[ at ]wonderware.something.com> wrote: >> Inline...... >> >> -- >> Phil Wilson >> [MVP Windows Installer] >> >> "Superfreak3" <Matt.Wal...[ at ]synergis.com> wrote in message >> >> news:1184249428.586154.39180[ at ]r34g2000hsd.googlegroups.com... >> >> > I've read in several places that for installations that run on VISTA, >> > ALLUSERS >> > should be set to 1 and the User Information dialog bypassed on Vista. >> > I just want to examine what I should do in prepping for VISTA. >> >> [[This is a general recommendation, not just for Vista. ]] >> >> > Currently with our installation, if a Standard User tries to install >> > with UAC disabled, the installation fails due to lack of privileges >> > to >> > \Program Files, etc. During the UI, the controls on the User >> > Information dialog are not displayed as the installing user is not >> > Privileged. This seems to be an out-of-the-box condition in our >> > authoring tool Wise for Windows Installer. >> >> > If I install as Admin, all OK, or if UAC is enabled all is OK if >> > Admin >> > or if credentials are supplied. >> >> [[ Limited users can't write to the ProgramFiles folder. This is not >> related >> to Vista except when administrators are running as limited and then get >> the >> same security limitations as limited users. ]] >> >> > It's easy enough to do I would think. I could possibly condition the >> > dialog with VersionNT<>600 and set the property with a Custom Action >> > or possibly on the next button on the install dialog. If I do set >> > ALLUSERS to 1, that would basically suggest that all would have to be >> > Admin to install. When I tested this as a Standard User, no UAC, >> > ALLUSERS=1, the install errored and none too gracefully. The log >> > didn't really point to anything much either. I would have suspected a >> > permissions message of some kind. >> >> > Any thoughts, pointers would be Greatly Appreciated! >> >> [[Using per-machine installs at all times is reasonable, no need to >> condition it on Vista. ]] > > OK, so I'll set ALLUSERS=1, but in thinking about this, I don't know > that I should only make the changes in the UI sequence. Our upgrade > process executes the .msi silently so I guess I would have to set it > in the Execute Immediate sequence as well. Where would be the best > place to set this property? Would immediately after CostFinalize be > OK? >