Microsoft System Center Configuration Manager Advanced Deployment by Martyn Coupland

Author:Martyn Coupland [Coupland, Martyn]
Language: eng
Format: azw3, epub, mobi, pdf
Publisher: Packt Publishing
Published: 2014-09-24T16:00:00+00:00

The following diagram shows the relationship between the components involved in the delivery of applications using Configuration Manager:

The diagram also lists all of the components within the Configuration Manager client and the components of WMI that are involved in this process; the components are as follows:

Management point

Configuration Manager client

Configuration item state store

Configuration item models

Windows Management Instrumentation

When to use packages

With all this information of application management, you might wonder what the point in using packages is. Many customers of Configuration Manager still use packages as their primary deployment method.

I have heard a lot of reasons why people still use packages after their migration to Configuration Manager. One thing that is common after discussing this with customers is that reasons for sticking with packages are generally not valid.

The most common reason is that executable or batch files cannot be created as applications. This is simply not the case. Configuration Manager has a deployment type called script installer. The easiest way to think of the script installer is for anything else not listed in the drop-down box.

Uses for the script installer deployment type could be some of the following, which might be used to deploy applications:

Executable

InstallShield installers

Batch files

PowerShell

VBScript

JScript

Custom bootstrap

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.