In SCCM, WMI class CCM_Application in ClientSDK does not list User-Available (Target = User Collection, Purpose = Available) Applications unless you Install them manually from the Software Center once, and hence you cannot trigger Installation ("Install" method of the "CCM_Application" class) of an application that has been made available to a user but has not yet been installed through the Software Center. Is there any way we could trigger the installation of such Application from the client machine using WMI or other code without actually having to go to the Software Center for the first time? (which otherwise, defies the purpose of ClientSDK IMO).
I do realize that there is a procedure that is followed behind the scenes whenever the deployment is made available to the user, the Policy gets downloaded (or enforced) to the client machine only once the installation is triggered through the Software Center and not before that. But all these steps of discovering and installing the User-Available Application, is it possible to do that from the client machine just like the Software Center, WITHOUT ever having to use the Software Center? There has to be a way.
Can anyone refer an SCCM expert to this Question? Anyone from Microsoft who actually have solution to this?
I have already read many long blogs on the internet related to this query but none seem to have figured it out.
Related Questions:
- https://video2.skills-academy.com/en-us/answers/questions/169898/ccm-application-client-wmi-class-available-softwar.html
- https://stackoverflow.com/questions/53276451/ccm-application-user-available-software-missing
(unsolved)
- https://stackoverflow.com/questions/12056088/automated-software-deployment-through-sccm-2012-using-wmi
This question has been answered but the objective there is different. It simply creates and starts the deployment of a software from the Configuration Manager. What I am trying to achieve is to Install the already deployed software (which is Available and hence not automatically installed), right from the client machine and not the server. Just like the Software Center does.