Enable SCCM PXE Without WDS on a Windows 10 computer, but what about SMP?

-

Starting SCCM 1806 comes the exciting new feature that will redefine the design and planning of SCCM sites. Or does it? Well the answer is, not entirely.

With PXE responder, one can use a client OS (Windows 7,8,10) to respond to PXE request without the need to setup a WDS.

Prior to CB 1806, if you had a remote distribution point and wanted to image using PXE, you’d have to use a server OS because of the pre-requisite of the installation of Windows Deployment Service (WDS).

But now, since the introduction of PXE responder, the setup is simplified and certainly saves a lot of cost by eliminating the need to setup up a server OS, possibly with its own hardware that was being used as a distribution point.
However, this new feature does come with some limitations –

First, it doesn’t support Multicast, so if you need multicast, you need to stick with Windows Deployment Service (WDS).

Second, client OS, especially Windows 10, still doesn’t support SMP. Which means you cannot use a distribution point running on Windows 10 for USMT as SMP will not configure.

However, if USMT is not a requirement for you, then see the process below on how to setup a PXE responder without WDS.

Distribution Point Configuration (PXE Responder)

You can use the Enable a PXE responder without Windows Deployment Service option on a server OS that is already PXE-enabled or select it while creating a new DP.

SCCM will suspend the Windows Deployment (WDS) Service and enable the new ConfigMgr PXE Responder Service on an existing DP or configure a new one without ever installing WDS in the first place. However, you always have the option to disable PXE responder and replace it with legacy solution of using Windows Deployment Service (WDS).

This is how it goes -

In the SCCM Console

·       Go to Administration \ Site Configuration \ Servers and Site System Roles
·       Select your Distribution Point and right-click Distribution Point in the roles, select Properties in case of an existing role OR while creating a new role enable as covered in the next step.
·       In the PXE tab, select Enable a PXE responder without Windows Deployment Service.



·       Select Yes




·       Click Apply and Ok to commit.

The new ConfigMgr PXE Responder Service is created. In an existing DP, WDS service will disable and the new ConfigMgr PXE Responder service will start.



Refer to the SMSPXE.log on your DP. It will be located under InstallationDrive\SMS_DP$\SMS\logs

SCCM PXE as a service is configured and starts responding to PXE requests.






Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Intune: UAC Elevation Prompt Behavior for Standard Users

-
Image
Implementing and maintaining a good security posture is an integral part of overall IT security governance for most organizations now. While you want to harden the security of infrastructure and give least number of privileges to your end users, sometimes you may need to cut back on the restrictions to ensure a good user experience and an effective IT support process. Recently, I had a requirement where the customer wanted to ease the restriction on the end user devices to make the helpdesk support process more efficient. This involved easing the UAC level access for the Standard users and if you are managing your devices using Intune, then this blog may just help you. Let us see what all is involved and some of the ways that you can use to implement this easily. Policy CSP – LocalPoliciesSecurityOptions LocalPoliciesSecurityOptions has many CSP settings and if you are managing these settings at an individual level, then the CSP that we need to concern ourselves with here is U
Read more