RIS on 2003 Server & "The operating system image you selected does not contain the necessary drivers

[Gui]

Hello All,

I'm not new to RIS, in fact I've sucessfully helped few in this newsgroup
with the same issue.
I had this same issue with Intel ProVM NICs when I set up a RIS server On
Win2K Server to deploy W2K Pro images.....
This time I'm trying to do it with Windows 2003 RIS Server and Broadcom Gig
NIC's in the workstation
I've followed the instructions for the follwoing "Q" articles wich resolved
the issue the last time and got nowhere.

Q315279 - How to Add a 3rd Party OEM Network Adapter to a RIS Installation
Q254078 - How to Add OEM Plug and Play Drivers to Windows Instalations

RIS works fine with other PCI based clients with M$ approved NIC's
I created the following folder hierarchies

CD Based Image w XP SP1a Slip'd
|
|_$oem$
| |_$1
| |_Drivers
| |_NIC
|
|_i386
| |_asms
|______lang
|__________system32
|____________Templates


RIPrep'd Image w XP SP1a
|
|_$oem$
| |_$1
| |_Drivers
| |_NIC
|
|_i386
| |_Mirror1
|______Templates

and copied the Broadcom drivers to each of the NIC folders
Also edited the .sif files with
[Unattended]
OemPreinstall = YES
OemPnpDriversPath = \Drivers\Nic
DriverSigningPolicy = Ignore

Any help will be greatly appreciated
Thanks
Brian

 

[NIC Student]

Hi Brian,

Take a look at my site under "OEM Driver installations" for Broadcom
instructions.

http://www.mvps.org/serverstuff/

 

[Crystal]

We just had a similar problem with broadcom NIC's on Dell
Latitude laptops. we fixed it by doing the following:

the .inf file is b57xp32.inf
In the .inf file that is to be placed in the
RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder,
remove NTx86.5.1 in two lines (see the following
example). You might need to change also in Provider = %
V_BCM% (it was %BRCM%), and you probably have to do it as
it is written below....

Original:
[Manufacturer]
%V_BCM% = BROADCOM, NTx86.5.1
[ControlFlags]
ExcludeFromSelect = *
[BROADCOM.NTx86.5.1]

Revised:
[Manufacturer]
%V_BCM% = BROADCOM
[ControlFlags]
ExcludeFromSelect = *
[BROADCOM]

Only use the .inf file provided by the vendor for this
purpose.

Remember to restart the Boot Information Negotiation
Layer service at the RIS server!
Hope this helps
Crystal
cggers(at)wm(dot)edu

-----Original Message-----
Hi Brian,

Take a look at my site under "OEM Driver installations" for Broadcom
instructions.

http://www.mvps.org/serverstuff/

--
Scott Baldridge
Windows Server MVP, MCSE

Hello All,

I'm not new to RIS, in fact I've sucessfully helped few in this newsgroup
with the same issue.
I had this same issue with Intel ProVM NICs when I set up a RIS server On
Win2K Server to deploy W2K Pro images.....
This time I'm trying to do it with Windows 2003 RIS

Server and Broadcom
Gig

NIC's in the workstation
I've followed the instructions for the follwoing "Q"

articles wich
resolved

the issue the last time and got nowhere.

Q315279 - How to Add a 3rd Party OEM Network Adapter to a RIS Installation
Q254078 - How to Add OEM Plug and Play Drivers to Windows Instalations

RIS works fine with other PCI based clients with M$ approved NIC's
I created the following folder hierarchies

CD Based Image w XP SP1a Slip'd
|
|_$oem$
| |_$1
| |_Drivers
| |_NIC
|
|_i386
| |_asms
|______lang
|__________system32
|____________Templates


RIPrep'd Image w XP SP1a
|
|_$oem$
| |_$1
| |_Drivers
| |_NIC
|
|_i386
| |_Mirror1
|______Templates

and copied the Broadcom drivers to each of the NIC folders
Also edited the .sif files with
[Unattended]
OemPreinstall = YES
OemPnpDriversPath = \Drivers\Nic
DriverSigningPolicy = Ignore

Any help will be greatly appreciated
Thanks
Brian

.

 

[Gui]

That did the trick!
Thanks to both of you for replying!

 

[Gui]

Thanks Scott And Crystal,
That did the trick!

-Brian McMullen

 

[Scott McArthur [MSFT]]

