question

DS-9030 avatar image
1 Vote"
DS-9030 asked ·

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

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.

mem-cm-generalmem-cm-application
capture.jpg (19.4 KiB)
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FionaYan-MSFT - were you able to resolve this ?

0 Votes 0 ·
FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered ·

@DS-9030

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.


· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DS-9030 avatar image
0 Votes"
DS-9030 answered ·

@FionaYan-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!




· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DS-9030 avatar image
0 Votes"
DS-9030 answered ·

@FionaYan-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.

· 3 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DS-9030

After we refreshing the application Deployment Evaluation Cycle and the Machine Policy Retrieval & Evaluation Cycle on our client ,maybe we could check the CcmMessaging.log,locationservice.log andpolicyagent.log to check whether these failed clients are healthy or not.

Have a nice day!

0 Votes 0 ·

The logs did d not have any entry of tasks failing..
I also had one another app deployed via Available deployment to my user name and it installed fine via SC.

There just apears to be something off with removing and readding membership. This somehow seems to break the Repar/Uninstall functionality of the application under SC

0 Votes 0 ·

@DS-9030

I review the case again and I got the following ideas:
1.The software center is also part of our agent, maybe we could try to reinstall our client agent to see if it works?
2.There are some anti-virus software may affect this issue, if there were some exist,please disable it to have a try.
3.If these doesn't work, could we use process monitor tool to monitor it?
4.Here is a powershell script that someone use fix this issue,maybe we could also try it:
"Powershell.exe Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false"
For more details please refer to this similar case:
https://social.technet.microsoft.com/Forums/en-US/75b640eb-b3ff-4754-9917-045cd52e9a8c/software-center-can-not-be-loaded-there-is-a-problem-loading-the-required-components-for-software?forum=ConfigMgrCBOSD

Look forward to your further good news!

0 Votes 0 ·
DS-9030 avatar image
0 Votes"
DS-9030 answered ·

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!

· 1 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DS-9030

The issue we faced currently is that we could not open our software center(please correct me if I'm incorrectly) so maybe the component of our SCCM client agent went something wrong. So in this situation:
If there is only a few clients faced this problem, maybe we could uninstall the failed one manually and then reinstall the client and then see if it can open our software center normally.
Use CCMSetup.exe /uninstall this command and open ccmsetup.log file to monitor the client uninstallation.
For more details, please refer to this article:
https://jocha.se/blog/tech/sccm-client-install-uninstall

Hope it can help you.








0 Votes 0 ·
DS-9030 avatar image
1 Vote"
DS-9030 answered ·

@FionaYan-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 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DS-9030

Thanks for your detailed explanation,that means your issue was not get expected after you click repaired button,is there any related errors in our appenfoce.log?Have we seen this log before?

0 Votes 0 ·
DS-9030 avatar image
0 Votes"
DS-9030 answered ·

No, there is nothing in appenforce.log. The Scclient-[username].log would shows SC not able to find the application entry under CCM_Application WMI class and failing with the error message above.

· 1 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DS-9030

For our repair failed issue,could we use PS tool open our system account to run repair command line manually instead of clicking our repair button in SC.
1.The PS tool use step shown below:
2.Download psexec.exe from Sysinternals.
3.Place it in your C:\ drive.
4.Logon as a standard or admin user and use the following command: cd . This places you in the root directory of your drive, where psexec is located.
5.Use the following command: psexec -i -s cmd.exe where -i is for interactive and -s is for system account.
6.When the command completes, a cmd shell will be launched. Type "whoami"->it will say "system".

Really hope it works.

0 Votes 0 ·
DS-9030 avatar image
0 Votes"
DS-9030 answered ·

@FionaYan-MSFT : I think you are missing the point here. I would like to know why Repair via SC would not work in the scenario I described above.

Ofcourse, Repairing the app manually via control panel or command prompt using elevated system is always present.

But I would like to see this work from SC as this allows normal users to Repair the application in system context without having to actually use any elevated account.

The step by step scenario I described above would work for (Device Targeted Available Deployment) but not for (User targeted Available Deployment). Is this an expected behavior?

· 2 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DS-9030

I appreciate your understanding that this case's situation is a bit complicated and i really understand your mood.I may need to do some experimental in my lab to research the difference between deploying usercollection and device collection, if there is any progress, I will reply you immediately.

Thanks for your understanding.

0 Votes 0 ·

@FionaYan-MSFT : Thank you. Appreciate it!

0 Votes 0 ·
FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered ·

@DS-9030

Sorry to reply late,dear DS-9030.

I have do the same operation as you described above in my environment and when i use this deleted user logged in the SC then i got the same error image as you provided.

I will try the best to deliver the information to the product team to see if they have some additional comments, but not guaranteed. once there is a reply, i will get back to you at the first time. thank you for your kind understanding.

While helping the customer solve problems,Microsoft also attaches great importance to the voice of users. It's recommended that we could use the following user voice link to submit our suggestion to let us see the bottom voice from our heart.
https://configurationmanager.uservoice.com/forums/300492-ideas

Have a good day and thank you!


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.


· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.