I've created user collections that lookup AD group membership. I now want to deploy software to the machines those users log into and install the software for the machine. Understandably this isn't a 'clean' way of managing the software deployments because users could log into multiple machines - but the software we're deploying is free/unlicensed so sprawl is irrelevant.
We're SCCM 1603 and I can see the deployment running, but it fails. Presumably because of the context the installer is running. If I install it against a device collection, it works. Presumably because the install is run in the SYSTEM context, and not user. How can I get around this? Is it possible to configure service accounts with admin rights to runas for a user deployment? Or is there a cleaner way?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I've created user collections that lookup AD group membership. I now want to deploy software to the machines those users log into and install the software for the machine. Understandably this isn't a 'clean' way of managing the software deployments because users could log into multiple machines - but the software we're deploying is free/unlicensed so sprawl is irrelevant.
We're SCCM 1603 and I can see the deployment running, but it fails. Presumably because of the context the installer is running. If I install it against a device collection, it works. Presumably because the install is run in the SYSTEM context, and not user. How can I get around this? Is it possible to configure service accounts with admin rights to runas for a user deployment? Or is there a cleaner way?
Cheers!
Share this post
Link to post
Share on other sites