Ok...I was afraid of that :) but it's good to know I should change
direction.
Many thanks for your help,
Francesc
On Thu, Apr 15, 2010 at 12:23 AM, Sascha Beaumont wrote:
> Unfortunately, no.
>
> You're going to need to redesign your data migration process, possibly
> requiring a manual step
Unfortunately, no.
You're going to need to redesign your data migration process, possibly
requiring a manual step or separate tool that runs pre or post
install as the user.
Sascha
On Wed, Apr 14, 2010 at 11:02 PM, Francesc Castells
wrote:
> Thanks Sascha,
> >From your comment, I studied wh
Thanks Sascha,
>From your comment, I studied what is going on in the installer with the
impersonation, etc...and you'll probably scream here, but the thing is:
1- The installer is "per machine" and updates a "per user" installation
(this can't be changed)
2- It runs elevated, with admin rights, ot
Most likely your CA is running deferred and with elevated privileges,
try setting CustomAction/@Impersonate="true"
On Wed, Apr 14, 2010 at 12:53 AM, Francesc Castells
wrote:
> Hi,
> I have an installer that upgrades an old program and imports the data. To do
> that, it opens the old program's co
Hi,
I have an installer that upgrades an old program and imports the data. To do
that, it opens the old program's config file and gets the path to the data
files (an access .mdb file, for example). The problem is that most of the
times the data was stored in Program Files, so Vista has created a vi
5 matches
Mail list logo
