Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Code 84 when running task sequence OSD

smurray

Member
Messages
6
Reaction score
0
Points
1
DNS settings are not being transferred into WinPE.

The environment has statically assign IP's and DNS servers. Task sequence OSD is proven to work in the environment but recently has hit a snag with more Code 84 errors.

Error code snippet:
Adapter with MACAddress '5c:60:ba:33:36:5f' is not connected, ignoring that there is no network connectivity yet in WinPE and applying adapter settings. TSBootShell 2/9/2026 6:22:32 PM 1784 (0x06F8)
If ultimately there is still no network connectivity when program proceeds, then delays/retries further along will kick in. TSBootShell 2/9/2026 6:22:32 PM 1784 (0x06F8)
uRetVal == 0 || uRetVal == 1, HRESULT=80004005 (F:\dbs\sh\cmgm\0926_074307\cmd\c\src\Framework\OSDCore\netwmiadapterconfig.cpp,1060) TSBootShell 2/9/2026 6:22:32 PM 1784 (0x06F8)
Win32_NetworkAdapterConfiguration::SetDNSServerSearchOrder failed (Code 84) TSBootShell 2/9/2026 6:22:32 PM 1784 (0x06F8)
Failed to set DNS settings for adapter (0x80004005) TSBootShell 2/9/2026 6:22:32 PM 1784 (0x06F8)



Things I have tried:
1. Manually capturing the settings with this script: https://gist.github.com/Recast-team/c76fce8ba772d0319befd416b761cea9
2. Multiple Microsoft tickets
 
does this mac address 5c:60:ba:33:36:5f belong to the correct NIC? Just wondering if the step is querying the wless adapter by mistake?
yes, that mac address is the correct NIC. It's weird that it says its not connected because the NIC is in use at the time the task seqeunce starts. It transfers the IP, subnet mask, and gateway correctly. DNS servers are the only thing having issues setting correctly
 
OK, what I have done in the past for similar situations is disable ipv6 on you boot wim and redistribute. Or set some variables before the capture to disable it.
 
OK, what I have done in the past for similar situations is disable ipv6 on you boot wim and redistribute. Or set some variables before the capture to disable it.
I disabled IPv6 in the boot wim and confirmed by remounting and running a reg query. What variables did you use to disable it?
 
OSDAdapter0DNSServerList
Value = your dns server ipv4 address

OSDAdapter0DNSDomain
Value = your domain name
I tried a variation of this with the following script:

$NetworkInfo = Get-CimInstance Win32_NetworkAdapterConfiguration | Where-Object {$_.DHCPEnabled -eq $false}
#Setup TS Environment
try
{
$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
}
catch
{
Write-Verbose "Not running in a task sequence."
}
$tsenv.value('OSDAdapter0IPAddressList') = $NetworkInfo.IPAddress[0]
$tsenv.value('OSDAdapter0SubnetMask') = $NetworkInfo.IPSubnet[0]
$tsenv.value('OSDAdapter0Gateways') = $NetworkInfo.DefaultIPGateway[0]
$tsenv.value('OSDAdapter0DNSServerList') = $NetworkInfo.DNSServerSearchOrder[0]
$tsenv.value('OSDAdapter0DNSSuffix') = $NetworkInfo.DNSDomainSuffixSearchOrder[0]
if ($NetworkInfo.DHCPEnabled -eq $false)
{
$tsenv.value('OSDAdapterCount') = 1
$tsenv.value('OSDAdapter0EnableDHCP') = $false
}
else {$tsenv.value('OSDAdapter0EnableDHCP') = $true}




Its missing the OSDAdapter0DNSDomain but manually capturing the network variables did not help either
 

Forum statistics

Threads
7,186
Messages
28,048
Members
18,326
Latest member
landry

Trending content

Back
Top