Before rebooting into winPE, SCCM client captures current network adapter settings to apply them in winPE environment. How can I prevent this?

adam t 6 Reputation points
2021-06-14T19:17:14.667+00:00

When PXE booting, or booting from removable media, this isn't necessary, and so it isn't necessary when triggering an OSD deployment from software center either. Yet, as part of no task step, the client captures network settings, and applies them as the task resumes from winPE.

This is causing a problem where there is no name resolution due to software controlled DNS settings in the full OS. They get copied to winPE and cause the task to fail. I've tried a couple workarounds, but they have issues and it seems like it shouldn't be necessary to correct something like this.

In the logs it even says (paraphrasing) capture adapters:true, as if the true can be changed to false somewhere. I've tried to do through through task sequence variables with no luck, as I believe they only affect actual capture or apply network settings steps. I have also tried to add such steps. Nothing hacky has worked.

Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,021 questions
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
901 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Colin Ford 1,026 Reputation points
    2021-06-14T20:28:06.53+00:00

    I'm not sure 100% sure this will work, but try set the task sequence variable OSDMigrateAdapterSettings to False in the OS portion of the task sequence before it boots into WinPE.

  2. Jason Sandys 31,151 Reputation points Microsoft Employee
    2021-06-14T21:27:44.417+00:00

    To validate, is there a Capture Network Settings task in the TS?

  3. Colin Ford 1,026 Reputation points
    2021-06-14T23:55:16.68+00:00

    I'm not sure how to fix the 'properly' and disable that behavior. However, could you try running this command in WinPE and see if it switches the interface back to DHCP? 

    netsh int ip set address Ethernet dhcp

    If this works, you could try to include that as a pre-start command in WinPe to switch the interface back to DHCP before the task sequence has started.

  4. Jason Sandys 31,151 Reputation points Microsoft Employee
    2021-06-15T13:48:52.45+00:00

    Can you expand on what "software controlled DNS settings" is exactly here?

  5. Colin Ford 1,026 Reputation points
    2021-06-15T22:10:38.957+00:00

    You may need to get creative with workaround rather than finding a perfect solution, as that may just not be possible. Can you remove the umbrella client prior to reboot?

    0 comments