Windows – Deploying Windows 7 with MDT over a WiFi connection

For ten laptops I would definitely use MDT. Download the package from Microsoft and read through the docs, they're quite good and cover all of the steps you need to make it go. If you encounter larger numbers of machines to deploy to I would then look towards WDS but use it with MDT.

Microsoft Deployment Toolkit 2010 Microsoft Deployment Toolkit (MDT) 2012 Update 1

Overview

You can distribute a WinPE image using pxelinux or any other PXE boot technology. That will get you a scriptable command prompt able to launch an unattended install.

You can use WAIK to create an unattend.xml file that's called during setup where you can create your own build scripts that meet whatever it is that your needs are. The unattend file can call batch or powershell scripts as well as any other application during the post-install phase for customization.

I strongly doubt that there is any commercial product that will do this. If you want to have a Windows imaging environment integrated with a Linux one, you're going to have to hand-roll a lot of it yourself. The good thing is that the tools to do it (WAIK,DISM, WinPE, etc) are all freely available.

Design Basics

You'll want to create an SMB share with a copy of the Windows OS installation files that you want to deploy. You can modify these files (incorporate patches, Windows modules, etc,) with DISM.

Once you have that, you'll want to deploy WinPE through whatever PXE solution you use. You can edit startnet.cmd in WinPE to contain whatever custom commands that you want. This cmd file is executed when WinPE loads. This will allow you to automate the install. At a minimum, you will map the SMB share with the source files

net use \\server\share

and call

\\server\share\setup /unattend:\\server\share\unattend.xml

This will run setup in unattended mode, assuming you've configured your unattend file correctly. There are many examples of how to do this on technet.

In the OOBE phase of the unattend file, you can configure autologin and call whatever build scripts you need. Slmgr.vbs can change product keys and activate, you can call netsh to set IP info, and directly in the unattend.xml, you can specify the creation of local users and groups.

This gives you a completely customizable install environment that can PXE boot from any TFTP server. It's a lot of trial and error if you've never done it before, but it can absolutely be done.