User-Targeted Available Deployment fails to Repair/Uninstall from Software Center

DS 51 Reputation points
2020-10-11T11:31:16.637+00:00

Hi,

We have an application deployment onto some of the users via user collection. It was an Available Deployment with Repair from Software Center enabled.

Initially, users were able to install/repair/uninstall the application fine from Software Center, as expected.

2-3 weeks down the line, one of the users reported he was getting below error when trying to Repair the installed application from SC.

31464-capture.jpg

On checking the SCClient.log on the user's machine, Software Center was unable to find any reference of the application under 'CCM_Application' class within namespace 'root\ccm\clientSDK'.

Turns out the user collection membership on SCCMCB had been emptied. Re-added the users back to the collection and was hoping that on triggering user 'User Policy Retrieval and Evaluation Cycle' followed by 'Application Deployment Evaluation Cycle' the entry of the application should re-populate back under CCM_Application class on the client end-point, but no joy.

Have tried re-booting the machine as well but app entry under the CCM_Application class would not come back on end points.

Still get the same SC dreaded error on trying to Repair / Uninstall the app from SC.

Kindly suggest.

Microsoft Configuration Manager Application
Microsoft Configuration Manager Application
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Application: A computer program designed to carry out a specific task other than one relating to the operation of the computer itself, typically to be used by end users.
459 questions
Microsoft Configuration Manager
{count} vote

8 answers

Sort by: Most helpful
  1. DS 51 Reputation points
    2020-10-16T10:46:41.187+00:00

    @Fiona Yan-MSFT :
    No, the issue is not at all with Software Center not opening!
    Let me put the steps, if feasible you can try it on your lab. Should face the same issue

    1. Targeted an application to a user with following settings:
      Deployment Purpose : Available
      Installation Behavior : Install For System
      Allow User to Repair the Application : Yes
    2. User logs in. Application shows under SC (expected). User installs the application. Repair from SC also works fine, as expected
    3. The CCM_Application WMI Class also lists the application as follows which is as expected:
      InstallState : Installed
      IsMachineTarget : False
    4. User then gets removed from User Collection and Repair of the application from SC on the machine fails with error I provided above. At this point, if the CCM_Application class is queries, application entry is also missing (guess that's expected)
    5. User is is added back to the user collection of the application. Collection membership confirms it. User triggers the application deployment / Machine & User policy from control panel but the application entry does not get populated back under CCM_Application class on the machine. When user clicks on the Repair / uninstall button under SC, application keeps popping up the error I provided above So far have tried all the troubleshooting step listed above, but it has not listed the application entry within CCM_Application and the error message continues to pop-up on trying to Repair or Uninstall the app from SC.

    NOTE: Tried the same scenario with a device collection, with Available deployment and Repair enabled. ASA the device is added back to the collection and machine policies are refreshed, app entry populates back under CCM_Application class and users can Repair/Uninstall the app fine from SC.

    So the issue seems to be specific to User Collection with Available Deployment.

    Hope its clear.

    1 person found this answer helpful.

  2. Fiona Yan-MSFT 2,311 Reputation points
    2020-10-12T06:29:05.97+00:00

    @DS

    Thank you for posting in Microsoft Q&A forum.

    Could we use the following WMIC command to reset the state of our software center to have a try?And then we refresh our policy again to see if it is ok.
    WMIC /Namespace:\root\ccm path SMS_Client CALL ResetPolicy 1 /NOINTERACTIVE
    For more details,please refer to this article:
    http://leinss.com/blog/?p=2250
    Note: this is non-official Microsoft article just for your reference.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. DS 51 Reputation points
    2020-10-12T18:09:55.727+00:00

    @Fiona Yan-MSFT :

    So running the command as Admin on the machine and triggering the policies, removed references of the uninstalled application from client WMI that is no longer target to the machine as well as per the
    http://leinss.com/blog/?p=2250

    But SC on launch does not seem to notice that and still shows the application entry with Install & Schedule button with status - Past due-will be installed. Will give it some time and check

    The main issue of user-Targeted installed app not repairing from SC is yet to be tested. Will get back to you on that.

    Thank You for your reply!

    0 comments No comments

  4. DS 51 Reputation points
    2020-10-14T09:37:16.317+00:00

    @Fiona Yan-MSFT :

    • Did not work. Repairing application via SC still fails with same error.
    • The WMI entry on the client is also not listing the application entry.

  5. DS 51 Reputation points
    2020-10-15T10:00:32.683+00:00

    I have already checked the SetClientProvisioningMode value in the registry and its already sey to false

    Already tried repairing client followed by restart.. dint help.

    If any new app deployed via Available deployment os coming down then dont think its antivirus blocking it as well

    Thanks for the suggestion!