hi,
We are facing 2 issues where we are not sure how to handle.
first: Userpart
We have several applications which have a "userpart" (this part should run with users credentials). So we try to configure that we have 1 application with 2 deployments. One is the machinepart, and the other one the userpart. the userpart deployment has the machinepart deployment configured as dependency. The detection rule is in both cases a registry key - one pointing to HKLM and one to HKCU.
We get the installation running successfull but afterwards the button to uninstall is grayed out (available deployment - not required). As i have seen this is a bug? Someone knows when this will be fixed?
But also if this gets fixed, there are 2 more open questions:
Within the uninstallation, are both deployments executed to be uninstalled? (I guess not :( - how to handle it then?).
If another users logs into the client, is the userpart then also executed for this user? (i guess yes, because the detection rule should know that something is missing from this application)
Second: Trigger a required update of available application
For example: you have AdobeReader installed on the clients and offered as "available Application". Now you get a new servicepack. So our behaviour within SCCM2007 was, that we update the package source with this new SP and add a commandline to
execute it within our execuion-script. Then we created a mandatory advertisement and so we get updated all the clients. We tried to do it the same way in SCCM2012 and it works, but the pain is, that nobody of the affected clients can uninstall/install the
application anymore because the button is grayed out due to the required deployment (i guess).
What is your suggestion to handle this? Create a new application for every minor change?
thanks for answers/proposals.
BR