Windows Deployment Services: Difference between revisions
Jump to navigation
Jump to search
(Initial creation) |
m (→Prepare Gold Image Machine: Added to procedure) |
||
Line 42: | Line 42: | ||
# Type in the name of the WDS server and click '''Connect''' | # Type in the name of the WDS server and click '''Connect''' | ||
#* See [[#Unable to Connect WDS server|Unable to Connect WDS server]] in case of problems | #* See [[#Unable to Connect WDS server|Unable to Connect WDS server]] in case of problems | ||
# Once complete, go to WDS server, Right-click over ''Install Images'' and select '''Add Install Image...''' | |||
# Find <code>wim</code> file | |||
# Update name/description as required | |||
=== Unable to Connect WDS server === | === Unable to Connect WDS server === |
Revision as of 09:02, 2 August 2013
- Boot images - provide an installation environment/platform, from which to install an OS
- Capture images - provide a capture environment/platform, from which to ingest a gold install of an OS
- Install images - OS installation images
Setup DHCP
DHCP is used to provide booting machines with an IP address, and then direct them to a boot image.
- In DHCP setup the following Scope Options
066 Boot Server Host Name
- hostname of WDS server067 Bootfile Name
- share path to boot file, eg\Boot\x86\wdsndp.com
or\Boot\x86\PXEboot.com
- If WDS server is not on same subnet as clients, allow DHCP broadcasts to WDS server
- Same as required for a DHCP server,
ip helper-address
for Cisco
- Same as required for a DHCP server,
Create a Boot Image
- Right-click over Boot Images and click on Add Boot Image...
- Locate a boot image (EG
boot.wim
in the sources folder on an OS install CD) - Provide an appropriate name and description
- Allow the creation to complete
- You may need to add additional drivers (eg for a NIC), right-click over the image and select Add Driver Packages to Image...
Create a Capture Image
- Right-click over an existing Boot image and select Create Capture Boot Image
- Give the image an appropriate name, description, and specify where it should be saved
- Click Next to initiate the creation of the image
- Tick the box to allow creation of boot image
- Accept the file location (should be as previously specified)
- Edit name and description if required
- Accept selected image, and complete.
Prepare Gold Image Machine
- Install and configure a PC as you want to deploy (check and double check)
- Run Sysprep to prepare the machine for imaging
cd C:\Windows\System32\sysprep
sysprep /oobe /generalize /reboot
- Eventually the machine will reboot, get ready to hold
F12
once at BIOS to ensure a network boot - When prompted, select Network Boot, Onboard NIC, etc
- You may need to hit
F12
in order to be able to select a boot image - Select the Capture Image to boot
- Select the drive to image
- Select a file to save the image to (can be on the same partition the image is coming from)
- Tick the Upload image to a... option
- Type in the name of the WDS server and click Connect
- See Unable to Connect WDS server in case of problems
- Once complete, go to WDS server, Right-click over Install Images and select Add Install Image...
- Find
wim
file - Update name/description as required
Unable to Connect WDS server
- Press
Shift
andF10
- Run
ipconfig
to confirm networking - If not running, run
wpeutil InitialzeNetwork
- Run
ipconfig
to confirm networking - If still nothing, run
netsh interface show interface
- If this shows nothing, your NIC can't be found so you'll need to just save locally, then boot back into the OS of your source machine and copy the image off manually.
Enable Multicast Transmission
Note that whilst images will preferably delivered by multicast, if they don't proceed fast enough (or at all), they'll fall back to SMB file copy
- Right-click over Multicast Transmissions and select Create Multicast Transmission...
- Give the Multicast Transmission a name, eg Auto-Cast
- Select the image group that will have images delivered by multicast
- Leave Auto-Cast selected
If multicast transmissions are slow or fail, you may need to reduce the multicast packet size (if your network doesn't handle fragmentation well).
- Windows 2008 R2 - In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Protocol
, change the followingApBlockSize
to 1385 (from 8785)TpCacheSize
to 3145 (from 1190)
- Windows 2008 - In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Profiles\Custom
, change the followingApBlockSize
to 1385 (from 8785)TpCacheSize
to 3145 (from 1190)
Restart the WDSService to apply