Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Add delay/retry option in the "Apply Network Settings" step in the Task Sequence.

With all of the new USB type NIC dongles needed to image devices, I've run into issues with some devices not joining the domain because the internal NIC didn't initialized in time. I know there's a "Join Domain or Workgroup" step you could add but it would be easier if the retry/delay could be included in the "Apply Network Settings" step versus having to create another group/step as a backup. Or even creating a TS variable that could be adjusted in the TS similar to SMSTSDownloadRetryCount & Delay.

3 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Yuri Van Dierendonck shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Frank Rojas commented  ·   ·  Flag as inappropriate

    This request doesn't make sense. All the Apply Network Settings task does is add the domain join information to the Unattend file. It does not actually join the domain. Windows Setup is the one that actually joins the domain via the settings in the Unattend file. There is actually no ConfigMgr components running when the domain join happens during the Windows Setup, so there is no way for ConfigMgr to "retry". If ConfigMgr "retried" during the Apply Network Settings task, all it would be doing is readding the domain join information to the Unattend file. You allude to what the actual solution is which is to use a Join Domain or Workgroup task right after the Setup Windows and ConfigMgr task which has a condition that it will only run if the device is not domain joined.

Feedback and Knowledge Base