Jump to content


Quinten

PXE Boot on current branch 2010

Recommended Posts

I have stood up SCCM-CB 2010
I have enabled PXE boot on the DP
I have setup all boundaries
I am able to deploy software and push data to my DP
I have added the ADK including WinPE portion
I have read that starting in 1806 you no longer need WDS to make PXE work
I PXE a laptop and it dies brining me to the menu

press F1 key to retry boot
Press F2 key to reboot into setup
Press F5 key to run onboard diagnostics

I checked the time when I started the F12 / PXE on my laptop
I see nothing written to SMSPXE.LOG on my primary site server at the time I ran the F12 / PXE process.  

 

Not sure what I'm missing.  Thanks.  

 

Share this post


Link to post
Share on other sites

Hello.  Yes, I have that setting enabled on my boot image.     In my BIOS on my target laptop I have enabled secure boot, UEFI, PXE.   I have tried with RAID and with ACHI.   

in the SCCM everything seems to work.  system discovery, user discovery.  I can deploy both packages and applications.  on my target laptops Software Center works and I can pull applications from there.   So content distribution is working.  Which should mean boundaries are working.   

on my DP\PXE role I have:

Enable PXE, Allow this DP to respond to incoming PXE requests, Enable unknown computer support, Respond to PXE requests on all network interfaces, specify the PXE server response delay = 3 seconds.  

I even tried adding the WDM role.  That did not work.  So I removed the WDM.   

I have also injected the NET, SCSI and HDC drivers into the boot.wim.  

any other suggestions would be greatly appreciated.  

Edited by Quinten
update

Share this post


Link to post
Share on other sites

yes, I have distributed the boot image.   here is something I don't get.   I removed WDS.   Since I am in a lab I removed the DP role.   I then re-added the DP role and it Reinstalled the WDS Role and it recreated the C:\RemoteInstall folder.    It populates the folder with my boot images etc...    I read that starting in CB 1806 WDS is no longer needed?  Why did adding the DP role reinstall WDS?  

 

my distman log says this:

 

WDSServer is STARTED SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:29 AM 9784 (0x2638)
Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:29 AM 9784 (0x2638)
Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:30 AM 9784 (0x2638)
Failed to run: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall". Program returned c1030105 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Machine is running Windows Server. (NTVersion=0X602, ServicePack=0) SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
No need to configure the firewall SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Processing LAB00002 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Expanding C:\SCCMContentLib\FileLib\BD88\BD88B94A0A4DE3BE6CCCA83D5572627F6650FD2D7E9BE8A18F1C2A6208A24498 from package LAB00002 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Finding Wimgapi.Dll ... SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Found wimgapi.dll in system folder, wimgapi path: C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
SetObjectOwner() failed. 0x80070003. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Expanding LAB00002 to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:31 AM 9784 (0x2638)
Processing LAB00005 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
Expanding C:\SCCMContentLib\FileLib\88D5\88D543CD7DE2EF4F189DAED5B54D6D32B6CEB13262E7CFE407CE3014F8F32D32 from package LAB00005 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
Finding Wimgapi.Dll ... SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
Found wimgapi.dll in system folder, wimgapi path: C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
SetObjectOwner() failed. 0x80070002. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
Expanding LAB00005 to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:32 AM 9784 (0x2638)
CcmInstallPXE: Deleting the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Finished ConfigurePXE - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Updating DP setting from SCF to DP machine, configure branchcache, LEDBAT, DOINC - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
DP monitoring task is disabed on server SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
No need to initialize monitoring task on SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
DP settings have been updated to SCCM.TEST.NET [sccm.test.net]. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Initialize usage gathering task on SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
IIS Version 10 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Successfully saved iis settings. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Log Location C:\inetpub\logs\LogFiles\W3SVC1 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
Successfully enabled usage gathering on the local distribution point. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
1998-01-01T00:00:00 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
DP settings have been updated to SCCM.TEST.NET [sccm.test.net]. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:33 AM 9784 (0x2638)
OS information for the server - 10.0.17763, ProductType=2 SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638)
Finished updating DP setting from SCF to DP machine, configured BranchCache, LEDBAT, MCC - SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638)
DP configuration thread done for distribution point SCCM.TEST.NET [sccm.test.net] SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 9784 (0x2638)
DP config change processing thread: thread completion event. SMS_DISTRIBUTION_MANAGER 4/13/2021 9:30:34 AM 8052 (0x1F74)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.