none
SCCM 2012 PXE Process Failing

    Question

  • Hi guys, having an issue at the moment with PXE

    PXE has been configured, WDS role installed on the distribution point and IP helpers have been configured on the routers to point to our two DHCP servers and our PXE server ( DHCP server and PXE server are on different servers in different subnets)

    When a PXE client attempts to PXE boot no DHCP address is given and we recieve E-53 no boot filename recieved. My understanding is that we should still recieve a DHCP address regardless of PXE configuration in SCCM. Is that the case?

    All sites will use one distribution point with PXE enabled (accross WAN)

    I have noticed on my boot images I did not have "Deploy this boot image from the PXE service point" ticked. Could this be causing my issue?

    Any ideas as to what this could be or wjhich logs I can examine?

    Thanks

    Monday, August 27, 2012 10:55 PM

Answers

  • Hi guys, had to log a support ticket for this issue that we had. Issue now resolved

    Initial Issue Description:

    After enabling PXE on one of our distribution points (this is also the site server and management point) and setting the following on our MDT boot images as per screenshot below we are unable to distribute the boot image to the distribution point. This is stuck in “In progress”

    Initial troubleshooting steps performed

    * removed the DP role
    * removed the WDS role from WSLDCTSCCM (which wasn't removed automatically for an unknown reason) (site server & DP)
    * rebooted the server
    * deleted SMSPKG$, SMSPKGx$, SMSPKGSIG, SMSSIG$, SCCMContentLib, RemoteInstall folders on all drives
    * verified no_sms_on_drive.sms files on appropriate drives
    * reconfigured the DP with PXE option

    Copying package P0100102 to the package share location \\WSLDCTSCCM.water.internal\SMSPKGF$\P0100102 on the server ["Display=\\WSLDCTSCCM.water.internal\"]MSWNET:["SMS_SITE=P01"]\\WSLDCTSCCM.water.internal\            SMS_DISTRIBUTION_MANAGER           29/08/2012 1:08:12 p.m. 2000 (0x07D0)

    CContentDefinition::GetFileProperties failed; 0x80070003         SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    CContentDefinition::CopyFileA failed; 0x80070003        SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.            2000 (0x07D0)

    CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    Failed to expand package P0100102 to \\?\F:\SMSPKGF$\P0100102. Error code = 0x80070003            SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.            2000 (0x07D0)

    Error occurred. Performing error cleanup prior to returning.   SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    Analysis and solution:

    -          For the CContentDefinition::GetFileProperties failed; 0x80070003       

    We found that there are package folders on other driver. So we back up and remove the SMSPKG* folders, SMSSIG, SCCMContentLib from all drives when removing DP.

    -          After the DP reinstallation, the above error was gone, but:

    \\?\E:\SMSPKGSIG\P010024A.3 could not be located     SMS_DISTRIBUTION_MANAGER               8/29/2012 4:51:07 PM         3740 (0x0E9C)

    Failed to get RDC signature path for for package P010024A version 3. Error = 2    SMS_DISTRIBUTION_MANAGER                8/29/2012 4:51:07 PM 3740 (0x0E9C)

    Or

    Copying content signatures for package P01000A2          SMS_DISTRIBUTION_MANAGER               8/29/2012 4:46:03 PM         4596 (0x11F4)

    RDC:Failed to copy package content signature file \\?\E:\SMSPKGSIG\Content_56622ff5-0f6d-4be0-8dc8-8bb928302abe.1.tar to \\WSLDCTSCCM.water.internal\SMSSIG$\Content_56622ff5-0f6d-4be0-8dc8-8bb928302abe.1.tar. Error 3      SMS_DISTRIBUTION_MANAGER               8/29/2012 4:46:03 PM 4596 (0x11F4)

    Per my code review, the SMSPKGSIG folder is a must for distmgr once it’s created that can’t be removed or changed.

    After your creating the new applications and package, the SMSPKGSIG folder was created on D: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER\Signature Manager\SignatureRepository

    So we copied the previous files under SMSPKGSIG folder to the current D:\SMSPKGSIG. This resolved the above error.

    -          The package downloading failed on client though it was installed in DP showing in the SCCM console:

    Sending location services HTTP failure message. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    Successfully sent location services HTTP failure message. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    Error sending DAV request. HTTP code 404, status 'Not Found' DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    GetDirectoryList_HTTP('http://WSLDCTSCCM.water.internal:80/SMS_DP_SMSPKG$/P0100204') failed with code 0x87d0027e. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    We find there is no 'http://WSLDCTSCCM.water.internal:80/SMS_DP_SMSPKG$/P0100204'

    The package files were not there under the SCCMContentLib.

    Tried package redistribute, success in distmgr.log, but still no entries under SCCMContentLib.

    Tried to delete and re-add the package, still the same.

    The affected ContentLib is on our only SCCM site server:

    The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 30/08/2012 3:44:47 p.m. 9152 (0x23C0)

    So we copy the SCCMContentLib from remote DP server.

      •        Back up the F:\SCCMContentLib on the SCCM site server WSLDCTSCCM.<u5:p></u5:p>
      •        Copy the files under SCCMContentLib from other working remote DP to the SCCM site server WSLDCTSCCM’s F:\SCCMContentLib. Don’t replace existing files.<u5:p></u5:p>
      •        Re-distribute one test package.<u5:p></u5:p>
      •        Check the package downloading on clients are good.<u5:p></u5:p>

    Based on the above information, I suggest to back up the SCCMContentLib and SMSPKGSIG on the your primary site server.

    • Marked as answer by nickm34 Sunday, September 16, 2012 11:49 PM
    Sunday, September 16, 2012 11:48 PM

All replies

  • I have attempted to tick this option on my x86 and x64 MDT boot images "Deploy this boot image from the PXE service point" and distribute to my DP which hosts PXE services and content will not distribute correctly. It is stuck "In Progress". When I look at my distmgr.log file I receive the following lines:

    ExpandPXEImage: P0100103, 1024 SMS_DISTRIBUTION_MANAGER 28/08/2012 11:22:19 a.m. 6472 (0x1948)

    Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 28/08/2012 11:22:19 a.m. 6472 (0x1948)

    Monday, August 27, 2012 11:32 PM
  • Yes, not having your boot images deployed to PXE will cause the issue you've described.

    Need more than just those two lines from the log file to help though.

    Also, is your DP even healthy? Can you deploy any packages to the DP?


    Jason | http://blog.configmgrftw.com

    Tuesday, August 28, 2012 1:08 AM
  • Hi Jason, yep DP is healthy and can deploy other packages fine.

    I have added standard boot images to be available to the PXE distribution point just fine (not in custom source location). So now this MDT boot image distribution issue is a secondary issue which I will be able to resolve. When PXE booting now I recieve a DHCP address but request is stuck on contacting server the eventually comes up with the following message


    TFTP Download: smsboot\x64\abortpxe.com
    PXE Boot aborted. Booting to next device...

    All I can see in SMSPXE.log is the following types of messages

    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778393" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778393" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    Set media certificate in transport SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Set authenticator in transport SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Set media certificate in transport SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    Set authenticator in transport SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    Set authenticator in transport SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Set authenticator in transport SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778393" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
     SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Client Identity: 21d4f712-39cf-45ab-a0db-b64a1929cac6 SMSPXE 28/08/2012 12:13:15 p.m. 1536 (0x0600)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778393" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
     SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)
    Client Identity: 21d4f712-39cf-45ab-a0db-b64a1929cac6 SMSPXE 28/08/2012 12:13:15 p.m. 6868 (0x1AD4)

    Looking at the following post http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

    This mentions that possibly this is an issue with task sequence deployments. I have all of my task sequences deployed as "available" to "all unknown computers" with the following option set "make available to boot media and PXE". So not really sure what to check next

    Tuesday, August 28, 2012 1:17 AM
  • Based upon the above log though, the client not unknown.

    Is this a new system? If so, it's possible an "unknown" resource was created making it now know. You should check the All Systems collection "Unknown" resources.


    Jason | http://blog.configmgrftw.com

    Tuesday, August 28, 2012 1:31 AM
  • Hi Jason, client was a built machine. I attempted deleting the SCCM record so it would be unknown. After doing that I still recieve this message. Also I let it rediscover this computer object and then added to a required task sequence but still the same

    Tuesday, August 28, 2012 1:56 AM
  • When booting now it is looking for the original MDT boot image but cant find it. So think I should concentrate on resolving the original distribution issue

    It seems to only be when attempting to distribute the MDT boot image on my DP that is also my management point (installs fine on other DPs which do actually have WDS installed)

    Tuesday, August 28, 2012 4:40 AM
  • I attempted deleting the SCCM record so it would be unknown. After doing that I still recieve this message. Also I let it rediscover this computer object and then added to a required task sequence but still the same


    That will not work. An AD system discovery record is not sufficient for a PXE boot, because it does not contain the MAC address or SMBIOSGUID. One of those attributes is needed to identify the client that's PXE-booting.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, August 28, 2012 7:16 AM
  • Hi Torsten, what I meant was it rediscovered the computer object but also the Windows 7 machine was turned on so the client reported back hardware information such as MAC address, SMSBIOSGUID etc and was seen as an active client in the console
    Tuesday, August 28, 2012 11:05 AM
  • Problem solved. Logged premier suppor ticket so will repost with the solution to this issue
    Friday, August 31, 2012 3:59 AM
  • Hi guys, had to log a support ticket for this issue that we had. Issue now resolved

    Initial Issue Description:

    After enabling PXE on one of our distribution points (this is also the site server and management point) and setting the following on our MDT boot images as per screenshot below we are unable to distribute the boot image to the distribution point. This is stuck in “In progress”

    Initial troubleshooting steps performed

    * removed the DP role
    * removed the WDS role from WSLDCTSCCM (which wasn't removed automatically for an unknown reason) (site server & DP)
    * rebooted the server
    * deleted SMSPKG$, SMSPKGx$, SMSPKGSIG, SMSSIG$, SCCMContentLib, RemoteInstall folders on all drives
    * verified no_sms_on_drive.sms files on appropriate drives
    * reconfigured the DP with PXE option

    Copying package P0100102 to the package share location \\WSLDCTSCCM.water.internal\SMSPKGF$\P0100102 on the server ["Display=\\WSLDCTSCCM.water.internal\"]MSWNET:["SMS_SITE=P01"]\\WSLDCTSCCM.water.internal\            SMS_DISTRIBUTION_MANAGER           29/08/2012 1:08:12 p.m. 2000 (0x07D0)

    CContentDefinition::GetFileProperties failed; 0x80070003         SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    CContentDefinition::CopyFileA failed; 0x80070003        SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.            2000 (0x07D0)

    CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    Failed to expand package P0100102 to \\?\F:\SMSPKGF$\P0100102. Error code = 0x80070003            SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.            2000 (0x07D0)

    Error occurred. Performing error cleanup prior to returning.   SMS_DISTRIBUTION_MANAGER          29/08/2012 1:08:12 p.m.     2000 (0x07D0)

    Analysis and solution:

    -          For the CContentDefinition::GetFileProperties failed; 0x80070003       

    We found that there are package folders on other driver. So we back up and remove the SMSPKG* folders, SMSSIG, SCCMContentLib from all drives when removing DP.

    -          After the DP reinstallation, the above error was gone, but:

    \\?\E:\SMSPKGSIG\P010024A.3 could not be located     SMS_DISTRIBUTION_MANAGER               8/29/2012 4:51:07 PM         3740 (0x0E9C)

    Failed to get RDC signature path for for package P010024A version 3. Error = 2    SMS_DISTRIBUTION_MANAGER                8/29/2012 4:51:07 PM 3740 (0x0E9C)

    Or

    Copying content signatures for package P01000A2          SMS_DISTRIBUTION_MANAGER               8/29/2012 4:46:03 PM         4596 (0x11F4)

    RDC:Failed to copy package content signature file \\?\E:\SMSPKGSIG\Content_56622ff5-0f6d-4be0-8dc8-8bb928302abe.1.tar to \\WSLDCTSCCM.water.internal\SMSSIG$\Content_56622ff5-0f6d-4be0-8dc8-8bb928302abe.1.tar. Error 3      SMS_DISTRIBUTION_MANAGER               8/29/2012 4:46:03 PM 4596 (0x11F4)

    Per my code review, the SMSPKGSIG folder is a must for distmgr once it’s created that can’t be removed or changed.

    After your creating the new applications and package, the SMSPKGSIG folder was created on D: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER\Signature Manager\SignatureRepository

    So we copied the previous files under SMSPKGSIG folder to the current D:\SMSPKGSIG. This resolved the above error.

    -          The package downloading failed on client though it was installed in DP showing in the SCCM console:

    Sending location services HTTP failure message. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    Successfully sent location services HTTP failure message. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    Error sending DAV request. HTTP code 404, status 'Not Found' DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    GetDirectoryList_HTTP('http://WSLDCTSCCM.water.internal:80/SMS_DP_SMSPKG$/P0100204') failed with code 0x87d0027e. DataTransferService 8/30/2012 9:54:15 AM 6288 (0x1890)

    We find there is no 'http://WSLDCTSCCM.water.internal:80/SMS_DP_SMSPKG$/P0100204'

    The package files were not there under the SCCMContentLib.

    Tried package redistribute, success in distmgr.log, but still no entries under SCCMContentLib.

    Tried to delete and re-add the package, still the same.

    The affected ContentLib is on our only SCCM site server:

    The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 30/08/2012 3:44:47 p.m. 9152 (0x23C0)

    So we copy the SCCMContentLib from remote DP server.

      •        Back up the F:\SCCMContentLib on the SCCM site server WSLDCTSCCM.<u5:p></u5:p>
      •        Copy the files under SCCMContentLib from other working remote DP to the SCCM site server WSLDCTSCCM’s F:\SCCMContentLib. Don’t replace existing files.<u5:p></u5:p>
      •        Re-distribute one test package.<u5:p></u5:p>
      •        Check the package downloading on clients are good.<u5:p></u5:p>

    Based on the above information, I suggest to back up the SCCMContentLib and SMSPKGSIG on the your primary site server.

    • Marked as answer by nickm34 Sunday, September 16, 2012 11:49 PM
    Sunday, September 16, 2012 11:48 PM