PENDING How to get user-based application deployments to register already compliant devices?

[LemonTetra]

When deploying an application to a user collection as an available installation, how do i get the deployment to register devices that are already compliant? From what i've read, this can only happen if the user then clicks the install button, which then forces the compliance check, and would then register as already compliant in the deployment monitoring.

Basically, we have been reimplementing a new SCCM environment and i'm currently deploying a bunch of applications to new collections. But most of this software will already be installed on user's devices due to them installing it previously via our old SCCM environment. Ideally, i want my deployments to reflect all of the users who currently have it installed and on which machines, as well as new people who install the application from software centre.

Currently the only way that shows this information is if i deploy to a device collection, but that isn't the way we want to deploy many of our apps. I know i can create collections with queries which pulls in devices based on specific installed software, but i'd rather have this information in the deployment instead of creating new collections all over the place. Is there any trickery that can be utilised to force this?

 

[Garth]

When deploying an application to a user collection as an available installation, how do i get the deployment to register devices that are already compliant? From what i've read, this can only happen if the user then clicks the install button, which then forces the compliance check, and would then register as already compliant in the deployment monitoring.

Basically, we have been reimplementing a new SCCM environment and i'm currently deploying a bunch of applications to new collections. But most of this software will already be installed on user's devices due to them installing it previously via our old SCCM environment. Ideally, i want my deployments to reflect all of the users who currently have it installed and on which machines, as well as new people who install the application from software centre.

Currently the only way that shows this information is if i deploy to a device collection, but that isn't the way we want to deploy many of our apps. I know i can create collections with queries which pulls in devices based on specific installed software, but i'd rather have this information in the deployment instead of creating new collections all over the place. Is there any trickery that can be utilised to force this?

You don't. The app detection is not triggered until the app is install. what does it matter if the deployment show it is installed or not? Why are you not using reporting for this?

 

[LemonTetra]

You don't. The app detection is not triggered until the app is install. what does it matter if the deployment show it is installed or not? Why are you not using reporting for this?

Because reporting hasn't been configured yet, that's why. Long story. But, also because i find it's quicker at a glance to see the compliance of a deployment and the reassurance that it is working properly.
This is a new environment and pretty much everything has been setup from scratch and we are not live yet. So getting feedback from the test deployments that things have been picked up ok after deploying everything for the first time is reassuring. Especially considering i have a control room to deploy to at some point where any issues with deployments might affect devices and lead to life or death situations.
I suppose i'd never noticed that detection for user deployments doesn't happen until they click the button, and that existing installations don't get picked up. This is because all of our software was previously deployed in our old environment, and much of it before my time, so users didn't previously have the software installed. If they wanted it they had to go and install it, so the compliance was then flagged up in the deployment. Further upgrades to those same applications were all mostly done with supersedence, so if they already had it installed it got automatically upgraded and the compliance was visible in the deployment.
Because this is a new environment, we are effectively trying/hoping to pick up those deployments again, which has worked fine for the device based deployments, but the user ones have all been empty even though i know the software is already existing on their device. And now i know why.