You could simply make a collection that includes all users and then excludes all users in your install collection.
If this is just a ThinApp that installs to the user profile, I don't think you have to worry about users roaming. On Thu, Oct 15, 2015 at 8:21 AM, <[email protected]> wrote: > > > Is this CM12 and are these packages or applications? Applications , > software deployment of Vmware ThinApp that install the applications into > de User\appdata\local profile > > > > If they don’t you could have a second collection of all users that are NOT > members of the “Office 2013 Users” group and then target that collection > with the uninstall of Office 2013. > > Q: How do you do that, my view is that, that the collection will showup > with all users without the users in the “Office 2013 Users” group, > correct? > > > > Thks for your support and Time > > > > > > > > *Maarten van Willigen* > Technical Specialist > Informatie & Communicatie Technologie > > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Marable, Mike > *Sent:* Thursday, October 15, 2015 14:33 > *To:* [email protected] > *Subject:* [mssms] RE: Software Deployment to an AD Group > > > > Is this CM12 and are these packages or applications? > > > > The installs are all keyed off of a user’s membership is a group, > correct? So, if for example the user is a member of the “Office 2013 > Users” group Office 2013 would automatically install? > > > > Do your users roam between machines? > > > > If they don’t you could have a second collection of all users that are NOT > members of the “Office 2013 Users” group and then target that collection > with the uninstall of Office 2013. > > > > Now if your users do move between computers that would be dangerous. > Let’s say that you and I share a computer. You’re a member of the > “Photoshop Users” and I am not. You log in and SCCM installs Photoshop > because you are a member. Later I log in and because I am not a member of > the “Photoshop Users” group SCCM uninstalls it. > > > > If you’re using the application model in SCCM 2012 then you can probably > leverage the primary user feature to minimize this problem. > > > > In my opinion, it would be easier to move to focusing on the computer and > not the user. So, Bob is supposed to have Photoshop on his computer, his > computer is added to the "Photoshop Computers” group, it then falls into a > collection and SCCM installs Photoshop. Bob no longer needs Photoshop? > You remove his computer from the group and it falls then into a collection > that automatically uninstalls Photoshop. > > > > Mike > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *[email protected] > *Sent:* Thursday, October 15, 2015 8:14 AM > *To:* [email protected] > *Subject:* [mssms] Software Deployment to an AD Group > > > > > > > > I have an requests to remove software from PCs/Users who no longer use it. > > The procedure has basically been to go to the properties of an AD Group > and manually remove the user from the AD group, > > update de collection, then manually remove the software from their PC. > > > > So far the requests have been for small numbers of users so it hasn't been > too horrible, but the whole procedure seems wrong and there just has to be > a better way. > > The actual uninstall from the PC is either a manual procedure, or I have > to create another "uninstall" collection to add the user to or is there an > history in sccm 2012 > > that hold the difference of an AD Group. > > > > > > So, I'm basically asking, "Is there a better way?". > > > > > > > > *Maarten van Willigen* > Technical Specialist > Informatie & Communicatie Technologie > > > > > > > > ================================================================================================ > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is > uitsluitend bestemd voor de geadresseerde. > Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet > te gebruiken en de afzender direct te informeren door het bericht te > retourneren. > > ================================================================================================ > The information contained in this message may be confidential and is > intended to be exclusively for the addressee. > Should you receive this message unintentionally, please do not use the > contents herein and notify the sender immediately by return e-mail. > > ================================================================================================ > > > > ********************************************************** > Electronic Mail is not secure, may not be read every day, and should not > be used for urgent or sensitive issues > > > > ================================================================================================ > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is > uitsluitend bestemd voor de geadresseerde. > Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet > te gebruiken en de afzender direct te informeren door het bericht te > retourneren. > > ================================================================================================ > The information contained in this message may be confidential and is > intended to be exclusively for the addressee. > Should you receive this message unintentionally, please do not use the > contents herein and notify the sender immediately by return e-mail. > > ================================================================================================ > >
