Below are some key takeaways from the Configuration Manager 2012 CEP session on OSD, which took place on December 15th. Session speaker for this topic was John Vintzel, Senior Program Manager in the Configuration Manager team.
Offline servicing:
- A feature allowing to update an OS stored in the Configuration Manager library, eliminating the need to redeploy and recapture it.
- Beneficial for reducing deployment time and exposure to vulnerabilities during deployment
- Allows for scheduled updating at any time
- Based on the DISM tool (from the WAIK)
- Works for Vista SP1 and Windows Server 2008 and later OS’s, for all CBS based updates
Media Updates:
- Prestart command (used to be pre-execution hook) improvements
- No more complex steps to add prestart command to media
- Ability to include files and add media specific variables
- Available with prestaged, bootable and standalone media
- Automation improvements
- Improvements to help with Zero Touch deployments. No more "click Next".
- Unattended boot media mode, eliminating most forms of user intervention
- Deployment selection from prestart command (scripts, custom HTA …)
- Hierarchy-wide Media
- Media no longer tied to a specific site
- Media will dynamically find site and MP based on boundaries
- Overrides and site specific media are also available
USMT 4.0 Integration:
- Easy and integrated way to use USMT 4.0 features with Configuration Manager
Application Integration:
- New SWD features can also be used for OSD
- Install application for Applications or install Packages for classic packages and programs
- Real time requirement evaluation and honoring of dependencies
- Applications do require installation mode for systems
User Device Affinity (UDA):
- Define user and device relationship during rollout of the machine
- Administrator defines the setting for UDA (do not allow, require approval or auto-approve)
- Associated to certificate, which can be revoked at any time
- Available to boot media, prestaged media and PXE
Apps and UDA new features allow different approach and specific usage scenarios:
- Use applications for complex software installations
- Use task sequence for the deployment of an OS
Centralized Management:
- Improved experience for centralized administration
- Components used for OSD can be managed from the CAS or primary site
- Also Task Sequences are global data which can be deployed from the CAS or primary site
- Computer Import and Association can occur from CAS or primary site
(Association requires 2 systems from the same site) - OSD related roles like Distribution Point, PXE Service Point and State Migration point can only be installed at a site, as no client are managed directly from the CAS.
