Thanks Sascha.
Yes, we have some enterprise customers. As what I just replied to Phil's email, that's no problem for us. The problem is our QA insist on this use case: the end user "run as admin" and further the application is launched "as admin" as well, then the settings will be saved in admin folder. Then next time, when the user run the application as a standard user, she will find her settings are gone. Actually not gone, but in admin folder. Even though I don't believe this is a valid use case, but I do own our QA a clear explanation about whether this can be done. So let's back to the original question, is possible to "run as admin" but "launch application as standard user"? Do you know how to use MSIREALADMINDETECTION to detect if the invoker is admin or not? Some example will be appreciated. Thanks. ________________________________ From: Sascha Beaumont <sascha.beaum...@gmail.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Wed, December 16, 2009 9:06:00 PM Subject: Re: [WiX-users] How to launch application as Standard User while the installer ran as Admin I agree with Phil here, If your customer base is in the corporate world, having an "Enterprise ready" installation is a must. One that can run with no user interaction, be configured pre-install and pushed out via GPO/AD (Group Policy Objects/Active Directory) so that the end user (non-Admin) can run the software without additional configuration, license keys, etc. i.e. If you have 5,000 workstations, you're not going to manually have an Administrator enter the license key on each one are you :) Sascha On Thu, Dec 17, 2009 at 12:14 PM, Wilson, Phil <phil.wil...@wonderware.com> wrote: > GPO is Group Policy Object. I think that's the right acronym, but anyway > larger enterprises don't (for example) install Office on every system by > going to each one and installing it. They assign it via group policy and have > it install in admin mode even if users are not administrators. This kind of > thing: > > http://technet.microsoft.com/en-us/library/cc179214.aspx > > and this where they talk about config files and the ability to specify > license using PIDKEY. > > http://technet.microsoft.com/en-us/library/cc179195.aspx > > If your customers include enterprises that do that kind of deployment your > product will be seen as much better than one that requires visiting each > workstation for installation or license key configuration. > > Phil Wilson > > > -----Original Message----- > From: little.forest [mailto:little.for...@ymail.com] > Sent: Wednesday, December 16, 2009 3:57 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] How to launch application as Standard User while the > installer ran as Admin > > Thanks Phil. > > > For #1, in the old version of our software, the license key was kept in a > common place. In this new version, it's changed. I agree with you for this > point. I'll talk to our team to put license key in a common place. It'll make > sense to put it in a common place as we support per-machine install. > > For #2, we could do that. But our QA also argued that "all settings" were > saved in admin folder instead of user's local folder. Anyways, I think what > our QA wanted is, "run as admin" but launch application "as standard user". > I'm not sure if this is possible. Can you tell me if it's possible? > > Also, what does "GPO" mean? > > Thanks! > > > > ________________________________ > From: "Wilson, Phil" <phil.wil...@wonderware.com> > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Sent: Wed, December 16, 2009 3:29:57 PM > Subject: Re: [WiX-users] How to launch application as Standard User while the > installer ran as Admin > > ..and a couple of things that don't make sense to me: > > 1. There are always likely to be cases (admin install, over the shoulder, > group policy) where somebody else is doing the install on behalf of a user. > So what seems odd to me is Brian's comment that the key is in the wrong place > because it's in the installing user's profile folder. Why not just install it > in some common area in the first place? It's not as if you can't > sub-directory the keys for each user in that location if necessary. > > 2. This sounds like standard data collection, so why not just have the user > enter the key in a user sequence dialog, and have MSI put it somewhere on the > system for you? Then you're not running programs with the wrong account. > Also, if it's an installer property then it also enables silent installs, GPO > installs. Have you looked at the PIDKEY property, for example? > > Phil Wilson > > > -----Original Message----- > From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] > Sent: Wednesday, December 16, 2009 1:34 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] How to launch application as Standard User while the > installer ran as Admin > > Check out http://blogs.msdn.com/rflaming/archive/2006/09/21/765665.aspx > > You can probably use MSIREALADMINDETECTION to make the AdminUser > property behave as you require. > > > Sascha > > > On Thu, Dec 17, 2009 at 6:08 AM, little.forest <little.for...@ymail.com> > wrote: >> Our installer needs Admin right to run. So a "Standard user" has to run the >> installer "run as Admin". On the final page of the installer, we have a >> "Launch application" option. So the user can check that option and launch >> the application. Our application will ask a license key. The user inputs the >> license key. But the key will be saved in "C:\Documents and >> Settings\Administrator\Application Data" folder. Then the user exits the >> application. And run the application again by using the normal "Standard >> user" privilege. Then the application will ask the license key again, >> because the license key wasn't saved in the right folder such as >> "C:\Documents and Settings\JoeSmith\Application Data". >> >> How to resolve this problem? >> >> I'm thinking two options: >> 1. The user can "run as admin". But the application will be launched by >> using "Standard user". This way, the license key input by the user will be >> saved in the correct spot, namely, the users setting folder like >> "C:\Documents and Settings\JoeSmith\Application Data". But how to do it? >> 2. If there is a way that the installer can detect this installation was >> from "run as admin", then set a property. Then in the final page's launch >> application option, we'll check this property. If it's set then we disable >> the "launch application" option. This will stop the user "running the >> application as admin" - they don't need to input license key two times. Is >> there a way to detect if the installation "run as admin"? >> >> By the way, we're using the code example from Wix.chm "How To: Run the >> Installed Application After Setup" section. >> >> Thanks in advance. >> /Brian >> >> >> __________________________________________________________________ >> Make your browsing faster, safer, and easier with the new Internet >> Explorer(r) 8. Optimized for Yahoo! Get it Now for Free! at >> http://downloads.yahoo.com/ca/internetexplorer/ >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then delete > this message from your system. Please do not copy it or use it for any > purposes, or disclose its contents to any other person. This email comes from > a division of the Invensys Group, owned by Invensys plc, which is a company > registered in England and Wales with its registered office at Portland House, > Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of > European legal entities within the Invensys Group, please go to > http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. > You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail > inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries and > affiliates). > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > __________________________________________________________________ > Looking for the perfect gift? Give the gift of Flickr! > > http://www.flickr.com/gift/ > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then delete > this message from your system. Please do not copy it or use it for any > purposes, or disclose its contents to any other person. This email comes from > a division of the Invensys Group, owned by Invensys plc, which is a company > registered in England and Wales with its registered office at Portland House, > Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of > European legal entities within the Invensys Group, please go to > http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. > You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __________________________________________________________________ Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
