Windows 7 Deployment – A Manual Approach to your first Baseline Image
Posted by: CSS Technical Team
When undertaking desktop deployment using SCCM, the first task begins after your SCCM Operating System Deployment (OSD) environment is configured and initial planning has been completed. This determines what your baseline image will contain, serving as the foundation for Windows 7 systems that you will deploy to your end users.
Creating a baseline image using SCCM is typically done using a Build and Capture task sequence. This installs Windows 7 from an ISO of the installation media onto a reference computer. It can then install updates, perform sysprep, and capture an image of the reference computer.
The default Build and Capture task sequence provides a Windows 7 system with default, out of the box settings. If that is all you need, you shouldn’t have much difficulty. If you want to add applications or custom settings to your baseline image, you need to modify the task sequence to automate your additional steps. If you are experienced at using SCCM for OS Deployment, you will be able to do this without much effort.
But if this is your first deployment, there can be a learning curve. If you miss something in your planning, it can take a significant amount of work and time building and testing your customizations to the task sequence before you get your desired baseline image.
It can be more efficient to build your first reference computer by installing Windows 7 manually from the DVD media, then installing your additional baseline applications and updates. As you do each manual step, document everything, and the order.
Keep in mind that this is a Baseline Image. By definition, a baseline is a starting point. Your final production deployment will start by applying this image, then using task sequences to add applications, install additional updates, activate Windows, and perform any number of other desired customizations to give the end user a complete, ready to work system. You should only build into the baseline a few applications which are infrequently upgraded and are used by everyone on your network. There are instances where having an application in the baseline image is better than installing it during deployment, such as when you want to minimize deployment time, or when you are deploying over slow links, but less is better for long-term management of baseline images.
When you have your desired reference computer configured, capture an image of it. Since you have SCCM in place, the easiest way to do this is using capture media created in SCCM. Simply insert the capture CD and launch the Image Capture Wizard. The system will be sysprepped and an image will be captured and saved to the network location you specified (for details on creating capture media, see http://technet.microsoft.com/en-us/library/bb694129.aspx).
Once you have your baseline image captured, deploy and test to be sure everything works as you intended. At this point, you can go back to your notes from the manual updates that led to the baseline image, and build those steps into a Build and Capture task sequence.
Why would you do that, when you already have a baseline image? Consistency. The person who built the first baseline image may not be the person who needs to update or reproduce it in the future. Different people creating a baseline image will end up with different results, unless very precise documentation is closely followed… or, unless there is a Build and Capture task sequence that will create the same image file every time.
So if you are struggling with, or overwhelmed by the prospect of creating a baseline image using Build and Capture, my advice is to manually build your first baseline image, then go back and create a capture and deploy task sequence so it will be there when you or your colleagues need it.
Of course, if you are just getting started with SCCM and Windows 7 Deployment, you can make it even easier on yourself and have a CSS Windows 7 Deployment expert perform an onsite Quickstart Proof-of-Concept, creating a sample baseline image and showing you the task sequence ropes as well as other details, tips, and tricks for OS Deployment with SCCM.