Crystal,

FYI. There is a fix now so you do not need to edit the inf's. You will
likely encounter this issue with just about every inf out there now so make
sure all your RIS servers have it installed. Just call into support and
request 823658. There is no charge to request the fix

Scott McArthur[MS]
Microsoft Windows Server Setup Support
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| Content-Class: urn:content-classes:message
| From: "Crystal" <[email protected]>
| Sender: "Crystal" <[email protected]>
| References: <#pZ#[email protected]>
<[email protected]>
| Subject: Re: RIS on 2003 Server & "The operating system image you
selected does not contain the necessary drivers"error
| Date: Wed, 10 Mar 2004 07:20:39 -0800
| Lines: 116
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQGsz6PKsRUTgcJRpC+nglkR1ia7g==
| Newsgroups: microsoft.public.windowsxp.setup_deployment
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:105073
| NNTP-Posting-Host: tk2msftngxa11.phx.gbl 10.40.1.163
| X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
|
| We just had a similar problem with broadcom NIC's on Dell
| Latitude laptops. we fixed it by doing the following:
|
| the .inf file is b57xp32.inf
| In the .inf file that is to be placed in the
| RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder,
| remove NTx86.5.1 in two lines (see the following
| example). You might need to change also in Provider = %
| V_BCM% (it was %BRCM%), and you probably have to do it as
| it is written below....
|
| Original:
| [Manufacturer]
| %V_BCM% = BROADCOM, NTx86.5.1
| [ControlFlags]
| ExcludeFromSelect = *
| [BROADCOM.NTx86.5.1]
|
| Revised:
| [Manufacturer]
| %V_BCM% = BROADCOM
| [ControlFlags]
| ExcludeFromSelect = *
| [BROADCOM]
|
| Only use the .inf file provided by the vendor for this
| purpose.
|
| Remember to restart the Boot Information Negotiation
| Layer service at the RIS server!
| Hope this helps
| Crystal
| cggers(at)wm(dot)edu
|
| >-----Original Message-----
| >Hi Brian,
| >
| >Take a look at my site under "OEM Driver installations"
| for Broadcom
| >instructions.
| >
| >http://www.mvps.org/serverstuff/
| >
| >--
| >Scott Baldridge
| >Windows Server MVP, MCSE
| >
| >
| >> Hello All,
| >>
| >> I'm not new to RIS, in fact I've sucessfully helped
| few in this newsgroup
| >> with the same issue.
| >> I had this same issue with Intel ProVM NICs when I set
| up a RIS server On
| >> Win2K Server to deploy W2K Pro images.....
| >> This time I'm trying to do it with Windows 2003 RIS
| Server and Broadcom
| >Gig
| >> NIC's in the workstation
| >> I've followed the instructions for the follwoing "Q"
| articles wich
| >resolved
| >> the issue the last time and got nowhere.
| >>
| >> Q315279 - How to Add a 3rd Party OEM Network Adapter
| to a RIS Installation
| >> Q254078 - How to Add OEM Plug and Play Drivers to
| Windows Instalations
| >>
| >> RIS works fine with other PCI based clients with M$
| approved NIC's
| >> I created the following folder hierarchies
| >>
| >> CD Based Image w XP SP1a Slip'd
| >> |
| >> |_$oem$
| >> | |_$1
| >> | |_Drivers
| >> | |_NIC
| >> |
| >> |_i386
| >> | |_asms
| >> |______lang
| >> |__________system32
| >> |____________Templates
| >>
| >>
| >> RIPrep'd Image w XP SP1a
| >> |
| >> |_$oem$
| >> | |_$1
| >> | |_Drivers
| >> | |_NIC
| >> |
| >> |_i386
| >> | |_Mirror1
| >> |______Templates
| >>
| >> and copied the Broadcom drivers to each of the NIC
| folders
| >> Also edited the .sif files with
| >> [Unattended]
| >> OemPreinstall = YES
| >> OemPnpDriversPath = \Drivers\Nic
| >> DriverSigningPolicy = Ignore
| >>
| >> Any help will be greatly appreciated
| >> Thanks
| >> Brian
| >>
| >>
| >
| >
| >.
| >
|

 

[NIC Student]

Thanks for the heads-up, Scott.

--
Scott Baldridge
Windows Server MVP, MCSE


"Scott McArthur [MSFT]