Hi experts.
I have made this a discussion rather than a question as I am really after other experts opinions regarding the removal of retired applications from ConfigMgr 2012.
The scenario we have is a list of some 150+ retired applications and a lack of space on the source location to keep them with new apps being added weekly. Obviously, some of these apps would be superseded by others and may be still installed on some devices, especially if they had only been retired a couple of months ago with no remediation work to remove the apps from the devices.
I'm really after some helpful tips that could provide assistance for me and anyone else who reads this thread and is tackling the same or similar scenarios, so that we don't fall into some obvious potholes during the process.
As i see it, the following is what I would consider the process:
- Run a scan on all devices to locate any installed "retired" applications.
- Remove any deployments of the retired applications (should be already done if the apps are retired, but best to check).
- Run the uninstall (or install of the superseding software if applicable) to remove the retired application.
- Remove retired application's content from all distribution points.
- Delete the source files from the source location.
- Delete all the deployment types.
- Delete the application
One step I haven't included as I believe it should have been included as part of the initial retiring process is:
- Checking all Task Sequences for references to this retired application
Is anyone able to provide some additional helpful steps that they feel have been overlooked or missed off of the above list? Any "things to avoid" or "be careful when doing this" comments?
Thanks
Dean