Best Practices for Application Management in Configuration Manager
Updated: January 1, 2013
Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 R2 Configuration Manager
Use the following best practices for application management in Microsoft System Center 2012 Configuration Manager.
When you modify a deployed application, any new installations will use the modified version of the application. If, when you modify the application you also modify the detection method associated with the application, then all deployed copies of the application will be updated. To provide greater control for application updates, use application supersedence. For more information about how to supersede applications, see How to Use Application Supersedence in Configuration Manager.
Because users cannot install applications from the Application Catalog from a Windows Embedded device that has write filters enabled, always deploy applications that are required rather than available to these devices. Typically, this will not be a problem because computers that run a Windows Embedded operating system often run a single application that must run in the same way for multiple users. Because of this, these devices are highly managed and locked down by the IT department. Required applications are well-suited to this scenario. However, if users do run more than one application on embedded devices when write filters are enabled, educate these users about the following limitations:
Users cannot install applications from the Application Catalog.
Users cannot install required software from Software Center.
Users cannot change their business hours in the Options tab of Software Center.
Users cannot postpone the installation of a required application.
In addition, low-rights users cannot log on during a maintenance period if Configuration Manager SP1 is committing changes for software installations and updates. During this period, users see a message informing them that the device is unavailable because it is being serviced.
When writer filters are disabled so that Configuration Manager can install software on embedded devices, low-rights users cannot log on to the device. If the installation requires the user to accept the license terms, this will not be possible and the installation will fail. Make sure that you do not deploy software to Windows Embedded devices if the installation requires user interaction. You can use the Applicable Platforms list to filter these operating systems.
For additional resources, see Information and Support for Configuration Manager.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.