Apply Network Settings step applying incorrectly

Question

Hi All

I'm having some trouble with the Apply Network Setting step in my OSD Task Sequence.

I'm running Config Mgr 2006 Current Branch. Deploying Server 2019.

I'm deploying Windows server vms in several vlans which have no dhcp configuration. As a result, I use the following process:

1. Before deploying VM, decide which vlan the VM will end up.
2. Provision VM with correct vlan ID on NIC
3. In the task sequence wizard, manually set the static IP, netmask, gateway etc. relative to vlan.
4. In task sequence, i have a "Set Dynamic Variables" step to set a vlanID variable based on the Default Gateway detected at the start of the build.
5. I have an "Apply Network Settings" step for each vlanID (wmi condition set to determine this)

Each Apply Network settings step has the "Add adaptors to specify static IP address and other configuration options" configured to apply a static IP in the required vlan.

I'm using Status Message Queries > All status messages for a specific deployment... to monitor the deployment.
I can see that the TS is skipping the steps which are not relevant (I.e. the vlanid does not match) - which is great!

However, when applying the static ip in the Apply Network settings, it is using the configuration applied to another step, and therefore incorrectly sets the wrong IP address.

Hope the screenshots I've attached illustrate this bug.

Any help/advise would be appreciated.
Thanks

Answer 1

Does anyone know where we report bugs with ConfigMgr? - I'm thinking this might be the best option ... clearly a bug IMO.

I have tried reaching our to Configuration Manager Support via: https://aka.ms/cmcbsupport

• However, this site wants you to pay for reporting an issue. So I won't be using this one. Are there any other avenues?

Thanks

Answer 2

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

1. We can use ipconfig /all command to check if the client get the expected network settings when the issue occurs.
2. It's also recommended to examine the smsts.log on the target system to troubleshoot the task sequence error. Please refer to:
   SCCM: How to copy SMSTS.log when a Task Sequence fails

Thanks for your time.

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Thanks Simon

So indeed - I've confirmed that the vm builds with the incorrect IP. I.e. It builds with the adaptor setting configured for vlan12 (this is associated with a completely different step) - see attached images.

The smsts.log log also confirms that the incorrect adaptor settings (for vlan12) are being applied on the vlan11 step.

Any other help out there?

Thanks

Answer 4

Did you resolve this by any chance?

I'm experiencing what appears to be this exact same issue with multiple static IP assignments in a task sequence. The SMSTS log file shows the query for the expected step evaluate to true, then running the network configuration with osdnetworksettings.exe, but it logs and configures the IP from a completely different and later step. When the TS reaches this later step, the log shows the query resolving to false.

Thanks,

Answer 5

Thanks @Stephen Dent

No. Not resolved yet - I'm hoping a guru would call in here to let me know I'm doing something wrong.

I believe this is the same issue - I think you probably did a better job of explaining it.

Cheers