The Integration Pack for System Center 2012 Configuration Manager, distributed via Orchestrator, causes the loading of the SCCM admin console to crash on servers that have been distributed to.
Error specifics of the Admin Console crash are:
Windows Installer has been the default installation format on Windows machines for well over a decade now. The technology was elegant and powerful but proved too complex for the subtle quirks to be fully understood by many people working with technology.
Bootcamp Is the application provided by Apple to allow 64bit Windows to run on an Apple produced machine. The application is provided in a zip format that calls an MSI with the current version being 5.1.5652, available from http://support.apple.com/downloads/#macoscomponents
With MDT 2012 and 2013 integrated with SCCM, default Client Replace Task Sequences can cause a situation where machines installed with the Task Sequences end up with Windows installed to D:\ not C:\. This is primarily because, during the install process, the C:\ driver letter has already been assigned to the so the system drive takes the next available drive letter.
I recently had a need to produce a full report to show the full INF driver details from within SCCM. We can see an original “Driver Source” folders from within the SCCM console as the path represents a field within the SCCM database.
One of the biggest problems with the use of “fat” Windows Images is accidental contamination of a production Image. A seemingly minor update can have unexpected consequences when background processes also make unnoticed changes. The only way of being certain of how a WIM Image has been created is to fully automate the process with Task Sequences so accidents can’t happen & an audit trail is left behind.
User State Migration (USMT) is a flexible framework for controlling how user data is managed during machine rebuilds. It uses XML for declaring rules over data is backed up and restored.
Every “component” has a unique display name and when being custom developed by administrators, they will generally consist of “documents” as a data type (just as the following role is likely to be “data” manipulation too.
SCCM 2012 allows for the bulk import of Machine accounts through the right click options of “Devices” within the SCCM console.
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.”
Recently I was forced to look at how Microsoft’s approach to factory pre-loading Windows has evolved. After coming to terms with the earlier (and legacy) “breadcrumbs” approach, I was surprised as the polished simplicity of the Deployment Toolkit’s “LiteTouch OEM” sequence and even more impressed with the approach from SCCM 2012.