System Center Configuration Manager 2007-Step by step guide installing SCCM 2007 Part 4

Step by step guide installing SCCM 2007 Part 4 series we will install & confiure Windows Deployment Service on PILOT-SCCM-01.

Note: I am assuming that you have now installed PILOT-SCCM-01 Operating System.

Windows 2008 R2 x64 BIT

How to Install Windows Server 2008 R2 Step by Step

The Windows Deployment Services is the updated and redesigned version of Remote Installation Services (RIS).

In this lab because we want to use the rich features of System Center Configuration Manager 2007 & not WDS; is capable of deploying images by itself with limited functionality.We will use WDS to assist us in this process.

WDS is the PXE server for System Center Configuration Manager 2007. System Center Configuration Manager 2007 hands off the request to WDS after checking it's own database to make sure it knows about the computer.

Note: System Center Configuration Manager 2007 R2 also introduces the ( Unknown computers support ) once again.
Known issues with configuring Windows Deployment Services
If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes.
If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the following:
(recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts).
Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to REMINST/SMSBoot/x64/pxeboot.com.

NOTE: In this lab WDS is also our SCCM server & DHCP is running on our Domain Controller !!!


Prerequisites for installing Windows Deployment Services:

Active Directory.  PILOT-DC-01
DHCP. You must have a working Dynamic Host Configuration Protocol (DHCP) server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.
DNS. PILOT-DC-01
NTFS partition: The server running Windows Deployment Services requires an NTFS file system volume for the image store.

To install the role by using the command line, run one of the following two commands:

For Deployment Server, run ServerManagerCmd -install WDS.
For Transport Server, run ServerManagerCmd -install WDS-Transport.

To install the role by using Server Manager, click Add roles, which is located in the Roles Summary pane. Click Next and then select Windows Deployment Services.












Click Next >





Click Next >



Click Next >



Click Finish
Note: In some documents you will come across where you will be instructed NOT to configure WDS & some will recommend configuring WDS initial wizard & not importing any images.
From my testing you can do either and it works fine results are indentical.
I personally ensure that the PXE request delay (explained further in the article) in WDS is set to longer than the PXE service point in SCCM.









Right click > Configure Server














Untick the " Add images "

Click Finish.





We need to allow WDS to respond to all ( Known & Unknown ) Computers.

Also set the PXE response delay to 1

Note: This will ensure that SCCM PXE service point will respond before WDS responds.



We need to ensure that the WDS service is also set to " Automatic Delayed Start " this simply ensures that WDS service does not fail at auto start or else everytime you restart the server WDS services will need to be manually restarted.




When WDS service is set to "Automatic Delayed Start" this change is also reflected in the registry at the following location.


Watch this space for Part 5