Skip to content

Problems Adding PXE to DP

Featured Replies

I am trying to get PXE setup on all my DP's and I'm finding a number of them that aren't working. I'm using 2012 SP1 CU2 and for the DP's that aren't working, it appears that the RemoteInstall\SMSBoot\X64 and X86 folders are completely empty. This is on both 2008 SP2 and 2008 R2 SP1 DP servers.

 

The process I'm using is to open the properties of the DP in the configuration manager console and to enable PXE there. I've also enabled PXE in both my x64 and X86 boot images. I'm not manually doing anything with WDS. It's working on some so my process seems to be correct.

 

In looking at the distmgr.log I see the below error, but I can't really find any info on this to know what the problem is.

CDistributionManager::ConfigurePXE failed; 0x80041001

 

Any suggestions on what I can do to get this working?

 

Thanks,

  • Author

These are all fresh installs of CM12SP1 and the servers are running Endpoint Protection. I can see that the RemoteInstall\Boot\x64 folder does have pxe files so it seems unlikely that it would be antivirus blocking them?

  • Author

A little more info...

This is from the smspxe.log file on one of the affected DP's.

 

InstallBootFilesForImage failed. 0x80004005 SMSPXE 8/23/2013 3:27:40 AM 3552 (0x0DE0)
Warning: Failed to copy the needed boot binaries from the boot image F:\RemoteInstall\SMSImages\HOK00008\boot.HOK00008.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 8/23/2013 3:27:40 AM 3552 (0x0DE0)
Failed adding image F:\RemoteInstall\SMSImages\HOK00008\boot.HOK00008.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 8/23/2013 3:27:40 AM 3552 (0x0DE0)
Failed to find ADK installation root registry key SMSPXE 8/23/2013 3:27:40 AM 3552 (0x0DE0)

 

Found Image file: F:\RemoteInstall\SMSImages\HOK0000E\boot.HOK0000E.wim
PackageID: HOK0000E
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 8/23/2013 3:27:41 AM 3552 (0x0DE0)
Closing image file F:\RemoteInstall\SMSImages\HOK0000E\boot.HOK0000E.wim SMSPXE 8/23/2013 3:27:41 AM 3552 (0x0DE0)
InstallBootFilesForImage failed. 0x80004005 SMSPXE 8/23/2013 3:27:41 AM 3552 (0x0DE0)
Warning: Failed to copy the needed boot binaries from the boot image F:\RemoteInstall\SMSImages\HOK0000E\boot.HOK0000E.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 8/23/2013 3:27:41 AM 3552 (0x0DE0)
Failed adding image F:\RemoteInstall\SMSImages\HOK0000E\boot.HOK0000E.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 8/23/2013 3:27:41 AM 3552 (0x0DE0)
  • Author

Yes ADK was installed on the site server before we did anything. Also, the exact same boot images are working fine on other servers. As a test I created a new boot image from the Windows ADK boot wim and I'm still getting the exact same results.

  • Author

After trying every fix I could find online I finally opened a case with Microsoft and was told this is a known bug that only affects Server 2008 and not 2008 R2. There is no real fix, but the workaround is to copy the RemoteInstall\SMSTempBootFiles directory from a working DP and then restart the WDS service. This will then populate the SMSBoot directories. This has to be redone any time the boot images are updated.

 

Hopefully this will be resolved in R2.

  • 1 year later...

Hi,

 

i am facing the same issue in Windows server 2008 R2 with Sp1 DP. I have copied the remote install folder from Working DP. But no luck.

 

Failed to find ADK installation root registry key

 

please help me out.

 

 

Regards,

Srinivas.

  • 10 years later...

Be aware that if you install WDS on the 😄 drive, then want to move it to another drive, the smspxe.dll file will remain registered on the 😄 drive. RemoteInstall will not have a folder called SMSBoot.

I had a server where Config Mgr had been deployed to the 😄 drive but was supposed to be on E:. The roles were removed and "NO_SMS_ON_DRIVE.SMS" was put onto the 😄 drive then Config Mgr was redeployed.

There did not seem to be a way to get WDS to install and put SMSBoot into the RemoteInstall folder.

Digging around in the registry I found entries for it on the 😄 drive and edited them to point to the E: drive (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\SMSPXE). 

This resolved the issue. I suspect it will help those who are looking for a solution for an empty SMSBoot folder, too.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.