Some points of attention in the process of building Windows Deployment Service (WDS)

Basically, the installation of WDS on the server is very easy, but this WDS has a prerequisite for its effect. Conditions can refer to this article on the Internet list:

The active Directory:windows Deployment service server must be a member of the Active Directory domain service domain or a domain controller in the Active Directory domain service domain. The version of the Active Directory domain service domain and forest is not relevant, and all domain and forest configurations support Windows Deployment Services. DHCP: Because the pre-boot Execution Environment (PXE) used by Windows Deployment Services relies on DHCP for IP addressing, you must have a valid Dynamic Host Configuration Protocol (DHCP) server with active scope on the network. DNS: You can run Windows Deployment Services only if you have a valid dynamic name Service (DNS) server on your network. NTFS Volume: The server running the Windows deployment service needs to have an NTFS file system volume to store the image. Credentials: To install this role, you must be a member of the local Administrators group on the Windows Deployment Services server. To start the Windows Deployment Services client, you must be a member of the Domain Users group.

However, what this article does not mention is that DHCP and WDS servers need special configuration if they are on the same platform or in different subnets. Here I use the same server, just say this, this issue can be seen from this post: http://support.microsoft.com/?scid=kb;en-us;954410&x=15&y=14

In fact, just set up a 67 port that prohibits the WDS service from listening to DHCP.

　　

Also, in the narration, WDS supports the deployment of a VHD image. The supported operating systems are only Windows Server 2008 R2, Windows 7 Enterprise Edition, and Windows 7 flagship.

After setting it up, be aware that your WDS server is configured to respond to any client requests.

Copy the Sysprep.exe and Setupcl.exe files in the Support/tools/deploy.cab package from the installation disk of the system installed by your client to C:/sysprep and execute Sysprep-nosidgen- Reseal.

Restart from the NIC boot to PE inside, you can start into the PE, here, in order to prevent the HAL error, the proposed direct use of Vista PE, note that this PE is from the Windows AIK tool to take, However, if you use the WAIK2.0 version of the Wdscapture program, there are two solutions, one is to call back the long version of AIK, and the second is according to the two tips to do:

If you are are using MDT, don ' t store the images in WDS, store them in the deployment share. As far as capture goes in MDT for you have two major options ... Option 1 Create A Build & Capture task sequence (standard client task sequence) in MDT and allow it to run the whole W Ay ... End result = A wim file on the server ... Option 2 Create A Capture only task Sequence (Post-os installation task Sequence) "You execute on" an existing machine That's want to capture. The TS would then run Sysprep, reboot into WinPE and capture to a WIM file.

Here, because I am using the first kind, so run the direct input after wdscapture can be. You can then save a WIM image locally and then upload it to the WDS server as required.