ConfigMgr Console
Capture Network Settings


Receive notification right in your inbox whenever new content like this is released & sign up for our email list!
We’ll send you the latest updates, how-to’s, and solutions to empower you at every endpoint.
By signing up you agree to our Privacy Policy.
Task Sequence Steps – Capture Network Settings
This post is part of our Task Sequence – Beyond the Docs series.
This page will be quite limited to specifics about the step itself, to see it integrated into OSD, check out the Combination Page. Capture, Apply, Network and Windows Settings
MS Docs
Variables
PowerShell
- Get-CMTSStepCaptureNetworkSettings
- New-CMTSStepCaptureNetworkSettings
- Remove-CMTSStepCaptureNetworkSettings
- Set-CMTSStepCaptureNetworkSettings
I rarely see this get used. Most of the time Workstations use DHCP, have one network card, and don’t require anything special. If it’s a reimage, the machine would be re-joined to domain in the same OU, because the machine object is already there. This I believe would be more useful in Server OSD, and yet at the same time, I never see Servers reimaged in a way that they want to keep the same name and IP information.
I typically only see two spectrums of Server OSD, almost completely manual setup of these settings, or heavily automated where scripts or an automation platform would create all of the variables required to apply network settings and apply to a device object in ConfigMgr.
If you use this step, I’d be interested to hear how you leverage it.
Step

More Task Sequence Steps – Beyond the Docs
Find all of our Task Sequence – Beyond the Docs series posts here.
About Recast Software
1 in 3 organizations using Microsoft Configuration Manager rely on Right Click Tools to surface vulnerabilities and remediate quicker than ever before.
Download Free Tools
Request Pricing