Re: [WiX-users] Fallback when not getting admin rights
My understanding is that Heat should produce the same result (on a clean
machine) that regasm produces (unless the binary is 64-bit only or if it is an
EXE instead of a DLL). If the machine heat is running on already had the binary
registered then most of the time it won't work (you have to unregister
everything you intend to harvest before you run the harvester, at minimum).
> Date: Tue, 27 Aug 2013 12:01:35 +0200
> From: trond.ander...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Fallback when not getting admin rights
>
> Thank you for your feeback.
> > I forget what the DropBox install experience was, but when I look at
> > those shell extensions they are all in HKCU, so they are per-user and
> > not per-system. That might work for you too.
>
> I run Regshot on my computer and looked at the changes in registry. A lot
> of the changes are in HKU, but there are quite a few changes in HKLM as
> shown below.
>
> We are currently using regasm to get our shell extension registered. Is it
> possible to avoid using regasm for shell extension registration? Any
> pointers to how this can be achieved? Currently we are using custom tasks
> for this. Here is an example on how we do it:
>
>Value='"[NETFRAMEWORK40CLIENTINSTALLROOTDIR64]RegAsm.exe"
> /codebase "[INSTALLLOCATION]$(var.SE.TargetFileName)"' />
> DllEntry='CAQuietExec' Execute='immediate' Return='check' />
>
> Overview of registry changes while Dropbox installer was run:
>
> Keys added:
> HKLM\SOFTWARE\Microsoft\Windows Media Player
> NSS\3.0\Events\{7F6A42D2-D502-47C2-A2D4-A5A62B1226B7}
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3
>
> The first one probably doesn't matter for us, but we also will need icon
> overlay.
>
> Values added:
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1\:
> "{FB314ED9-A251-47B7-93E1-CDD82E34AF8B}"
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2\:
> "{FB314EDA-A251-47B7-93E1-CDD82E34AF8B}"
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3\:
> "{FB314EDB-A251-47B7-93E1-CDD82E34AF8B}"
> HKLM\SYSTEM\ControlSet001\Control\Session
> Manager\PendingFileRenameOperations: ...
> HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
> "v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
> HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
> "v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
> HKLM\SYSTEM\CurrentControlSet\Control\Session
> Manager\PendingFileRenameOperations: ...
> HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
> "v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
> HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
> "v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
>
>
> Not sure how many of these would be applicable for us. Firewall rules -
> probably not.
>
>
> Values modified:
> HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime: 75 A0 B5 46
> 5E A2 CE 01
> HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime: C7 D0 DD 4D
> 01 A3 CE 01
> HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
> 38 1D 55 ED 36 A2 CE 01
> HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
> 25 93 69 47 01 A3 CE 01
> HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009\Counter:
>
> There were some others in HKLM, but I don't think the Dropbox installer is
> responsible for these changes.
> ---
Re: [WiX-users] Fallback when not getting admin rights
Thank you for your feeback.
> I forget what the DropBox install experience was, but when I look at
> those shell extensions they are all in HKCU, so they are per-user and
> not per-system. That might work for you too.
I run Regshot on my computer and looked at the changes in registry. A lot
of the changes are in HKU, but there are quite a few changes in HKLM as
shown below.
We are currently using regasm to get our shell extension registered. Is it
possible to avoid using regasm for shell extension registration? Any
pointers to how this can be achieved? Currently we are using custom tasks
for this. Here is an example on how we do it:
Overview of registry changes while Dropbox installer was run:
Keys added:
HKLM\SOFTWARE\Microsoft\Windows Media Player
NSS\3.0\Events\{7F6A42D2-D502-47C2-A2D4-A5A62B1226B7}
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3
The first one probably doesn't matter for us, but we also will need icon
overlay.
Values added:
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1\:
"{FB314ED9-A251-47B7-93E1-CDD82E34AF8B}"
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2\:
"{FB314EDA-A251-47B7-93E1-CDD82E34AF8B}"
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3\:
"{FB314EDB-A251-47B7-93E1-CDD82E34AF8B}"
HKLM\SYSTEM\ControlSet001\Control\Session
Manager\PendingFileRenameOperations: ...
HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
"v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
"v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations: ...
HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
"v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
"v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|"
Not sure how many of these would be applicable for us. Firewall rules -
probably not.
Values modified:
HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime: 75 A0 B5 46
5E A2 CE 01
HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime: C7 D0 DD 4D
01 A3 CE 01
HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
38 1D 55 ED 36 A2 CE 01
HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
25 93 69 47 01 A3 CE 01
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009\Counter:
There were some others in HKLM, but I don't think the Dropbox installer is
responsible for these changes.
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fallback when not getting admin rights
I forget what the DropBox install experience was, but when I look at those shell extensions they are all in HKCU, so they are per-user and not per-system. That might work for you too. Phil Wilson On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen wrote: > I have an application which uses Shell extensions to add a menu in Windows > Explorer, however I would like the installer to have a fallback if the user > is not able to give the installer admin rights in which the user can access > the functionality without using menus/toolbar in Windows Explorer. The > Dropbox installer does the same thing. > > Does anyone have an example or other resources which could help me getting > this working. > > For information - I'm using WIX 3.7 and Burn bootstrapper. Is this > something the bootstrapper should handle? Will the Burn bootstrapper be > able to do this or do I have to use a different bootstrapper/modify Burn? > > > -- > Trond > > -- > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fallback when not getting admin rights
I have an application which uses Shell extensions to add a menu in Windows Explorer, however I would like the installer to have a fallback if the user is not able to give the installer admin rights in which the user can access the functionality without using menus/toolbar in Windows Explorer. The Dropbox installer does the same thing. Does anyone have an example or other resources which could help me getting this working. For information - I'm using WIX 3.7 and Burn bootstrapper. Is this something the bootstrapper should handle? Will the Burn bootstrapper be able to do this or do I have to use a different bootstrapper/modify Burn? -- Trond -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
