Can't delete application because of a (Non-existent) dependent Task sequence
I am running CM 2012 R2.  I have an application that I can not delete because it tells me that there are 5 task sequences dependent on it.  I am able to retire it though. 

I removed all revisions and even deleted the deployment type.

I have tried this script http://blogs.msdn.com/b/customer_reviews_of_stb_products/archive/2013/07/09/powershell-with-system-center-configuration-manager-2012-shortens-long-administrative-efforts-with-task-sequence-dependencies-by-dujon-walsham.aspx , but it does not find any dependent task sequences.

I have also utilized a console extension from David Obrien http://www.david-obrien.net/2014/05/configmgr-console-extension-find-referenced-task-sequences/ that does a check for dependencies, and it reported that there were none for that application. 

Attempting to remove via the Remove-CMApplication cmdlet displays the same dependency message.  Any one have any other ideas?
May 28th, 2015 6:09pm

I have verified that there are no more revisions of the application.
June 9th, 2015 9:56am

I was actually able to query for my application via the Get-CMTaskSequence cmdlet to see that my application was actually still referenced in a couple of task sequences.  Once those were modified I could delete the application
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2015 9:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics