locked
Remote Operating System Deployment RRS feed

  • Question

  • Hi all,

    Im kinda new to SCCM, I have a situation that needs to be handled. So really appreciate if you can give me some hints.

    We are using 1906 in our environment,  single site with 3 DPs (two on-prem and one in AWS). I need to pave the way so computers in our remote branches can be PXE boot and imaged.

    I have all the contents and requirements loaded on all DPs, all the boundary groups setup. (currently working and able to PXE boot on-site close to DP) but when I try to image a computer over the network on remote location, it just sits on looking for content at the very initial steps of PXE booting.

    Our branches are equipped with Meraki network gear and connect with SD-WAN.

    Please advise,

    Thank you,

    Thursday, July 23, 2020 4:33 AM

All replies

  • Hi,

    Thanks for posting in TechNet.

    Based on my experience, you need to configure the IP Helpers correctly. IP Helpers must be configured on the routers if any of the DHCP server, the client computer, or the Configuration Manager server that is running WDS and the PXE-enabled DP are on separate subnets or VLANs. 

    1. IP Helpers are necessary because the PXE request that is generated by the client computer is a broadcast that doesn't travel outside the local subnet or VLAN. If the DHCP server or the WDS/PXE-enabled DP aren't on the same subnet or VLAN as the client computer, they will not see or hear the PXE request broadcast from the client. Therefore, the servers will not respond to the PXE request.

    2. For the scenario that are unable to use IP Helpers, we can deploy both DHCP server and PXE-enabled DP on the remote site.

    For more information, please refer to: Troubleshooting PXE boot issues in Configuration Manager

    Thanks for your time.
     
    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 24, 2020 2:42 AM
  • Hi,

    Hope everything goes well. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 27, 2020 6:11 AM
  • Hi Simon, 

    Thank you for your message and please accept my apologies for the late reply.

    So I have added the next boot server and the file name on Meraki MX-67C DHCP config, once Ive done that now client can download the wim file and install operation system, but as soon as it finish the OS installation it start downloading amdocl12d.dll but half way through this it fails with an error "Task sequence has failed with the error code 0x80070002 in the task sequence step". 

    Ive checked my boundary groups pointing to the right direction. Ive checked the network access account under site distribution setting and that is also setup correctly. Was thinking maybe the network access account doesn't have the sufficient privileges, so Ive test and verified that connection was successful.

    Any thoughts? 

    Many thanks, 

    Moses,  

    Sunday, August 2, 2020 5:57 AM
  • Hi,

    Thanks for your reply.

    1.Can the same task sequence images the same model devices on local site? Check if you have added the correct network drivers to you boot image. Please remember that the NIC driver you add to the boot image must match the version of WinPE and is independent from the OS you are deploying.

    2.Does the smsts.log give us some further information for troubleshooting?

    Thanks for your time.
     
    Best regards,
    Simon

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post. Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 7, 2020 7:53 AM