Answered by:
32bit windows 7 deployment

Question
-
I am trying to deploy win7 x32 on a HP DC7100 SFF PC. Instaling from DVD works fine.
I have created my OS deployment Image, a TS, deployed the TS to a collection and imported the PC via mac into the collection. I have also installed the NIC driver into the Boot Image (x86). When I try to install the image to the PC it getting to the SCCM screen but never give the option to select the TS I've made available.
I have looked in the smspxe.log file and it says there is no TS available which there is. I have also looked on the client in the wpeinit.log which says, if I am reading right "WaitForNetworkToInitialize failed" and the computer just reboots. I dont have the problem when installing x64 images. I have also updated the boot images which was successful
Can anyone help by point me in the right direction. I no its the correct nic drivers because it works when I install windows via CDThanks
Wayne
2014-05-08 16:02:22.184, Info No unattend file was found; WPEINIT is using default settings to initialize WinPE
2014-05-08 16:02:22.184, Info Spent 1265ms initializing removable media before unattend search
2014-05-08 16:02:22.216, Info ==== Initializing Display Settings ====
2014-05-08 16:02:22.216, Info No display settings specified
2014-05-08 16:02:22.216, Info STATUS: SUCCESS (0x00000001)
2014-05-08 16:02:22.216, Info ==== Initializing Computer Name ====
2014-05-08 16:02:22.216, Info Generating a random computer name
2014-05-08 16:02:22.216, Info No computer name specified, generating a random name.
2014-05-08 16:02:22.216, Info Renaming computer to MININT-22SICP4.
2014-05-08 16:02:22.216, Info Waiting on the profiling mutex handle
2014-05-08 16:02:22.216, Info Acquired profiling mutex
2014-05-08 16:02:22.216, Info Service winmgmt disable: 0x00000000
2014-05-08 16:02:22.216, Info Service winmgmt stop: 0x00000000
2014-05-08 16:02:22.247, Info Service winmgmt enable: 0x00000000
2014-05-08 16:02:22.247, Info Released profiling mutex
2014-05-08 16:02:22.247, Info STATUS: SUCCESS (0x00000000)
2014-05-08 16:02:22.247, Info ==== Initializing Virtual Memory Paging File ====
2014-05-08 16:02:22.247, Info No WinPE page file setting specified
2014-05-08 16:02:22.247, Info STATUS: SUCCESS (0x00000001)
2014-05-08 16:02:22.247, Info ==== Initializing Optional Components ====
2014-05-08 16:02:22.247, Info WinPE optional component 'Microsoft-WinPE-WMI' is present
2014-05-08 16:02:22.294, Info WinPE optional component 'Microsoft-WinPE-WSH' is present
2014-05-08 16:02:22.309, Info STATUS: SUCCESS (0x00000000)
2014-05-08 16:02:22.325, Info ==== Initializing Network Access and Applying Configuration ====
2014-05-08 16:02:22.325, Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
2014-05-08 16:02:22.325, Info Global handle for profiling mutex is non-null
2014-05-08 16:02:22.325, Info Waiting on the profiling mutex handle
2014-05-08 16:02:22.325, Info Acquired profiling mutex
2014-05-08 16:02:22.903, Info Install MS_MSCLIENT: 0x00000000
2014-05-08 16:02:22.903, Info Install MS_NETBIOS: 0x00000000
2014-05-08 16:02:23.075, Info Install MS_SMB: 0x00000000
2014-05-08 16:02:23.294, Info Install MS_TCPIP6: 0x00000000
2014-05-08 16:02:24.013, Info Install MS_TCPIP: 0x00000000
2014-05-08 16:02:24.013, Info Service dhcp start: 0x00000000
2014-05-08 16:02:24.013, Info Service lmhosts start: 0x00000000
2014-05-08 16:02:24.184, Info Service ikeext start: 0x00000000
2014-05-08 16:02:24.309, Info Service mpssvc start: 0x00000000
2014-05-08 16:02:24.309, Info Released profiling mutex
2014-05-08 16:02:24.309, Info Spent 1985ms installing network components
2014-05-08 16:02:25.059, Info Installing device root\kdnic X:\WINDOWS\INF\kdnic.inf succeeded
2014-05-08 16:02:34.606, Info Installing device pci\ven_14e4&dev_1677&subsys_3006103c X:\WINDOWS\INF\oem0.inf succeeded
2014-05-08 16:02:34.903, Info Spent 10593ms installing network drivers
2014-05-08 16:02:35.044, Error QueryAdapterStatus: no adapters found.
2014-05-08 16:02:35.044, Info Spent 16ms confirming network initialization; status 0x80004005
2014-05-08 16:02:35.044, Info WaitForNetworkToInitialize failed; ignoring error
2014-05-08 16:02:35.044, Info STATUS: SUCCESS (0x003d0001)
2014-05-08 16:02:35.044, Info ==== Applying Firewall Settings ====
2014-05-08 16:02:35.044, Info STATUS: SUCCESS (0x00000001)
2014-05-08 16:02:35.044, Info ==== Executing Synchronous User-Provided Commands ====
2014-05-08 16:02:35.044, Info STATUS: SUCCESS (0x00000001)
2014-05-08 16:02:35.044, Info ==== Executing Asynchronous User-Provided Commands ====
2014-05-08 16:02:35.044, Info STATUS: SUCCESS (0x00000001)
2014-05-08 16:02:35.044, Info ==== Applying Shutdown Settings ====
2014-05-08 16:02:35.044, Info No shutdown setting was specified
2014-05-08 16:02:35.044, Info STATUS: SUCCESS (0x00000001)
Thursday, May 8, 2014 3:36 PM
Answers
-
Thank you for your replies. I resolved the issue. I injected the updated NIC driver into the boot images which I did not need to do, once removed it all worked fine
w
- Marked as answer by wmb37 Friday, May 9, 2014 7:17 AM
Friday, May 9, 2014 7:16 AM
All replies
-
What does smsts.log tell? Have you got in IP address when running PE? What does smspxe.log tell?
Torsten Meringer | http://www.mssccmfaq.de
Thursday, May 8, 2014 5:13 PM -
It Looks like there are no Network Adapters recognized.
Spent 10593ms installing network drivers
2014-05-08 16:02:35.044, Error QueryAdapterStatus: no adapters found.
2014-05-08 16:02:35.044, Info Spent 16ms confirming network initialization; status 0x80004005This means you have to Import the Network Card Driver to WinPE. The following blog post describes how to find the relevant Drivers and how to Import them. http://www.adamfowlerit.com/2013/10/08/troubleshooting-nic-drivers-in-winpe-for-sccm-2012/
Cheers,
Thomas Kurth
Netree AG, System Engineer
Blog:http://netecm.netree.ch/blog | Twitter:
| LinkedIn:
| Xing:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.- Proposed as answer by Joyce L Friday, May 9, 2014 3:02 AM
Thursday, May 8, 2014 9:43 PM -
Thank you for your replies. I resolved the issue. I injected the updated NIC driver into the boot images which I did not need to do, once removed it all worked fine
w
- Marked as answer by wmb37 Friday, May 9, 2014 7:17 AM
Friday, May 9, 2014 7:16 AM