Maybe it's just me, but having an IT staff member remote to a PC to manually initiate a software installation kind of defeats the purpose of a system such as this.
On Fri, Mar 6, 2015 at 6:28 PM Atkinson, Matt T < [email protected]> wrote: > Sure it’s possible, but we would either have to expose the SCCM console > to desktop support/help desk or rely on them adding AD user accounts to AD > groups, then keying the collections based off of the group memberships. > Kind of a pain due to wait times for AD discovery and collection evaluation. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Kent, Mark > *Sent:* Friday, March 06, 2015 2:35 PM > *To:* [email protected] > *Subject:* [mssms] RE: App catalog background transfers? > > > > What about letting the users themselves run it from the app catalog? You > can control what they see. And require approvals as well. > > > > Mark Kent (MCP) > > Sr. Desktop Systems Engineer > > Computing & Technology Services - SUNY Buffalo State > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Atkinson, Matt T > *Sent:* Friday, March 6, 2015 4:56 PM > *To:* [email protected] > *Subject:* [mssms] App catalog background transfers? > > > > Coming up against a problem while we are getting our service desk folks up > to speed with deploying software using SCCM 2012. Our original plan was to > have the tech connect remotely to the machine, login, launch the app > catalog with their credentials and start an install from the catalog. Then > log out, let the user log back in and continue working while the > application finishes downloading. > > > > This isn’t working in practice, as soon as the tech logs out, the BITS > transfer gets queued and won’t resume until the technician is logged in > again. Is there any way to work around this? It’s been frustrating running > against a wall trying to get a way to let our desktop support folks to > install apps for users. Deploying directly to the user accounts or > computers themselves would obviously work, but not desirable from our > leadership. > > > ------------------------------ > > > This message is intended for the sole use of the addressee, and may > contain information that is privileged, confidential and exempt from > disclosure under applicable law. If you are not the addressee you are > hereby notified that you may not use, copy, disclose, or distribute to > anyone the message or any information contained in the message. If you have > received this message in error, please immediately advise the sender by > reply email and delete this message. > > > > > > ------------------------------ > > This message is intended for the sole use of the addressee, and may > contain information that is privileged, confidential and exempt from > disclosure under applicable law. If you are not the addressee you are > hereby notified that you may not use, copy, disclose, or distribute to > anyone the message or any information contained in the message. If you have > received this message in error, please immediately advise the sender by > reply email and delete this message. >
