Custom Action Condition - AllUsers vs NOT REINSTALL...

Hi there,

I'm testing my install on a Windows 7 machine and we do require admin
rights to install. With that, there is no problem.

Now, when a standard user log in, some User registry keys and the like
have to be 'repaired' or placed for that user. During this repair, I'm
getting two Custom Action errors that I think are related to rights
(both run in system context). During a repair, I don't really need
these actions to run.

What I was thinking of doing for these Deferred Custom actions if
certain properties are available... If possible could I condition with
NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
which is the better method.

Or, if there is something better, please let me know.

Thanks!

Have a condition of Not Installed on your custom actions, then they run only
on first install.
--
Phil Wilson
The Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972


"Superfreak3" <mawa316@rcn.com> wrote in message
news:bce746dc-88ff-4d90-adee-2e2a7a2af312@t23g2000yqt.googlegroups.com...
> Hi there,
>
> I'm testing my install on a Windows 7 machine and we do require admin
> rights to install. With that, there is no problem.
>
> Now, when a standard user log in, some User registry keys and the like
> have to be 'repaired' or placed for that user. During this repair, I'm
> getting two Custom Action errors that I think are related to rights
> (both run in system context). During a repair, I don't really need
> these actions to run.
>
> What I was thinking of doing for these Deferred Custom actions if
> certain properties are available... If possible could I condition with
> NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
> which is the better method.
>
> Or, if there is something better, please let me know.
>
> Thanks!

On Mar 5, 2:40*am, Sebastian Brand <sebast...@instyler.com> wrote:
> It depends on your custom actions I think. If their action is not
> required in a reinstall use the NOT REINSTALL attempt.
> When in repair mode, I think Privileged is handled the same way as in
> first installation so that wouldn't help either.
> What are the CA errors anyway?
>
> Best regards,
> Sebastian Brandhttp://blog.sebastianbrand.com
>
> On Mar 4, 11:05*pm, Superfreak3 <mawa...@rcn.com> wrote:
>
>
>
> > Hi there,
>
> > I'm testing my install on a Windows 7 machine and we do require admin
> > rights to install. With that, there is no problem.
>
> > Now, when a standard user log in, some User registry keys and the like
> > have to be 'repaired' or placed for that user. During this repair, I'm
> > getting two Custom Action errors that I think are related to rights
> > (both run in system context). During a repair, I don't really need
> > these actions to run.
>
> > What I was thinking of doing for these Deferred Custom actions if
> > certain properties are available... If possible could I condition with
> > NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
> > which is the better method.
>
> > Or, if there is something better, please let me know.
>
> > Thanks!- Hide quoted text -
>
> - Show quoted text -

Oh, I think OK. After checking my script I see that the action I was
concerned about is wrapped in a NOT PATCH block so it isn't currently
set to run during a patch.

It depends on your custom actions I think. If their action is not
required in a reinstall use the NOT REINSTALL attempt.
When in repair mode, I think Privileged is handled the same way as in
first installation so that wouldn't help either.
What are the CA errors anyway?


Best regards,
Sebastian Brand
http://blog.sebastianbrand.com

On Mar 4, 11:05*pm, Superfreak3 <mawa...@rcn.com> wrote:
> Hi there,
>
> I'm testing my install on a Windows 7 machine and we do require admin
> rights to install. With that, there is no problem.
>
> Now, when a standard user log in, some User registry keys and the like
> have to be 'repaired' or placed for that user. During this repair, I'm
> getting two Custom Action errors that I think are related to rights
> (both run in system context). During a repair, I don't really need
> these actions to run.
>
> What I was thinking of doing for these Deferred Custom actions if
> certain properties are available... If possible could I condition with
> NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
> which is the better method.
>
> Or, if there is something better, please let me know.
>
> Thanks!

On Mar 5, 2:40*am, Sebastian Brand <sebast...@instyler.com> wrote:
> It depends on your custom actions I think. If their action is not
> required in a reinstall use the NOT REINSTALL attempt.
> When in repair mode, I think Privileged is handled the same way as in
> first installation so that wouldn't help either.
> What are the CA errors anyway?
>
> Best regards,
> Sebastian Brandhttp://blog.sebastianbrand.com
>
> On Mar 4, 11:05*pm, Superfreak3 <mawa...@rcn.com> wrote:
>
>
>
> > Hi there,
>
> > I'm testing my install on a Windows 7 machine and we do require admin
> > rights to install. With that, there is no problem.
>
> > Now, when a standard user log in, some User registry keys and the like
> > have to be 'repaired' or placed for that user. During this repair, I'm
> > getting two Custom Action errors that I think are related to rights
> > (both run in system context). During a repair, I don't really need
> > these actions to run.
>
> > What I was thinking of doing for these Deferred Custom actions if
> > certain properties are available... If possible could I condition with
> > NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
> > which is the better method.
>
> > Or, if there is something better, please let me know.
>
> > Thanks!- Hide quoted text -
>
> - Show quoted text -

Can't quite remember, but I think they were 1723. I killed the
virtual image I was testing on so I can't recreate since I already
changed the install to condition NOT REINSTALL.

My only concern is that if I Patch, these actions will not run I don't
think, correct? The one action I'm not too concerned because it just
tweaks an Add/Remove Programs Support version display on our app
listing.

The other runs RegAsm on some files. I can't think straight right now
(head spinning from all this stuff) so I can't telll if I will need to
run this for patch or not.

I wonder if I can condition it something like this.....

(NOT REMOVE~="ALL" AND NOT REINSTALL) OR PATCH ??

Any further help is GREATLY APPRECIATED!!!!

You could use Earthlink.NET on their DNS and compile a windows update.


"Superfreak3" <mawa316@rcn.com> wrote in message
news:bce746dc-88ff-4d90-adee-2e2a7a2af312@t23g2000yqt.googlegroups.com...
> Hi there,
>
> I'm testing my install on a Windows 7 machine and we do require admin
> rights to install. With that, there is no problem.
>
> Now, when a standard user log in, some User registry keys and the like
> have to be 'repaired' or placed for that user. During this repair, I'm
> getting two Custom Action errors that I think are related to rights
> (both run in system context). During a repair, I don't really need
> these actions to run.
>
> What I was thinking of doing for these Deferred Custom actions if
> certain properties are available... If possible could I condition with
> NOT REINSTALL or do I have access to AdminUser or Privileged. If so,
> which is the better method.
>
> Or, if there is something better, please let me know.
>
> Thanks!