Tallbearblue81
asked on
SCCM2007 Image Capture failing with error code 0x800704CF
Whenever I try to capture an OSD image from a reference machine, after the sysprep is run from the capture disk, and the system reboots into WindowsPE, the image capture process fails with error code 0x800704CF. I have made sure that the machine can access the share on the SCCM site server that the capture image is written to - I shared the directory to everyone for troubleshooting purposes. I also checked and the local admin password is not set on the reference machine. What else could cause this issue?
raeldri
What do the SMSTS Logs show? it's possible when the machine boots to Win PE it no longer has a driver for the network card to write the image back across the network
ASKER
I am able to PXE boot to WinPE with the same model machine, so this shouldn't be a driver issue, right? I attached the smsts.log for review.
smsts.log
smsts.log
If you scroll back from the end of the log you see it failing to connect to \\sccm\f$\capture and even further back time stamp 2/16/2012 9:12:56AM you'll see the message.
No valid network adapter found.
littler further back in the log you see the following
it looks like its finding a card and possible not able to find an IP via DHCP? is DHCP funtioning in your network if not you'll need to configure the network card as part of your build and capture task sequence
No valid network adapter found.
littler further back in the log you see the following
==============================[ TSBootShell.exe ]============================== TSBootShell 2/16/2012 9:12:43 AM 768 (0x0300)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSBootShell 2/16/2012 9:12:43 AM 768 (0x0300)
Waiting for PNP initialization... TSBootShell 2/16/2012 9:12:43 AM 776 (0x0308)
Booted from fixed disk TSBootShell 2/16/2012 9:12:43 AM 776 (0x0308)
!sVolumeID.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467) TSBootShell 2/16/2012 9:12:43 AM 776 (0x0308)
Found config path D:\_SMSTaskSequence TSBootShell 2/16/2012 9:12:43 AM 776 (0x0308)
Restoring boot system from D:\_SMSTaskSequence\backup TSBootShell 2/16/2012 9:12:43 AM 776 (0x0308)
Successfully loaded the BCD boot system TSBootShell 2/16/2012 9:12:48 AM 776 (0x0308)
Successfully loaded an exported BCD boot system TSBootShell 2/16/2012 9:12:48 AM 776 (0x0308)
Successfully merged logs from cache. TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Loading saved WinPE settings TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Environment scope "Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}" successfully created TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Configuring WinPE bootstrap settings TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Creating WinPE answer file TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Setting hive location to "X:\windows\system32" TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86" TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Configuring global network settings TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Join type: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
DNS domain: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
DNS domain search order: company.int TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
IP filter sec enabled: false TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Configuring 1 of 1 network adapters TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Configuring DHCP TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
DNS suffix: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
DNS server search order: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
DNS registration enabled: false TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Full DNS registration enabled: true TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Permitted IP protocols: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Permitted TCP ports: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Permitted UDP ports: TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Tcpip Netbios options: 0 TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Enable WINS: false TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
WINS server(s): TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
MAC address: 2c:27:d7:40:1c:a0 TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Adapter index: 0 TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Adapter name: Local Area Connection TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Getting namespace "Microsoft-Windows-TCPIP" for architecture "x86" TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Added list item with key value '2c-27-d7-40-1c-a0' TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Writing configuration information to D:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Successfully saved configuration information to D:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
Executing command line: wpeinit.exe -winpe TSBootShell 2/16/2012 9:12:52 AM 776 (0x0308)
The command completed successfully. TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Starting DNS client service. TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Finalizing network settings TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Finalizing global network settings TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS domain: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS domain search order: company.int TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS for WINS enabled: false TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
LMHosts file enabled: true TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Host lookup file: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
WINS scope ID: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Finalizing 1 of 1 network adapters TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Configuring DHCP TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS suffix: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS server search order: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
DNS registration enabled: false TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Full DNS registration enabled: true TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Permitted IP protocols: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Permitted TCP ports: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Permitted UDP ports: TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Tcpip Netbios options: 0 TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Enable WINS: false TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
WINS server(s): TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
MAC address: 2c:27:d7:40:1c:a0 TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Adapter index: 0 TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Adapter name: Local Area Connection TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdcore\netwmiadapterconfig.cpp,126) TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Unable to find Win32_NetworkAdapter where MACAddress = "2c:27:d7:40:1c:a0" TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
pAdapter->FindAdapter( pszPropertyName, pszPropertyValue ), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdcore\netwmiadapterconfig.cpp,64) TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Unable to find adapter during finalization TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:D:\_SMSTaskSequence TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
The command completed successfully. TSBootShell 2/16/2012 9:12:56 AM 776 (0x0308)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 2/16/2012 9:12:56 AM 1656 (0x0678)it looks like its finding a card and possible not able to find an IP via DHCP? is DHCP funtioning in your network if not you'll need to configure the network card as part of your build and capture task sequence
ASKER
DHCP is functioning on the network. Could it be a storage driver perhaps?
Most certinaly its a network related issue. in the log it shows a mac address is this the correct address for the card in question?
2c:27:d7:40:1c:a0
2c:27:d7:40:1c:a0
ASKER
Yes, that is the correct MAC address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The issue was the boot disk needed to be recreated with the new drivers that were injected for the machine.