Archive | SCCM RSS for this section

How to automatically remove physical applications from PC’s when using Primary Devices.

When you deploy applications to users that are members of a specific Active Directory Application Group but install them machine based, how do you automatically remove the application when a user is no longer a member of the Application Group? Well, before SCCM 2012 this was not possible. There was no way of knowing from which computer to remove the application if a user was no longer a member of  the corresponding Application Group. Another problem was that a user could install de application on any PC he logged on to. Possible causing the company to not adhere to the license agreement.

With SCCM 2012 Microsoft introduced the ability to define Primary Devices for users and only allow installation of an application on the user’s primary device. This gives you better a grip on where applications are installed (and the required licenses).

This for me raised the question “Can I automatically remove an application from the primary PC for a user that is not (or no longer) the member of the Application Group for that application?”. Read More…


Managing App-V 5 Connection Groups using SCCM 2012 SP1 (Updated 5-sept-2013)

In this article I will try to explain how SCCM 2012 can be used to manage App-V 5 Connection Groups, and what the differences are between managing them with SCCM and managing them from a App-V 5 Full Infrastructure management server.
App-V 5 Connection Groups are managed from SCCM through what are called Virtual Environments. Virtual Environments define how the Connection Groups are created on the clients. Read More…