Provide the ability to set an "expiration date" on a DEPLOYMENT
Even thought Applications are state based there are still use cases when a deployment could be expired so that no future deployments of that application will occur. Either an expiration or the use of automatically disabling the deployment, since Software Updates could be disabled so should Software Application Deployments. The reason to keep the deployment would be for reporting so a way to disable or expire would be ideal if state based is not needed.
The sms_applicationassignment WMI class exposes an ExpirationTime property which actually removes deployments from App Catalog but it does not work with software center.
If we can have it similar to how you can deploy a package. I would like to try to install every night but not during the day, outside the current maintenance windows.
+1 - I've just talked to a customer that would like to see it.
Even better if we could apply a recurring availability window, i.e. a maintenance window per application.
Peter Schwankl commented
100% want this.
This is a problem for both required and available deployments.
In the environment I work in, we release software weekly, ideally at 10AM on Friday mornings. When we release software, we delete previous deployments for the same software title to reduce confusion in Software Center (for Available deployments) or deployments that could potentially fight back and forth on detection (for Required deployments) . However, currently I have to delete the available deployment, which causes the immediate action of pulling the application from production via the Software Center as soon as client machines update policy. This causes one of two undesirable situations: I can leave a gap if I set the available application deployment to go live at 10AM for consistency in our release window OR make the new application available right when I create the deployment, which can create a rather scattered release window.
For required deployments, it would be similarly helpful to be able to expire the old deployments at the same time that the new deployments become available/enforced so there's seamless cutover.
If I could expire a deployment at a set time (critically, on an existing deployment), then I could create seamless transitions between available and required software being deployed to the environment. Additionally, this would also mean that I can setup these deployments far in advance, as soon as applications pass QA, rather than shortly before we want them live in production due to these less-than-ideal choices.
Agree. It would be very useful to have the possibility to configure the deployment of an application with expiration date.
I would love to see this change being implemented.
Absolutely agree this is very annoying and should be a no brainer change
Ashok K commented
there are tons of case when there a approved MW for a app install for only a given period. in such case, its important to have this ability to disable the deployment past that MW
totally - sort it out microsoft