Re: OSD/PE05 Ramboot via RIS freezes systems everytime
- From: "JayBee" <jason.benedicic@xxxxxxxxx>
- Date: Mon, 24 Apr 2006 16:08:20 +0100
We recently had a very similar problem with booting OSD from RIS. We don't
use Ramdisks but the error was the same.
All of our machines use either BroadCom or Intel NIC's. I found an article
on the Intel website related to a RIS booting issue. I followed thier advice
and removed the drivers that we're build into Windows/WinPE. This forced the
system to use the drivers that I provide as opposed to the existing ones.
Sorry I can't explain in greater detail, I tried so many things over that
week as I was pulling my hair out and only managed to get it working by a
stroke of luck (the issues only started when I upgraded my server to R2).
"SMS_Wannabe" <SMSWannabe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F5F9AD5A-EFE2-4D7D-8F95-C5D708B57EDF@xxxxxxxxxxxxxxxx
Just a follow up on this earlier post. I have since realized all 3
systems
we were testing, had the SAME network card (a 3Com 3c905..). We have
tested
on a 4th system that has a broadcom, and everything works fine. So it
appears to be a problem specific to the 3Com NIC's; perhaps an
incompatible
driver? Although I still don't understand why the systems do not freeze
when
they are booted from CD as opposed to RIS?
"SMS_Wannabe" wrote:
We are having problems performing a ramboot from a Windows 2003 RIS
Server.
We have followed some of the great advice offered on this forum, but no
matter what we try, the ramboot freezes at an early stage in the Windows
PE
boot. Here are the details:
1. Windows 2003 R2 SP1 RIS server
2. Created a customized version of Windows PE 2005 using the "config.hta"
utility. For source files we used Windows Server 2003 SP1 files and
Windows
PE 2005 files. To create the customized version, we select the "generic
iso"
option from the config.hta utility
3. We burn the customized version of Windows PE 2005 to a CD and insert
the
CD into the SMS server
4. Using the "image packages" node in the SMS console, we select "Update
Windows PE" and point the wizard to the customized windows PE CD
a. Note: the original OSDSHell has been replaced with OSDshell.lab
5. After the update completes, we create a new Operating System
Installation
CD using the wizard available at the "image packages" node
6. On the ris server we create the following folder structure:
\RemoteInstall\Setup\English\Images\OSD_Install\i386\templates
7. We copy the newly create OSD iso (OSDInstall.iso) to
\RemoteInstall\Setup\English\Images\OSD_Install\i386
8. Then we copy ntdetect.com, startrom.com, and setupldr.exe from the
customized version of Windows PE created in step 2 to the
\OSD_Install\i386\templates directory
9. We rename setupldr.exe to Ntldr
10. We create a text file name Winnt.sif in the templates directory with
the
following text:
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd
/rdpath=%INSTALLPATH%\%MACHINETYPE%\OSDInstall.iso"
Architecture = "i386"
[RemoteInstall]
Repartition = No
[OSChooser]
Description = "OSD Installation"
Help = "OSD Installation"
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType = WinPE
Version = "5.2 (0)"
We have 3 different laptops (2 with 256MB memory, and one with 512MB
memory). All three laptops have different NICs. When we boot using PXE,
select the maintenance option and choose "OSD Installation" things work
initially. The systems all begin the TFTP download of the iso. We have
watched the connections over network monitor on the RIS server and see
all
clients download the 177MB iso image. After downloading the iso into
ram,
the systems begin their PE boot. 2 of the systems (one with 512mb
memory)
freeze while starting Windows PE (they freeze with the "please wait"
message
on the screen and the status bar is almost complete). The third system
actually gets beyond the text-only screens and loads it's shell; however,
soon after the GUI appears, that system freezes also. The system freezes
with an OSD SMS dialog box stating "initializing windows PE." I have
pressed
f8 and in the 30 seconds or so before the freeze, I can tell it does not
have
an IP address yet (I believe it has not loaded the network stack yet).
The OSDshell.log does not seem to have any clues, but I'll gladly post
the
contents if they are useful. We have tried some changes to network card
drivers, Ntldr versions, and new ISOs. But no matter what we try, the
systems
freeze. Without much of an understanding of the ramboot process, it's
difficult to identify the cause of these freezes. It feels like a memory
issue, but I cannot seem to pin anything down. Also we are confused by
the
fact we can take the OSD Install iso and burn it to CD and everything
works
fine. We have also test booting systems to flat XP SP2 and W2k3 SP1
source
files and it works fine. "rambooting" to a windows PE 2005 iso, does not
work however - that test freezes also?
Any help is greatly appreciated.
.
- References:
- OSD/PE05 Ramboot via RIS freezes systems everytime
- From: SMS_Wannabe
- RE: OSD/PE05 Ramboot via RIS freezes systems everytime
- From: SMS_Wannabe
- OSD/PE05 Ramboot via RIS freezes systems everytime
- Prev by Date: Re: Sysprep / Drivers Update Postinstall Phase in ZTI
- Next by Date: RePartition a Drive During A Refresh Scenario, BDD, ZTI OSD
- Previous by thread: RE: OSD/PE05 Ramboot via RIS freezes systems everytime
- Next by thread: sychronisation tool
- Index(es):
Relevant Pages
|
Loading
