I have not used SMS 2003 for about 6 years so i am really rusty. We have an application that when installed must be installed in the USER Context. This is on windows XP machines so for the msiexec.exe we wil use ALLUSERS=2

Our users are only users, they are not even Power Users of their machines so it is really locked down. Can SMS run something with Admin Rights but still run it on a per user context? I know the ALLUSERS=2 will run per-user only if the user has rights and in our case they don't. How do you setup SMS 2003 to handle this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I can only speak from an SCCM perspective. My last client installed everything per-user (don't ask...) and trying to get SCCM to do the same was a monumental PITR. If you have only one app with this restriction (what are its license terms, BTW?) I'd use Group Policy instead. This was what that cleint was using before, although we found setting ALLUSERS to null (in the MSI, use '{}' to do that) produced the best results.

Lastly, AppDeploy has a dedicated SCCM/SMS forum.
Answered 12/23/2010 by: VBScab
Red Belt

Please log in to comment
0
I have not used SMS 2003 for about 6 years so i am really rusty. We have an application that when installed must be installed in the USER Context. This is on windows XP machines so for the msiexec.exe we wil use ALLUSERS=2

Our users are only users, they are not even Power Users of their machines so it is really locked down. Can SMS run something with Admin Rights but still run it on a per user context? I know the ALLUSERS=2 will run per-user only if the user has rights and in our case they don't. How do you setup SMS 2003 to handle this?
Answered 06/04/2011 by: Orlandoreal
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity