Here is a summary of how to capture an image for the Deployment Workbench.
- Boot the system to be captured and use the sysprep tool.
- Boot the system from either the CD or PXE boot and choose command prompt from the menu.
- Run diskpart at the command prompt.
- list volume # Check the volume of the disk you are imaging to get the correct drive letter
- exit #leave diskpart
- net use u: \\g212win2012r2\DeploymentShare$ # Capture network drive to place image in. You will need to adjust based on your server name and deployment share. This is using the default share created by MDT. Use domain name in the username.
- dism /Capture-Image /CaptureDir:D:\ /ImageFile:U:\Captures\TestImage.wim /Name:”TestImage”
- Import captured OS in the Deployment Workbench
- Create new task
- Boot from CD or PXE to install your newly capture image to another system
Here is a quick outline of the steps I followed to install the MDT and WADK on a Windows Server 2012 R2 System. Please be advised that these are from notes from the first walkthrough of setting this system up. I am certain there will be some typos, unnecessary steps, out of order steps, and other issues with these instructions.
- Install Microsoft Deployment Tools
- Install WADK
- Start Deployment Tools and create Deployment Share
- Right-click Operating Systems and Import Operating System
- Right-click Operating system and update operating system
- Create new install task
- Burn ISO file in Boot folder to CD
- Boot new machine from CD
- Start task
- From Deployment and Imaging Tools Environment, Create Bootable flash Drive
- copype amd64 C:\winpe_amd64
- MakeWinPEMedia /UFD C:\winpe_amd64 F:
- Create Deployment from Windows System Image Manager
- File, Create Distribution Share
- Copy install.wim from media to server
- Select Windows Image file, will have to create a catalog file
Some helpful links from Microsoft are:
Once you boot from the remote system, you work from the command prompt to create a new image. The tool is DISM.
I have been playing around with the Microsoft Deployment Toolkit (MDT) on Windows Server 2012 R2 and decided I need to my client machines to perform a PXE boot instead of booting from a CD, which takes quite awhile. Configuring Windows Deployment Server is a fairly easy process, especially if you all ready have a bootable WIM created from using MDT. These instructions assume you have already setup MDT on your server and that your server is a member of a Windows Domain. The basic process is as follows:
- Add the Windows Deployment Server (WDS) Role from Server Manager on the server you wish to boot from. You will need to restart the server after this role is added.
- Open a command line to initialize your server with the command wdsutil /Initialize-Server /RemInst:”C:\DeploymentShare\boot”, assuming you are using the default directory from your MDT installation. If you encounter an error during the initialize step, you may need to issue the command wdsutil /Uninitialize-Server so that you can fix the error and then try to initialize the server again.
- Next you will add the WIM you wish to boot from with the command wdsutil /Add-Image /ImageFile:”c:\DeploymentShare\Boot\LiteTouchPE_x64.wim” /ImageType:Boot.
- Check Services to make for sure the Windows Deployment Services Server is running.
Assuming everything worked correctly, you should know be able to connect a computer to the same network as the server and PXE boot from the client to the server without the need of a flash drive or optical disk. You may need to enable PXE boot on the client machine, or change the boot order of the devices.
Microsoft has a web page that includes all of the syntax for the wdsutil command available at http://technet.microsoft.com/en-us/library/cc771206.aspx.