user context custom actions in deferred mode
Hi,
The project in which we are working, has std. ALLUSERS=2, all the users will be power users. Right now, I have business object application, in which so many deferred mode custom actions, are in user context...will it be a good practice to move all user context custom actions in to system context?
The project in which we are working, has std. ALLUSERS=2, all the users will be power users. Right now, I have business object application, in which so many deferred mode custom actions, are in user context...will it be a good practice to move all user context custom actions in to system context?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
That depends on what the CAs do. If they're customising the application for the user environment, there won't be much point in having the System account run them. On the other hand, if they're making changes to the system (and why else would they do in deferred?), then yes, they should run in System context.
Also, given the above, I'd wager that the MSI has a LaunchCondition which checks for admin privileges.
Also, given the above, I'd wager that the MSI has a LaunchCondition which checks for admin privileges.
Posted by:
Jsaylor
14 years ago
Keep in mind that, just because ALLUSERS is set to 2, does not mean that the program will install to the user profile. If you're using a deployment system that uses the system account for installations, then the program will install to all users instead.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.