Re: [WiX-users] Modifying registry key permissions for new user

[Matthew Moses]

Sorry, it looks like I jumped the gun on this one. I was receiving an
error message about the user not being valid. However, I upgraded to
the latest release of WiX and began getting an error regarding the
SecureObject column being null. Turns out I had neglected to set the
RegistryKey/@Action attribute, so it defaulted to "none". What I
really wanted was to set the attribute to "create". After that,
everything turned out as planned.

Thanks for all your help. The information you provided regarding
immediate vs. deferred CA's was also a great help.

Matthew

On 11/22/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Matthew Moses wrote:
> > My initial thought was to use the PermissionEx element nested under an
> > appropriate RegistryKey element. However, this doesn't seem to work as
> > the user has not been created by the time the installer attempts to
> > set the permissions on the registry key.
> >
>
> ConfigureUsers runs early in the sequence and SchedSecureObjects (which
> handles PermissionEx) runs late, so it should work. How are you
> determining that the users weren't created? If the CA failed to create
> the user, it would log the reason and fail the install, for example.
>
> > Another custom action run by our installer also relies on the user
> > being created, and by sequencing it after InstallFinalize, it worked.
> > It seems that I could write another custom action that sets the
> > required permissions, sequence it after InstallFinalize, and have
> > everything work. Am I on the right track? Did I miss something
> > important? Is there a better way to do this?
> >
>
> Immediate CAs after InstallFinalize can't be rolled back and won't get
> elevated permissions on Windows Vista. They should be deferred CAs (and
> marked no-impersonate if they need elevated permissions).
>
> --
> sig://boB
> http://bobs.org
>
>
>

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Modifying registry key permissions for new user

[Matthew Moses]

We have a WiX (v3.0.2315.0) project in VS2005 to build an installer
for one of our products. The installer makes use of the User element
to create a new user on the target machine for various purposes. I
have recently been instructed to make sure the user is able to
manipulate a registry key as part of the installation process. By
default, the user is only able to read this particular key, nothing
else.

My initial thought was to use the PermissionEx element nested under an
appropriate RegistryKey element. However, this doesn't seem to work as
the user has not been created by the time the installer attempts to
set the permissions on the registry key.

Another custom action run by our installer also relies on the user
being created, and by sequencing it after InstallFinalize, it worked.
It seems that I could write another custom action that sets the
required permissions, sequence it after InstallFinalize, and have
everything work. Am I on the right track? Did I miss something
important? Is there a better way to do this?

Matthew

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users