WDS hangs at OS Chooser V5.0 screen

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

We are implementing Server 2003SP2 with Windows Deployment Services. I have
successfully installed and configured the server according to the
Step-by-Step Guide for Windows 2003.

I have been able to capture an image, and deploy it to several computers
without any problems. However, there are a few computers that when they are
booted to the network using F12, hang at a black screen with "OS Chooser
v5.0" in the top left corner. After a few minutes, the screen will turn blue
and be completely blank. Then nothing happens at all.

I am not sure what may be causing this as the computers that "hang" at this
point are exactly the same model of laptop, with identical hardware to ones
that deploy successfully.

Any suggestions would be greatly appreciated.

Chris
 
Hi Chris,

Do you have free ips in your dhcp scope when you attempt the deployment?
Have you tried connecting one of the problem laptops to a network port of a
laptop that did deploy fine?
Are there very many computers that are having this issue? ..it could be
possible i suppose if it is a small number of them, and of the same series,
that the nics could be factory faulty. You could try changing one to test.

Are your computers x64? If so, this is what Microsoft suggests...
"x64-based client computers do not receive an x64-based Windows PE boot
image. This can occur if the PXE basic input/output system (BIOS)
implementation of the network booting computer does not correctly identify
itself as supporting x64-based computers. To work around this issue, enable
architecture detection in the boot programs by typing the following at a
command prompt:
WDSUTIL /set-server /architecturediscovery:yes
"

Coraleigh Miller

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:C502ADFE-F9C9-4110-9349-53A29318F06E@microsoft.com...
> We are implementing Server 2003SP2 with Windows Deployment Services. I
> have
> successfully installed and configured the server according to the
> Step-by-Step Guide for Windows 2003.
>
> I have been able to capture an image, and deploy it to several computers
> without any problems. However, there are a few computers that when they
> are
> booted to the network using F12, hang at a black screen with "OS Chooser
> v5.0" in the top left corner. After a few minutes, the screen will turn
> blue
> and be completely blank. Then nothing happens at all.
>
> I am not sure what may be causing this as the computers that "hang" at
> this
> point are exactly the same model of laptop, with identical hardware to
> ones
> that deploy successfully.
>
> Any suggestions would be greatly appreciated.
>
> Chris
 
Hi Coraleigh,

I didn't check the DHCP scope at the time of deploying the laptop in
question, however when I tried to deploy again with the laptop that did work,
it was able to receive the image again, and that was within a few minutes of
the first attempt. In regards to the network port connection, the failed
laptop was plugged into the same cable as the first, then plugged into the
same docking station as the first one the deployed properly. They are all x86
based laptops, and out of 8 laptops, 3 have failed at the OS Chooser screen.

As an additional note, I tried with a desktop x86 machine, and that failed
at the OS Chooser screen as well.

Thank you for the reply, and if you have any other things to check, I would
be glad try them out.

Chris

"Coraleigh Miller" wrote:

> Hi Chris,
>
> Do you have free ips in your dhcp scope when you attempt the deployment?
> Have you tried connecting one of the problem laptops to a network port of a
> laptop that did deploy fine?
> Are there very many computers that are having this issue? ..it could be
> possible i suppose if it is a small number of them, and of the same series,
> that the nics could be factory faulty. You could try changing one to test.
>
> Are your computers x64? If so, this is what Microsoft suggests...
> "x64-based client computers do not receive an x64-based Windows PE boot
> image. This can occur if the PXE basic input/output system (BIOS)
> implementation of the network booting computer does not correctly identify
> itself as supporting x64-based computers. To work around this issue, enable
> architecture detection in the boot programs by typing the following at a
> command prompt:
> WDSUTIL /set-server /architecturediscovery:yes
> "
>
> Coraleigh Miller
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:C502ADFE-F9C9-4110-9349-53A29318F06E@microsoft.com...
> > We are implementing Server 2003SP2 with Windows Deployment Services. I
> > have
> > successfully installed and configured the server according to the
> > Step-by-Step Guide for Windows 2003.
> >
> > I have been able to capture an image, and deploy it to several computers
> > without any problems. However, there are a few computers that when they
> > are
> > booted to the network using F12, hang at a black screen with "OS Chooser
> > v5.0" in the top left corner. After a few minutes, the screen will turn
> > blue
> > and be completely blank. Then nothing happens at all.
> >
> > I am not sure what may be causing this as the computers that "hang" at
> > this
> > point are exactly the same model of laptop, with identical hardware to
> > ones
> > that deploy successfully.
> >
> > Any suggestions would be greatly appreciated.
> >
> > Chris
>
>
>
 
Back
Top