sccm - run with administrators rights and CU profile
Hi
Despite my best efforts to find a definitive answer to this I am getting conflicting information.
When I deploy software using SCCM and I want the software to place keys in the HKCU and files in the users profile, I thought that I could use the option "Run with Administrators rights" and as long as the user was logged in when the software was installed, the CU keys and files would be delivered to their profile. The users in my environment are standard users and do not hold the privileges required to install software. I understand that if I want to apply the CU settings to all users then I will have to set up a self repair or active setup.
I have read stuff that says in order for CU keys and files to be delivered the software must be deployed with user rights.
Can someone clarify this for me.
Cheers
G
Despite my best efforts to find a definitive answer to this I am getting conflicting information.
When I deploy software using SCCM and I want the software to place keys in the HKCU and files in the users profile, I thought that I could use the option "Run with Administrators rights" and as long as the user was logged in when the software was installed, the CU keys and files would be delivered to their profile. The users in my environment are standard users and do not hold the privileges required to install software. I understand that if I want to apply the CU settings to all users then I will have to set up a self repair or active setup.
I have read stuff that says in order for CU keys and files to be delivered the software must be deployed with user rights.
Can someone clarify this for me.
Cheers
G
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Posted by:
pjgeutjens
13 years ago
A distinction should be made between initial deployment under administrative rights (which is usually done under LOCALSYSTEM credentials), and subsequent repairs or self-heals which are executed in user context.
Basically during the initial deployment no user data for end users gets written, only for the installing user, which is usually not the same as the logged-on user in a deployment scenario. Like Ian said, it's only when a repair or selfheal is triggered in the session of a logged on user, either through ActiveSetup or an advertised entrypoint like a shortcut, that the user-level stuff for that user gets put into place. So it's basically a 2-step process.
PJ
Basically during the initial deployment no user data for end users gets written, only for the installing user, which is usually not the same as the logged-on user in a deployment scenario. Like Ian said, it's only when a repair or selfheal is triggered in the session of a logged on user, either through ActiveSetup or an advertised entrypoint like a shortcut, that the user-level stuff for that user gets put into place. So it's basically a 2-step process.
PJ
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.