The ability to deploy applications has long been a primary function of Configuration Manager. The Application Deployment feature of Configuration Manager 2012 is the new approach for software deployment and allows administrators to deploy almost any kind of content to Configuration Manager clients, affecting potentially thousands of systems or users.
The list of content deployable through Application Deployment includes virtually anything—from full applications (i.e., Office) to scripts and batch files. Beyond simply specifying what to deploy is also the ability to detail how to deploy, including whether an application should be delivered to systems versus users or whether the application should be a full installation on the target system versus a virtualized version using App-V.
With so much flexibility and power comes a great amount of responsibility. Configuration Manager provides robust ability to define and control Application Deployment to systems and users. When properly used, the experience with Application Deployment will be very positive, ut it is also possible to make mistakes with this feature and deliver the mistakes to potentially thousands of systems or users. This underscores the need to completely understand the feature and its various options and also the need for proper testing before introducing a change to such a potentially large number of systems or users. This need for proper understanding and testing is not unique to Configuration Manager but applies to any product of enterprise scale.
No comments:
Post a Comment