...@verizon.net
To: wix-users@lists.sourceforge.net
Sent: Sunday, February 9, 2014 3:13 PM
Subject: Re: [WiX-users] XP Install Error 0x80070001 Access is denied
Could I please have a straightforward answer as to why WiX is changing the
LogonUser from the logged on user to SYSTEM
when InstallScope
Some rambling comments:
First thing: it's already been said but this whole thing of running
cmd.exe is a bad idea, especially when there is an alternative, the
WiX copyfile element . You should be using it, that's the point being
made, the built-in MSI capability of copying files, table driven,
Could I please have a straightforward answer as to why WiX is changing the
LogonUser from the logged on user to SYSTEM
when InstallScope is set to perMachine on XP installs? On Win7 the LogonUser
remains the logged on user.
Thank you.
On 02/09/2014 02:43 PM, Phil Wilson wrote:
Some
It's not Wix, it's MSI.
A detailed install log might show when the user is set.
Dave
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Sent: Sunday, February 9, 2014 3:13 PM
Subject: Re: [WiX-users] XP Install Error 0x80070001 Access
I don't know for a fact because there is a CA processes firing off a
process firing off a process but. if any of the things in that
chain are a ShellExecute type of process initiation then there will
not be any transfer of privilege into the process and you'll see
access denied. That's why
If I take out the InstallScope then the install succeeds on XP (of course Win 7
w/UAC then fails).
If I leave in the InstallScope then the reverse is true.
With the InstallScope, on XP the LogonUser ends up being SYSTEM whereas without
InstallScope it is the logged on user.
This is what is
I now have this half-way working.
Installing on Windows 7 w/UAC succeeds
Installing on Windows XP fails
In .wxs:
InstallScope=perMachine
InstallPrivileges=elevated
CopyFile is setup in an immediate property and then executed deferred
without impersonation.
XP Install Log
It knows about our custom actions as well and they rollback just fine.
On 02/06/2014 09:42 PM, David Connet wrote:
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about it (hence
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about it (hence handles
uninstall, rollback, upgrade, etc).
Dave
On 2/6/2014 5:35 PM, Gerry Reno wrote:
Ok, after some experiments:
The
Ok, after some experiments:
The copy file is like this:
CustomActionSchedule(Action=CopyFile,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData=cmd.exe
/c
copy C:\Program Files\OURCOMPANY\OURPRODUCT\OURFILE.exe
C:\OURSTUFF\[LogonUser]\ADIRECTORY\\)
And now since I added
10 matches
Mail list logo
