Account used for software deployment (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

jmiller120 -> Account used for software deployment (6/9/2008 12:56:58 PM)

I would like to allow certain groups to only deploy out to certain collections - i would also like the software to be run as that particular user.  Is this possible?  The only way i've seen this is to allow certain groups access to certain collections, but the software will always be run as a domain administrator (which i don't want, since i'm wanting to allow the helpdesk to be able to deploy packages)



wbracken -> RE: Account used for software deployment (6/9/2008 2:09:59 PM)

Can you elaborate on what you mena by you want osftware to be run as a particular user?  Are you saying you want the installation to happen on the client PC using the logged on users credentials?  or you want to delegate rights within the SMS Console for your helpdesk to be able to distribute software?



jmiller120 -> RE: Account used for software deployment (6/9/2008 2:15:27 PM)

i would like to have the software run as a specified account.  The users in my domain do not have administrative rights, so the account specified for client installs is the domain admin right now.  the only place i can find this is in the "client push installation" settings.  Ideally, the helpdesk has an account that is a local admin on all the user's pcs - that is the account i would like for the software to run as.



rbennett806 -> RE: Account used for software deployment (6/10/2008 1:41:56 PM)

Normally when you push out software you do not specify any account information, and then it runs within the SYSTEM context on a client machine (which has the ability to do just about anything). So what you probably need to do is to create some collections based on domain groups. Then have your helpdesk personel add an AD computer account object to the domain group. Once the updated domain group membership information is pulled into SCCM then the next time the client machine talks to SCCM it should start feeding out and installing the application.

The downside to this is that SCCM isn't truly AD-aware so it takes a bit for the domain group memberships (and thus your collections) to be updated.

I hope that makes sense...



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.15625