Hello!

Whenever i delete a Deployment from a collection, it doesn't get deleted out of the clients Softwarecenter. The Application is still visible on the client and if I click the button to install it, I get an error telling me that the Softwarecenter can't update the needed Information.

i've already tried to reinstall the Client. This removes all old (deleted) deployments from the softwarecenter, but as soon as i deploy an aplication and then delete the deployment I get the same Error again.

Has anyone experienced something like this before?

Thanks in advance!

• Moved by Joyce Wang [MSFT]Microsoft employee Wednesday, July 25, 2012 5:34 PM (From:Configuration Manager 2012 - General)

Have you updated machine policies on the client or waited for the default cycle to occur?

I tried both. but nothing changed in the Softwarecenter.

Have you deployed the application to user or machine collection ? Also, is the deployment marked as available or required ?

I tried both. but nothing changed in the Softwarecenter.

Did you refresh(F5) the Software Center window after forcing the machine/user policy update?

Yes i did... nothing changes when i delete a deployment. It is still shown in the Softwarecenter.

The applications are deployed to a device collection and they are marked as available

I know it's no help, but I'm having the exact same problem.  Applications deployed to a device group.  Deployment deleted.  Software center still shows it available.  If I try running it, I get "Software Center cannot retrieve the information that you requested".  Same thing happens when I modify the deployment type.  Ran policy cycle, even left the machines overnight.  It just doesn't go away.

I've discovered that if I mark the application as retired, the Install button on the client does become disabled.  So my client is picking up policies.

Has anyone been able to solve this issue? I am experiencing the same issue. I created three applications for installing commonly used software and they worked fine. I then decided to make installation more simple by creating a fourth application that installed all three of the software programs with one deployment/install. This was done by cloning one of the original applications and setting the other two as dependents.  I began experiencing issues because of this fourth application and thus decided to not delete the applications. I first deleted the deployment that I had for the application and then deleted the application completely from ConfigMgr. I have executed the action update on all of the available policies on the systems that had received the deployments but the delete application still shows as "installed" on them even though the application doesn't even exists. I have even restarted the system multiple times and updated the ConfigMgr policies again multiple times. The deleted application simply will not go away.

If you reset policies by using policy spy and reinitiate policy retrival action would they still appear in software center? There might be some indication in the logs as why it does not revoke those policies. If you move the computer or user object out of the collection that you have the deployments for, would this still happen

Hi All,

I previously had an application deployed to a group of users in a collection which the vendor wanted removed.
I did the normal steps of:

• Delete the deployments
• Delete the application

A turn of events occurred where this application had to be redeployed to the same machines under a different name, this is where my problem has occurred.

In the software center - the newly deployed applications are there - as they should be. But also the old deployments are still showing up even though that application and deployment (under that application name) does not exist. Does anyone know how i can get rid of these?

I'm not sure if it is important but the files being used for the new application are exactly the same as the old application.

I've seen these links:

• http://social.technet.microsoft.com/Forums/en-US/7a50101a-328e-4905-92bc-8070b04a613c/old-application-deployment-to-user-still-visible-in-software-center (not an option to delete client)
• http://social.technet.microsoft.com/Forums/en-US/5e233760-5805-457b-8dbf-35e5d2ec7683/deleted-deployments-are-still-visible-in-softwarecenter (no solution)

So i know other people have ahd this problem but cannot find a sensible solution

Looking forward to your replies!

• Edited by mlg_24_05 Friday, July 26, 2013 10:48 AM
• Merged by Torsten [MVP]MVP, Moderator Friday, July 26, 2013 11:43 AM merged threads

A note here that *may* be the source of confusion here: you do know that deleting the deployment will *not* uninstall the application, correct?

I am aware of this, thats why im so confused about thwat has happened. I have ensured that the machines receiving the new application have uninstalled the original application before i deployed. Still get the old ones showing up...weird.

Jason-

I am having the same issue. I uninstall the Application. Then I delete the deployment. Then I refresh all SCCM policies on client. The application still shows as Available Software and status Past Due- will be installed. When I hit Install I get the "Software Center cannot retrieve the information you requested" "The Item you requested from Software Center is no longer available. You can press F5 to refresh view" When I press F5 the App is still there, as available. It should be gone since I have deleted the Deployment, however, after 5 days it is still there....

I am wondering if this is a bug with uninstalling an App before deleting the deployment? Perhaps the deployment should be removed first and then uninstall?

• Edited by HW19 Monday, June 09, 2014 8:44 PM

Similar scenario for me:

I have a test app (Launches CMD, Creates a File (for detection), then exits).

My test App has an uninstaller (Launches CMD, Deletes the file (for detection), then exits)

I targeted to a user collection as available and show in application catalog.

I install the software, then uninstall it.  It moves over to the Available software tab as available software.

I created this because we had people use the app catalog to install Project 2007 before we had Project 2010.  THey now install Project 2010 and are consistently notified that there's new software available (the Project 2007) deployment that they pulled from App Catalog.

I'm able to duplicate this behavior at my leisure.  What's the issue here?  I've seen a few posts that went unanswered over a year ago.  This is still "new" as HW19 updated his last comment only 20 hours ago.

Someone?  Anyone have an answer?  It seems doing a policy reset using Roger Zander's 'client center' fixes the issue.  Shouldn't have to do that.

Has anyone found a solution to this? It's 2015, R2 RU4 is out and this is still unanswered...

Already found an answer/solution ?

 

Indeed, always the same problem exists ... when MS will provide a solution for this ?

I think I found the solution

You have to update your Distribution Points.  I ran into the same exact problem but then I remembered the Applications were still listed in my Distribution Points even though I deleted the actual Deployment.  Once I cleared them from the Distribution Points, my Clients removed the entries from "Available Software."

I believe this is tied to the "Content Validation" schedule which may automatically clean it up for you but manually removing the apps from Distribution Points definitely removed the listing from the Software Center.  Hope this helps someone.

That's very odd AGoodGreek.  I cant imagine why having the content in the Content Library on the DP would cause the client to retain the policy.  There could be many scenarios where the content shouldn't be removed, just certain machines or users no longer need the deployment.  Removing it from the DP certainly breaks that ability..