Windows – Image -> Answer File -> Sysprep -> Image

Image of what? XP? Windows 7?

Sysprep is it - because sysprep properly removes the system's identifying components, for lack of a better description coming to mind. While Mark Russinovich detailed a year ago that SIDs were really not an issue, he also noted that some services still need sysprep to have been run for a cloned machine to work properly (he noted WSUS).

In the case of XP, yes, you are likely to have headaches when you clone between CHIPSETS (which is really the key point in XP). For Windows 7, I think the only restriction is CPU Brand - one image for AMD, one for Intel and you should be good. (and of course, one 32 bit and one 64 bit - if you want both platforms).

Of course, you could look into Microsoft's deployment tools - they are QUITE EXTENSIVE, offering task sequences that can make the deployment of apps and similar items much easier. Specifically, check out:

• Microsoft Deployment Toolkit
• Windows Automated Installation Kit
• Windows Deployment Services (especially on 2008, this supports Multicasts; if you need help setting up, I have a I link I can give you)
• User State Migration Tool

among others.

Is there a way I can take my image from the already configured laptop and load that image on another laptop using an answer file to automate the windows setup?

Yes, while you COULD use just standalone WAIK tools, you should really use them in conjuction with the Microsoft Deployment Toolkit. (AIK is just commandline tools, MDT is the GUI and scripts) Part of the confusion here is what toolset does what. You really need both MDT and AIK to deploy windows 7 successfully. AIK is the toolset, MDT is the workbench. MDT is the automation framework you're missing, AIK alone won't cut it.

While in theory you could use just imagex and sysprep, you're making things more complicated than they need to be. Using the Microsoft Deployment Toolkit (MDT) 2012 Update 1, you can build, capture, and deploy windows image files (WIM). WAIK is the set of tools that MDT uses to automate the whole process.

Download the MDT 2012 Update 1

http://technet.microsoft.com/en-us/solutionaccelerators/dd407791.aspx

Theoretically one could use just WDS and WAIK. but it's not really recommended. Most people don't need WDS unless you're PXE booting, and pushing dozens and dozens of PCs at the same time, besides, you need Server 2008 or 2012 to get WDS. MDT can be hosted from any vista, win7 or 8 box you have laying around. Once MDT is installed you would use the Windows Automated Installation Kit (WAIK) in conjunction with MDT. In your case, this laptop you want to build a thick image with can be captured and used as an reference, you need to capture it first then import into a deployment share.

MDT uses deployment shares to push both thick and thin images. Traditionally, most people have used thick images in the past, but where MDT really shines is in its ability to push drivers and software after an a lean clean and mean thin image has been applied during a task sequence. Its widely regarded as best practice in MDT to build two shares, one for builds with it's own task sequence, and another for deploying. If your systems are 100 homogeneous, you can get away with using the old school "thick images"

Confusing? Yes, but here's the deal, MDT builds images for you, captures them, and then formats, images, names the workstations installs drivers, applications, windows updates, and can even join them to a domain or workgroup if you even want to.

Build two shares in MDT, one for building images, one for production. Do yourself a HUGE favor and build your image in a VM. That way it can run on anything.

Install MDT & AIK 1. Install MDT 2012 2. Install WAIK 3.0 3. Install WAIK Supplement (3.1)

Building a Reference Share

4. Create Deployment Share
5. Import OS (Vanilla .wim NOT a customized .wim)
6. Create Task Sequence & enable windows updates
7. Customize unattend.xml answer file
8. Insert LTI Suspend in state restore in the task sequence(optional)
9. Import Applications (optional)
10. Update Deployment Share
11. Burn ISO

Capturing Reference Image

1. Boot to CD in VM
2. use MDT to apply updates, tweaks, install apps
3. When LTI suspend executes, make changes then resume from icon on desktop
4. Capture image

Building a Production Share

4. Create a Second Deployment Share
5. Import OS (customized .wim) from VM capture
6. Create Task Sequence & enable windows updates
7. Customize unattend.xml answer file
8. Import Drivers (optional)
9. Import Applications (optional)
10. Update Deployment Share
11. Burn ISO

Deploying Captured Image

1. Boot to MDT CD
2. Select Task Sequence
3. Deploy Image & Repeat until deploys are complete.

Deployment Soup Video

http://technet.microsoft.com/en-us/windows/hh215959

Deploying Windows A - Z

http://www.microsoft.com/en-us/download/details.aspx?id=6157

Learning to use MDT litetouch

http://www.deploymentresearch.com/Videos/MDT2010LiteTouchUnleashedVideos.aspx