Been looking into this some more. I've asked the customer to log before and after (nothing yet) but in the meantime they found this article on how to elevate privileges for an MSI ( http://footheory.com/blogs/shane/archive/2007/08/03/vista-and-elevating-security-of-an-msi-to-run-as-administrator.aspx ).
Thats not the ONLY way to do this is it? Is the article author mistaken? I see UAC prompts come up when I run my MSI so I thought it would be OK. I'd hate to have to do a bodge because Vista has a security by obscurity flaw. Regards Ryan Rob Hamflett wrote: > The only thing that I can think to cause this would be if the command prompt > was elevated. Have you > tried logging the installation to see what the differences are? This article > explains how to turn > on global logging so you can get the logs for the double-click installation. > > http://support.microsoft.com/kb/223300 > > Rob > > Ryan O'Neill wrote: > >> Ah, sorry, didn't see you there amongst all the spam! >> >> I mean that from a command prompt it installs the Browser Helper Object >> DLL just fine, but when run via double clicking it does not. It appears >> to work the same but the DLL is not registered properly and does not get >> installed into IE. But, this is only on certain systems. I worry that >> they are doing something silly which they are not telling me about. >> >> Would the MSI run OK from UNC network share? I think they are doing >> this, which is the only major difference in the way I would run anything. >> >> Regards >> >> Ryan >> >> Rob Hamflett wrote: >> >>> You say it runs fine from a command prompt. How does it normally run? >>> >>> Rob >>> >>> Ryan O'Neill wrote: >>> >>> >>>> Anyone got a clue about this? I can't resolve it. >>>> >>>> Ryan O'Neill wrote: >>>> >>>> >>>>> Hi all, >>>>> >>>>> I have an installer that works great for all Win platforms, except Vista >>>>> where it will fail to register a DLL on specific machines. It runs on >>>>> most Vista installations fine (under admin and limited user accounts >>>>> which prompt for admin access). I did manage to get to a machine that >>>>> exhibited the issue yesterday and after running the MSI from the command >>>>> prompt, it installed correctly. I understand what happened there with >>>>> the automatically elevated privileges using the command prompt but I >>>>> can't understand why the normal UAC prompts did not allow the installer >>>>> to write the DLL registration to the registry. >>>>> >>>>> I think perhaps the systems it fails on have a policy that is >>>>> disallowing my installer registry writes, but I'm out of ideas. >>>>> >>>>> In testing it has proved to install correctly with; >>>>> a) Admin accounts. >>>>> b) Non admin accounts. >>>>> c) Non default user admin account. >>>>> >>>>> The method I am using to write to the registy is via the usual Registry >>>>> tag, as below; >>>>> <Component Id="C_MainDll" Guid="{XXXXXXXXX}"> >>>>> <Registry Root="HKLM" >>>>> Key="Software\Microsoft\Internet Explorer\Toolbar"> >>>>> <Registry Name="{YYYYYYYYYY}" Type="string" >>>>> Value="My toolbar" /> >>>>> </Registry> >>>>> <Registry Root="HKCR" Key="CLSID\{YYYYYY}" >>>>> Value="My toolbar" Type="string" /> >>>>> >>>>> Obviously there are many more registry tags as well. >>>>> >>>>> I'm really stuck here, it works on most Vista systems and then the >>>>> remainder it will work after being installed from the command prompt. >>>>> Any help would be very much appreciated. >>>>> >>>>> Thanks in advance, >>>>> >>>>> Ryan >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> This SF.net email is sponsored by: Microsoft >>>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>>> _______________________________________________ >>>>> WiX-users mailing list >>>>> WiX-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> >>>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
