Dashboard

Installing and Configuring System Center Configuration Manager (SCCM)

0%

0/1 Lessons

Getting Started with this Course

• 26min

0 / 3 lessons complete

System Center Configuration Manager - Features and Capibilities

• 31min

0 / 5 lessons complete

SCCM 1902 Lab Setup

• 51min

0 / 12 lessons complete

Installing SCCM 1902 Installation

• 1hr 32min

0 / 11 lessons complete

Configuration Manager Basics

• 1hr 58min

0 / 8 lessons complete

Updating SCCM

• 30min

0 / 7 lessons complete

SCCM Client Installation

• 46min

0 / 4 lessons complete

User and Device Collections

• 1hr 6min

0 / 13 lessons complete

Application Management

• 2hr 34min

0 / 12 lessons complete

Operating System Deployment

• 23min

0 / 7 lessons complete

Endpoint Protection

• 1hr 12min

0 / 10 lessons complete

Troubleshooting

• 37min

0 / 4 lessons complete

Problems and Solutions from the Message Board

• 14min

0 / 5 lessons complete

Enable PXE Support – Configure WDS

Instructions

Q&A (0)

Notes (0)

Resources (0)

Saving Progress...

Resources

There are no resources for this lesson.

Notes can be saved and accessed anywhere in the course. They also double as bookmarks so you can quickly review important lesson material.

Create note
  • So that computers in the Unknown computer collection will be able to request a deployment image from the network. The operating system image and the Windows PE boot image are sent to a distribution point that is configured to accept PXE requests.  
  • Open Configuration Manager, from the Workspace, click Administration
  • From the Navigation Pane double click Site Configuration, then click Servers and Site System Roles. 
  • From the List View, right click distribution point, click properties 
  • Click PXE, click the box and Enable PXE support for clients. 
  • Windows Deployment Services will be installed.Important, install but do not configure WDS
  • Check Allow this Distribution point to respond to incoming PXE requests. 
  • Check Enable unknown computer Support, read the warning, click ok 
  • Check, Require a password when computers use PXE, type the password twice 
  • User device Affinity – Select do not use device affinity 
  • From network interfaces, select Respond to PXE requests on all network interfaces.
  • Click ok 

DHCP and WDS on the same server 

If you have DHCP and WDS on the same server. Configure the registry and configure WDS to use option 60. Relax it’s easy 

Registry edit –From the server where DHCP and WDS is installed, in this case ITFSCCM01  

Open a command prompt, administrator level, then type regedit

  • Drill down into the registry following this path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WD SPXE

  • To the right, double click UseDhcpPorts, change the value from one to 0, click ok,  close the registry

Configure WDS to use Option 60  

  • From the same administrator command prompt type the command

WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

Start the Client Deployment 

  • Open Virtual Box, double click the client computer ITFWS03
  • the OSD process now begins. 

Congratulations you have completed this lecture. Thanks for watching and we will see you in this next lecture.

Server Academy Members Only

Sorry, this lesson is only available to Server Academy Full Access members. Become a Full-Access Member now and you’ll get instant access to all of our courses.

0 0 votes
Lesson Rating
Subscribe
Notify of
profile avatar
2 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

profile avatar
aaron marriotti(@aaron-marriotti)
#75312
Member
1 year ago

if my company does not use a PXE Server, how can I use the deployment out of SCCM far as network controls

0
Reply
profile avatar
robert.hill(@roberth2)
Admin
#75317
Reply to  aaron marriotti
1 year ago

Hello Aaron,

The ultimate answer and supported method is to use IP helpers. These are options that are specified within your networking equipment. Using IP helpers tells your device where to go for the boot file then your PXE/WDS/SCCM server dynamically delivers the correct boot file for the device architecture/firmware.
I would take a look at your networking devices and check for alternatives.

https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/understand-pxe-boot.

0
Reply