Conditioning Actions for AdminUser or Repair?
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!
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!
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
mekaywe
14 years ago
You can use the condition "Not Installed " OR change the CA setting to run in "User Context" and try
Posted by:
anonymous_9363
14 years ago
Changing the CA's context to user probably won't help since the OP states that the CAs are setting permissions, something which ordinary users probably (hopefully!) won't have sufficient privileges to do. Nor will that change affect whether or not the CAs get run during a repair.
"NOT Installed" is the condition to use. Note that the case for the word 'Installed' is important. "NOT INSTALLED" or "NOT installed" will be ignored.
"NOT Installed" is the condition to use. Note that the case for the word 'Installed' is important. "NOT INSTALLED" or "NOT installed" will be ignored.
Posted by:
cygan
14 years ago
ORIGINAL: mekaywe
You can use the condition "Not Installed " OR change the CA setting to run in "User Context" and try
hope you are not getting confused with running a CA in user context which basically means running your CA with the same rights as a standard user
a standard user has no rights to set permissions
running a CA in system context will be run with elevated privileges
Posted by:
anonymous_9363
14 years ago
Not explicitly, but implied:
I'm getting two Custom Action errors that I think are related to rights (both run in system context)
Posted by:
Superfreak3
14 years ago
Currently the condition I've tested and seems to work is...
NOT REMOVE~="ALL" AND NOT REINSTALL.
Can I replace that whole thing with NOT Installed or just the NOT REINSTALL portion.
Also, I see that this action is wrapped in a larger NOT PATCH block. Can I remove the action in question from that block and simply condition with NOT Installed? I guess the question is will and action conditioned with NOT Installed run during a patch?
NOT REMOVE~="ALL" AND NOT REINSTALL.
Can I replace that whole thing with NOT Installed or just the NOT REINSTALL portion.
Also, I see that this action is wrapped in a larger NOT PATCH block. Can I remove the action in question from that block and simply condition with NOT Installed? I guess the question is will and action conditioned with NOT Installed run during a patch?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.