Re: [WiX-users] Vista Standard User and perMachine install
Hi there, I am using setupbld to create a setup.exe from my msi. Using the command: SETUPBLD -title MyApp -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe However, I get a strange difference between the exe msi installer version. Running the installer with the application already installed: with MyAppSetup.msi it shows up the Change, Repair, Remove dialog as expected. with MyAppSetup.exe it proceeds to a repair install and no Change, Repair, Remove dialog like I got when I ran the msi installer. Any ideas why this is so anyone or is this normal ? Would be slightly concerned releasing setup.exe showing this behaviour. Also, is it possible to add external cabs to my setup.exe using setupbld? thanks very much! _ Chat to your friends for free on selected mobiles http://clk.atdmt.com/UKM/go/174426567/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Thanks for the help, I tried it without InstallPrivileges=elevated and it
almost got it to work. Both methods ('Condition' element and type 19 custom
action) appear to have the same net effect.
XP works great and stops the install if not an admin. That fine and is what I
want. Vista however is different. If logged in as admin, double clicking the
msi to launch the install doesn't recognise Im admin stops with my error
message. Under the same admin login, if I open a command prompt as
administrator and run msiexec /i myinstall.msi , the installer now detects
admin and continues fine. Great! But what sane user is going to want to run an
installer from the command prompt as administrator ;(
Here is my Custom action
InstallUISequence
Custom Action=IsPrivileged Before=LaunchConditionsNot
AdminUser/Custom
Show Dialog=OldVerDetected
After=FindRelatedProductsREMOVEOLDPRODUCT/Show
/InstallUISequence
Is UISequence the correct place for this stuff? Also note I need to set the
MSIUSEREALADMINDETECTION property to 1 for this to work.
After trying all this it seems (in this case) msi cannot detect if I am an
admin user in Vista. What about creating a bootsrap setup.exe which runs my
installer using msiexec like I did the command prompt. Is that whats normally
done to get round this type of problem?
Lastly I noticed when using:
Condition Message=You must be an admin to install this product.Not
AdminUser/Condition
No Launch Condition Table is created when I open the msi in Orca, even though
the condition seems to work (at least for XP and vista standard user). Why is
that?
_
With Windows Live, you can organise, edit, and share your photos.
http://clk.atdmt.com/UKM/go/134665338/direct/01/
--
Come build with us! The BlackBerryreg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9#45;12, 2009. Register now#33;
http://p.sf.net/sfu/devconf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
In XP: you either are an administrator or you are not. It is simple.
In Vista with UAC turned off: Same as XP.
In Vista with UAC turned on: Administrators are not an administrator until
they elevate (via the consent dialog). Non-administrators can also elevate
via the same mechanism by supplying an administrator's credentials.
To prevent breaking older installation packages, on Vista without
MSIUSEREALADMINDETECTION set, AdminUser (and Privileged) are always set,
since the user can (in theory) always supply the credentials needed to the
consent dialog.
Privileged means that either the user can install or would be able to
install by supplying credentials. AdminUser (if MSIUSERREALADMINDETECTION is
set to 1) means that you have a token that has the administrator's groups
privileges enabled. The non-elevated token of the your admin doesn't have
those set.
Typically, what people have done is not set MSIUSEREALADMINDETECTION, test
for the condition of Privileged, and expect that the following happens:
If the installation could succeed on XP, the condition passes, otherwise it
fails.
The condition always passes on Vista (on the assumption that the user will
later see the consent dialog), and the user must navigate the consent dialog
in order to complete the installation.
I'm sure you have a justification to not allow Vista standard users from
attempting perMachine installations, but the reason for the changes above
was to enable what is called over-the-shoulder permission: standard users
starts installation, gets consent dialog, administrator comes by and
supplies credentials, installation completes. That is easier than the XP
model of logout, login as admin, run installation, logout, log back in as
user.
-Original Message-
From: warne warne [mailto:warne...@hotmail.com]
Sent: Friday, September 25, 2009 1:25 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Vista Standard User and perMachine install
Thanks for the help, I tried it without InstallPrivileges=elevated and it
almost got it to work. Both methods ('Condition' element and type 19 custom
action) appear to have the same net effect.
XP works great and stops the install if not an admin. That fine and is what
I want. Vista however is different. If logged in as admin, double clicking
the msi to launch the install doesn't recognise Im admin stops with my
error message. Under the same admin login, if I open a command prompt as
administrator and run msiexec /i myinstall.msi , the installer now detects
admin and continues fine. Great! But what sane user is going to want to run
an installer from the command prompt as administrator ;(
Here is my Custom action
InstallUISequence
Custom Action=IsPrivileged Before=LaunchConditionsNot
AdminUser/Custom
Show Dialog=OldVerDetected
After=FindRelatedProductsREMOVEOLDPRODUCT/Show
/InstallUISequence
Is UISequence the correct place for this stuff? Also note I need to set the
MSIUSEREALADMINDETECTION property to 1 for this to work.
After trying all this it seems (in this case) msi cannot detect if I am an
admin user in Vista. What about creating a bootsrap setup.exe which runs my
installer using msiexec like I did the command prompt. Is that whats
normally done to get round this type of problem?
Lastly I noticed when using:
Condition Message=You must be an admin to install this product.Not
AdminUser/Condition
No Launch Condition Table is created when I open the msi in Orca, even
though the condition seems to work (at least for XP and vista standard
user). Why is that?
_
With Windows Live, you can organise, edit, and share your photos.
http://clk.atdmt.com/UKM/go/134665338/direct/01/
--
Come build with us! The BlackBerryreg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9#45;12, 2009. Register now#33;
http://p.sf.net/sfu/devconf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Come build with us! The BlackBerryreg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9#45;12, 2009. Register now#33;
http://p.sf.net/sfu/devconf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Hi thanks, but the privileged property is always 1 regardless if Im standard, or admin user. As I was saying I have InstallScope=perMachine InstallPrivileges=elevated in my package element. Is that setting privileged to 1 by any chance? I thought by doing that it would inform msi that this installer requires admin rights to install? _ Share your photos with Windows Live Photos – Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/ -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
If you set Privileged to 1, you are overriding whatever setting Windows Installer had generated. Don't set it, just consume it in your conditions. Installer sets it for you if appropriate. InstallPrivilages=elevated tells Windows Installer that you need admin rights. (Really it suppresses telling Windows Installer that you don't need them, but by implication...) -Original Message- From: warne warne [mailto:warne...@hotmail.com] Sent: Thursday, September 24, 2009 11:24 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista Standard User and perMachine install Hi thanks, but the privileged property is always 1 regardless if Im standard, or admin user. As I was saying I have InstallScope=perMachine InstallPrivileges=elevated in my package element. Is that setting privileged to 1 by any chance? I thought by doing that it would inform msi that this installer requires admin rights to install? _ Share your photos with Windows Live Photos - Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/ -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
I frequently lose track of all this, but I think (well for today at least): 1) You can't trust Privileged when there is going to be an elevation prompt in the execute sequence. The UI sequence can be untrustworthy. If you want older semantics, set the MSIUSEREALADMINDETECTION property to get it set for the UI sequence. 2) As a result of 1) the recommended way to stop if the user does not have privilege is to use a type 19 custom action in the Execute sequence to terminate the setup if Privileged is not 1. 3) The MsiRunningElevated property is relevant too, and although I haven't looked at it in detail I believe it will get set in situations (like maintenance mode) where Privileged might not. Phil Wilson -Original Message- From: Blair [mailto:os...@live.com] Sent: Thursday, September 24, 2009 3:19 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Vista Standard User and perMachine install If you set Privileged to 1, you are overriding whatever setting Windows Installer had generated. Don't set it, just consume it in your conditions. Installer sets it for you if appropriate. InstallPrivilages=elevated tells Windows Installer that you need admin rights. (Really it suppresses telling Windows Installer that you don't need them, but by implication...) -Original Message- From: warne warne [mailto:warne...@hotmail.com] Sent: Thursday, September 24, 2009 11:24 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista Standard User and perMachine install Hi thanks, but the privileged property is always 1 regardless if Im standard, or admin user. As I was saying I have InstallScope=perMachine InstallPrivileges=elevated in my package element. Is that setting privileged to 1 by any chance? I thought by doing that it would inform msi that this installer requires admin rights to install? _ Share your photos with Windows Live Photos - Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/ -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
I use the Privileged property in a LaunchCondition to do exactly that Warne it works without fail. Tested it on XP, XP64, Vista Vista64 Virtual machines with user accounts which are only members of the User group it always works. If you're checking during InstallExecute the MSI needs to be elevated at that point otherwise it can't make any per-machine changes so it'll always return true or as Sascha says the machine itself may be the issue. This is one of the things VM's are so good at. See http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/ Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] Sent: 23 September 2009 01:51 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Vista Standard User and perMachine install From the documentation: The Privileged property indicates whether the installation is performed in the context of elevated privileges. The installer sets this property if the user has administrator privileges, if the application has been assigned by a system administrator, or if both the user and machine policies AlwaysInstallElevated are set to true. I'd check the MSI logs to see if AlwaysInstallElevated is set true for both machine and user. On Sat, Sep 19, 2009 at 8:30 AM, warne warne warne...@hotmail.com wrote: Is there a property I could check for that is set when either a XP Limited or Vista Standard user runs my installer? I tried 'AdminUser' 'Privileged but it seems they are always '1' regardless if I run the setup logged in as an administrator or not. thanks very much, -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
From the documentation: The Privileged property indicates whether the installation is performed in the context of elevated privileges. The installer sets this property if the user has administrator privileges, if the application has been assigned by a system administrator, or if both the user and machine policies AlwaysInstallElevated are set to true. I'd check the MSI logs to see if AlwaysInstallElevated is set true for both machine and user. On Sat, Sep 19, 2009 at 8:30 AM, warne warne warne...@hotmail.com wrote: Is there a property I could check for that is set when either a XP Limited or Vista Standard user runs my installer? I tried 'AdminUser' 'Privileged but it seems they are always '1' regardless if I run the setup logged in as an administrator or not. thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Is there a property I could check for that is set when either a XP Limited or Vista Standard user runs my installer? I tried 'AdminUser' 'Privileged but it seems they are always '1' regardless if I run the setup logged in as an administrator or not. thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Even with WIXUI_INSTALLDIR you can set the default to a per-user location, and launching the app after installation generally also does not generally require admin privs so that also does not prevent perUser. In that pure perUser package, they would get an error if they tried to navigate to and install under ProgramFiles. It is true that using the VC .msm modules does require perMachine. However, you can use the Deploying Visual C++ library DLLs as private assemblies method instead of using the MSM modules to use the CRT for perUser applications, but you lose the ability to have Microsoft service your CRT DLLs using publisher's redirection that way (you will have to update your packages and ship the updates yourself to your users whenever MSFT updates them just like any other security fix). http://msdn.microsoft.com/en-us/library/ms235291.aspx : last section http://msdn.microsoft.com/en-us/library/ms235316.aspx : scenario #3 The mail you linked to shows just some of the grief caused by mixing perUser with perMachine, not by pure perUser. You can set a launch condition to prevent a user from setting ALLUSERS and running your installation package (assuming they don't modify the MSI), which would help mitigate the grief by preventing it in the first place. The intigorose.com page's list of grief is also caused by mixing perUser and perMachine (which is usually caused by setting ALLUSERS=2, which some tutorials/examples/other environments did/do by default) which is NOT a recommended practice (in fact, I remember reading someone's blog about ALLUSERS=2 being broken under UAC and recommending all computer shops ban that value, but I didn't notice it doing a quick search). You need to know the technologies and platforms you support, and how to limit your packages to the kinds of deployments you intend to support on those platforms. That includes adding launch conditions to prevent other's attempts to install things in a different way than you intend them to be deployed. Know also that each team at MSFT has their own goals and don't always coordinate with each other on making sure that the results are truly best practice or even possible on all the various platforms they collectively produce. Deployment is a technology platform area as large as .NET or Java or LAMP or any other, yet it often doesn't get the respect that is required to have it addressed in projects as it should to prevent these kinds of issues. Just as that happens at most other companies on the planet, it also happens at MSFT (they are humans more-or-less like the rest of us after allgrin/). Also, often things are supported that are no longer really supported or recommended because they go against newer knowledge about how to maintain platform security, and so some advice given 10 years ago is now considered exactly counter to how it should be done today. -Original Message- From: warne warne [mailto:warne...@hotmail.com] Sent: Friday, September 11, 2009 6:11 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista Standard User and perMachine install Thanks thats certainly clarified it. My install is a 'WIXUI_INSTALLDIR' type so from what I read here: http://www.indigorose.com/webhelp/msifact/Concepts/Per-Machine_vs._Per-User_ Installations.htm that rules out perUser install. I also use a custom action to launch my app after install and Visual C merge .msm modules which, as Blair mentioned, may also rule out the perUser install. Would I be wrong then in thinking perUser installs are to be avoided generally speaking? Just perUser seems to cause grief. For example: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg26517.html _ Use Hotmail to send and receive mail from your different email accounts. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Outstanding, thanks again for all the help. _ Save time by using Hotmail to access your other email accounts. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Vista Standard User and perMachine install
Hi there, My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package' element and thats fine. Just wondering then, is there any way to get round vista's UAC for users without admin rights ie 'Standard Users' ? They get the old You do not have sufficient priviliges etc message during install. I understand that is entirely by design but, nonetheless, I would still like them to be able to install. I dont want to allow a 'perUser' install for possible upgrade/uninstall problems later on down the road that I read all about. I set InstallPrivileges=limited in the Package element also but that just gets over the initial setup part. Is there an MSIEXEC command I could use as part of a bootstrap for example? thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
It's all about where you're deploying to and what CAs you're running. If you're operating outside of the user's profile then you'll get a UAC prompt if it's enabled. 2009/9/11 warne warne warne...@hotmail.com: Hi there, My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package' element and thats fine. Just wondering then, is there any way to get round vista's UAC for users without admin rights ie 'Standard Users' ? They get the old You do not have sufficient priviliges etc message during install. I understand that is entirely by design but, nonetheless, I would still like them to be able to install. I dont want to allow a 'perUser' install for possible upgrade/uninstall problems later on down the road that I read all about. I set InstallPrivileges=limited in the Package element also but that just gets over the initial setup part. Is there an MSIEXEC command I could use as part of a bootstrap for example? thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
Per-machine is exactly that: all users on that machine. Anything that affects more than the current user is supposed to require admin privileges to accomplish (that is why opening the clock/calendar in the task bar on XP requires admin privileges) as a basic tenant of machine stability (and reducing the impact of viruses and other malware). As a result, all workarounds, in order to maintain basic machine security, require administrative privilege to setup, which means successfully navigating the UAC prompt as part of your installation routine. If you author your application in such a way as to be completely per-user (and not ever need anything that is a protected per-machine resource) you can do pure per-User installations and each installation will be completely independent of all others (as if they were on separate computers). Of course, some things can't be done this way (drivers, services, GAC, native SxS) but most probably software can (in fact, OneClick is based entirely on a per-User model) even though as an industry we aren't used to it. Of course this also means installing your code somewhere other than ProgramFiles. It also means not using the Windows Firewall APIs or other similar things. It also means not installing the MSM version of the native C/C++ libraries. OTOH, if you are not using Windows/Microsoft Update to service your application (and non-MSFT groups that are not distributing drivers currently can't AFAIK) that won't be an issue. It also means that each user that installs your application will have separate copies (but disk space isn't the issue it once was for most users). COM has a per-user variation, and most hosts don't care, so you can even deploy COM (even in Internet Explorer) per-user. .NET can run full trust without being installed to the GAC from a per-user installation as well, and start menu items/desktop icons/quick-launch-bar icons are all available to you from those installations. -Original Message- From: warne warne [mailto:warne...@hotmail.com] Sent: Friday, September 11, 2009 12:49 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Vista Standard User and perMachine install Hi there, My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package' element and thats fine. Just wondering then, is there any way to get round vista's UAC for users without admin rights ie 'Standard Users' ? They get the old You do not have sufficient priviliges etc message during install. I understand that is entirely by design but, nonetheless, I would still like them to be able to install. I dont want to allow a 'perUser' install for possible upgrade/uninstall problems later on down the road that I read all about. I set InstallPrivileges=limited in the Package element also but that just gets over the initial setup part. Is there an MSIEXEC command I could use as part of a bootstrap for example? thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista Standard User and perMachine install
I'll just add (and risk stating the obvious) that if a limited user could actually perform an install that changed areas on the system that are restricted to administrators, then that would be one heck of a security hole. Administrator credentials have to be supplied somewhere, whether it's an over the shoulder install or a group policy push to the machine from a server somewhere. Phil Wilson -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, September 11, 2009 2:04 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Vista Standard User and perMachine install Per-machine is exactly that: all users on that machine. Anything that affects more than the current user is supposed to require admin privileges to accomplish (that is why opening the clock/calendar in the task bar on XP requires admin privileges) as a basic tenant of machine stability (and reducing the impact of viruses and other malware). As a result, all workarounds, in order to maintain basic machine security, require administrative privilege to setup, which means successfully navigating the UAC prompt as part of your installation routine. If you author your application in such a way as to be completely per-user (and not ever need anything that is a protected per-machine resource) you can do pure per-User installations and each installation will be completely independent of all others (as if they were on separate computers). Of course, some things can't be done this way (drivers, services, GAC, native SxS) but most probably software can (in fact, OneClick is based entirely on a per-User model) even though as an industry we aren't used to it. Of course this also means installing your code somewhere other than ProgramFiles. It also means not using the Windows Firewall APIs or other similar things. It also means not installing the MSM version of the native C/C++ libraries. OTOH, if you are not using Windows/Microsoft Update to service your application (and non-MSFT groups that are not distributing drivers currently can't AFAIK) that won't be an issue. It also means that each user that installs your application will have separate copies (but disk space isn't the issue it once was for most users). COM has a per-user variation, and most hosts don't care, so you can even deploy COM (even in Internet Explorer) per-user. .NET can run full trust without being installed to the GAC from a per-user installation as well, and start menu items/desktop icons/quick-launch-bar icons are all available to you from those installations. -Original Message- From: warne warne [mailto:warne...@hotmail.com] Sent: Friday, September 11, 2009 12:49 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Vista Standard User and perMachine install Hi there, My setup is a perMachine (ALLUSERS=1) install which I set in the 'Package' element and thats fine. Just wondering then, is there any way to get round vista's UAC for users without admin rights ie 'Standard Users' ? They get the old You do not have sufficient priviliges etc message during install. I understand that is entirely by design but, nonetheless, I would still like them to be able to install. I dont want to allow a 'perUser' install for possible upgrade/uninstall problems later on down the road that I read all about. I set InstallPrivileges=limited in the Package element also but that just gets over the initial setup part. Is there an MSIEXEC command I could use as part of a bootstrap for example? thanks very much, _ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design
Re: [WiX-users] Vista Standard User and perMachine install
Thanks thats certainly clarified it. My install is a 'WIXUI_INSTALLDIR' type so from what I read here: http://www.indigorose.com/webhelp/msifact/Concepts/Per-Machine_vs._Per-User_Installations.htm that rules out perUser install. I also use a custom action to launch my app after install and Visual C merge .msm modules which, as Blair mentioned, may also rule out the perUser install. Would I be wrong then in thinking perUser installs are to be avoided generally speaking? Just perUser seems to cause grief. For example: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg26517.html _ Use Hotmail to send and receive mail from your different email accounts. http://clk.atdmt.com/UKM/go/167688463/direct/01/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
