Capturing W2K3 Server .WIM image -- WinPE rebooting without displaying error message!!!
I created a TS where I boot the server using a WinPE boot image (x86) and create a .WIM image from this server (Server 2003 installed on basic disk created on a LSI Logic SAS SCSI RAID Controller), and before getting anything done at the WinPE screen (after SCCM WinPE splash & Initializing devices), the server reboot!
I created a driver packages which contian the LSI Logic SAS SCSI RAID Controller, and injected them to the WinPE image, but without success, the server still reboot.
I tried to find anything logged into SMS, but without success, correct me if I'm wrong, the advertisement should have status messages populated for each step??? Under Advertisement status, I'm getting nothing!
Where I should look to find out what's going wrong with my WinPE boot Task Sequence?
Thanks.
Claude Lachapelle
Systems Administrator, MCSE
Answers
Finally I got it!
On the Broadcom site, I found:
IMPORTANT: PLEASE READ BELOW
Due to limitations in Microsoft's operating systems not supporting the Virtual Bus Device architecture of the NetXtreme II adapter under certain circumstances, separate drivers were created to address these limitations. The NetXtreme II monolithic "RIS" driver allows the adapter to behave similarly to standard network adapters and only provides network connectivity without the advanced offerings of the device. The monolithic driver should be used for connectivity during the text mode portion of a RIS installation (by placing in the I386 or AMD64 platform directory), in a Windows Preinstallation Environment (Windows PE), and for the agent used for Microsoft's Automated Deployment Services (ADS).As soon as I used the appropriate SPECIFIC driver, the WinPE network connections has been established... beautiful!
Problem solved!
Thanks.
Claude Lachapelle
Systems Administrator, MCSE
All Replies
the most likely scenario is that you have not added the required Network drivers to the boot image.
The TS environment reboots because it failed to access any required servers and no messages are returned to the CCM server because there is no network connectivity.
Effectively, WinPE is rebooting itself just after displaying "Establishing network connections" (window that appear and disappear very fastly!).
This said, I added the required x64 NIC drivers to the x64 WinPE image, but I'm still getting the same problem...
Still looking for a solution, but we are looking in the right direction.
Thanks.
Claude Lachapelle
Systems Administrator, MCSE
Finally I got it!
On the Broadcom site, I found:
IMPORTANT: PLEASE READ BELOW
Due to limitations in Microsoft's operating systems not supporting the Virtual Bus Device architecture of the NetXtreme II adapter under certain circumstances, separate drivers were created to address these limitations. The NetXtreme II monolithic "RIS" driver allows the adapter to behave similarly to standard network adapters and only provides network connectivity without the advanced offerings of the device. The monolithic driver should be used for connectivity during the text mode portion of a RIS installation (by placing in the I386 or AMD64 platform directory), in a Windows Preinstallation Environment (Windows PE), and for the agent used for Microsoft's Automated Deployment Services (ADS).As soon as I used the appropriate SPECIFIC driver, the WinPE network connections has been established... beautiful!
Problem solved!
Thanks.
Claude Lachapelle
Systems Administrator, MCSE
