Most support issues with Operating System Deployment (OSD) in System Center 2012 Configuration Manager stem from product misconfigurations. While there are no simple guides to implement something as powerful and complex as OSD, this article describes the step-by-step process for configuring System Center 2012 Configuration Manager (ConfigMgr 2012) to capture an existing Windows image, then walks you through creating a Client Package and Task Sequence to deploy and install that image.
This article assumes you have an existing environment that has a Configuration Manager 2012 site installed as well as a primary site that is running Configuration Manager 2012. These steps can also be used with a standalone primary site running Configuration Manager 2012. Further, this article requires that the Network Access Account and Boundaries are properly configured, and that ConfigMgr client agents are installed on the clients.
You can find the complete article here:
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/