Documents related to System Center Configuration Manager
Generally, using WMI to query a mainboard and determine driver sets is quite a straightforward exercise. We can easily run up a tool like MSInfo32.exe to determine the Manufacturer and Model of a machine and these same BIOS files can be used in a Task Sequence to allow a driver set to be used. The Image above shows a series of models that are available for the Manufacturer “Dell Inc.”
A common problem with SCCM can be the long delays after OS deployment for a full compliment of applications to be installed.
SCCM 2012 R2 is a great product but I have some strong disagreements with some elements of how it deals with software management. By default, the product suggests that a Windows Installer Product Code can be used to uniquely identify when a package is installed to a machine. This is a misunderstanding that “Product Codes” are not unique to Windows Installer packages – “Package Codes” are. It also overlooks that the same utility or product may be installed in an organisation as different variants such as the “HR package” or the “Spanish package” or the “me
The Desired Configuration Management within SCCM 2012 relies upon Operating System Expressions when constructing rules for software deployment. The Requirements tab of an Application "Deployment Type". When scripting the creation of SCCM Applications (either with Powershell of C#) the Operation System representations have to be written in a specific format to be valid.
This Launcher is a C# compiled executable that interprets a local XML configuration file to install or remove a software package. It is designed to separate the complexity of logic that can surround a software installations from configuration information while providing an audit mechanism over a software library.
The Launcher is an evolution to a standardised deployment “wrapper” that provides a standardised interface for all applications. It separates configuration information from the logic of installing and uninstalling applications.