Thanks for the response Trevor. I understand the difference between the two, but regardless of the type of deployment, you are still telling SCCM to install software on a system, and there are circumstances where you may want that action to stop at a certain date and time. Deleting a deployment will have the same effect, but it will also remove the ability for me to view the reports for it, and also it requires a manual action, which is the whole reason why you would schedule the expiration instead of doing it manually. Retiring the application would affect any other current deployments of that application, which may not be what I want.
I guess I just find it hard to fathom why they would specifically NOT provide for this function, especially since it was maintained for package deployments. Cheers John From: [email protected] To: [email protected] Subject: RE: [mssms] Expire an Application Deployment Date: Mon, 10 Mar 2014 13:17:46 -0500 Applications and Packages are two different concepts. When you Deploy an Application to a Collection, you are instructing that Application to install on that system. If you want to stop deploying it, simply delete the Deployment. You can also Retire the Application, preventing it from being deployed any longer. Check out this fabulous article from the ConfigMgr documentation team: http://technet.microsoft.com/en-us/library/gg682031.aspx Cheers,Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of John M Sent: Monday, March 10, 2014 1:11 PM To: [email protected] Subject: [mssms] Expire an Application Deployment We rarely expire our software deployments, but the requirement to do this has arisen, and I am just now discovering that there is no expire option for Application deployments. First, can someone confirm this is true and that I just haven't missed it somewhere? And second, can anyone explain to me why they would remove this very useful function? Thanks! John
