Jump to content

how to add broadcom nic driver to ris installation?


Recommended Posts

hello everyone.

i had a problem as follow..

* ris server information

- machine : IBM x445

- os : windows2003 ent sp1

our customer is using 200 dell-poweredge-1650 machines. during ris installation, i got the problem to install broadcom driver on 1650 machine. ( ris client os is also win2003 ent )

whenever i check the n/w driver after ris client installation, i find that n/w driver is "unknwon driver" in Device driver manager.

i did everything as ms/broadcom guide.

please.. help!!

the following was done.

1. broadcom recommandation

To deploy a Windows 2003/Windows XP Image

Follow the steps described in Microsoft Knowledge Base Article - 315279 at http://support.microsoft.com/default.aspx?...ben-us%3b315279.

Modify the b57win32.inf file as described below. In the .inf file that is to be placed in the RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder:

Remove the [broadcom] section (see the following example):

[broadcom]

%OEM1_DEV5% = OEM1_DEV5.Inst, PCI\VEN_14e4&DEV_165D&SUBSYS_865d1028

.

.

%BCM5750B0F% = BCM5750B0MF.Inst, PCI\VEN_14e4&DEV_167E&SUBSYS_057D1014&REV_10

Remove NTx86.5.1 in two locations (see the following example).

Original Revised

[Manufacturer]

%BRCM% = Broadcom, NTx86.5.1

[broadcom.NTx86.5.1]

[Manufacturer]

%BRCM% = Broadcom

[broadcom]

Follow the steps in the Microsoft Knowledge Base Article- 315279 at http://support.microsoft.com/default.aspx?...kb;en-us;315279, skipping step 1, as shown above.

2. Folder structure.

D:\RemoteInstall\Setup\Korean\Images\win2003.ent.kor

D:\RemoteInstall\Setup\Korean\Images\win2003.ent.kor\$OEM$

D:\RemoteInstall\Setup\Korean\Images\win2003.ent.kor\$OEM$\$1$

D:\RemoteInstall\Setup\Korean\Images\win2003.ent.kor\$OEM$\$1$\Drivers

D:\RemoteInstall\Setup\Korean\Images\win2003.ent.kor\$OEM$\$1$\Drivers\Nic

3. ristndrd.sif configuration.

;SetupMgrTag

[data]

floppyless="1"

msdosinitiated="1"

OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%"

OriTyp="4"

LocalSourceOnCD=1

DisableAdminAccountOnDomainJoin=1

AutoPartition=1

UnattendedInstall="Yes"

[setupData]

OsLoadOptions="/noguiboot /fastdetect"

SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[unattended]

OemPreinstall=Yes

OemPnpDriversPath="Drivers\Nic"

DriverSigningPolicy=Ignore

FileSystem=LeaveAlone

ExtendOEMPartition=0

TargetPath=\WINDOWS

OemSkipEula=Yes

InstallFilesPath=\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%

LegacyNIC=1

UnattendMode=FullUnattended

NtUpgrade=No

OverwriteOemFilesOnUpgrade=No

[userData]

FullName="%USERFIRSTNAME% %USERLASTNAME%"

OrgName="%ORGNAME%"

ComputerName=%MACHINENAME%

ProductKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[GuiUnattended]

OemSkipWelcome=1

OemSkipRegional=1

TimeZone=230

AdminPassword=xxxxxxxxxxxxxxxxxxxxxxxxxx

EncryptedAdminPassword=Yes

AutoLogon=Yes

AutoLogonCount=1

[LicenseFilePrintData]

AutoMode=PerServer

AutoUsers=500

[Display]

BitsPerPel=32

XResolution=1024

YResolution=768

VRefresh=60

[Networking]

InstallDefaultComponents=No

ProcessPageSections=Yes

[identification]

JoinDomain=%MACHINEDOMAIN%

DoOldStyleDomainJoin=Yes

[RemoteInstall]

Repartition=Yes

UseWholeDisk=Yes

[OSChooser]

Description="Win2003 Ent. Kor."

Help="Windows 2003 Enterprise installation"

LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"

ImageType=Flat

[RegionalSettings]

LanguageGroup=8

[branding]

BrandIEUsingUnattended=Yes

Home_Page=http://www.naver.com

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

[NetAdapters]

Adapter1=params.Adapter1

[NetClients]

MS_MSClient=params.MS_MSClient

[NetProtocols]

MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]

DNS=Yes

UseDomainNameDevolution=No

EnableLMHosts=Yes

AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]

SpecificTo=Adapter1

DHCP=Yes

WINS=No

NetBIOSOptions=1

edit by Martin L: removed licensekey and adminpassword :)

Edited by Martin L
Link to comment
Share on other sites


Hi,

You don't mention *exactly* what the problem is...

i) Does the RIS installation complete only for the client system to not have the Windows driver for the Broadcom NIC installed?

or

ii) Does the RIS server refuse to load the image through text-mode setup saying that "There is not a suitable driver for your hardware" or something to that effect?

If the problem is i) then the answer lies with checking your SIF file.

If the problem is ii) (which I suspect) then you need to check that you followed the Broadcom RIS instructions 100% and that you have restarted the BINL service. I suspect that not restarting the BINL service is the most likely cause as you don't mention it in your otherwise comprehensive post.

To restart the BINL service, first make sure you have copied the required Broadcom *.inf and *.sys driver files to the i386 folder.

Next, log on to the RIS server and open a "cmd" prompt. Then type:

NET STOP BINLSVC
NET START BINLSVC

Your drivers should now work.

Please let me know how it goes.

Cheers,

Andy

ps - There is one other possibility which is that you need to make sure you are using the latest Broadcom drivers. They are v8.48e for gigabit NICs.

Also, note (this is a big note!) Broadcom changed their RIS instructions recently. You seem to be using the old method. Try this instead (from the Broadcom site):

...Locate [Manufacturer]within the file.

Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1, NTamd64.

Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The change made replaces the comma and space after "Broadcom" with a period.

Save the file.

Edited by Fencer128
Link to comment
Share on other sites

sorry..

the problem is that broadcom driver is not installed on ris client nevertheless ris insatllation complete on client.

i) Does the RIS installation complete only for the client system to not have the Windows driver for the Broadcom NIC installed?

Yes.

ii) Does the RIS server refuse to load the image through text-mode setup saying that "There is not a suitable driver for your hardware" or something to that effect?

No. there was no error messange during ris installation..

Hi,

You don't mention *exactly* what the problem is...

i) Does the RIS installation complete only for the client system to not have the Windows driver for the Broadcom NIC installed?

or

ii) Does the RIS server refuse to load the image through text-mode setup saying that "There is not a suitable driver for your hardware" or something to that effect?

If the problem is i) then the answer lies with checking your SIF file.

If the problem is ii) (which I suspect) then you need to check that you followed the Broadcom RIS instructions 100% and that you have restarted the BINL service. I suspect that not restarting the BINL service is the most likely cause as you don't mention it in your otherwise comprehensive post.

To restart the BINL service, first make sure you have copied the required Broadcom *.inf and *.sys driver files to the i386 folder.

Next, log on to the RIS server and open a "cmd" prompt. Then type:

NET STOP BINLSVC
NET START BINLSVC

Your drivers should now work.

Please let me know how it goes.

Cheers,

Andy

ps - There is one other possibility which is that you need to make sure you are using the latest Broadcom drivers. They are v8.48e for gigabit NICs.

Also, note (this is a big note!) Broadcom changed their RIS instructions recently. You seem to be using the old method. Try this instead (from the Broadcom site):

...Locate [Manufacturer] within the file.

Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1, NTamd64.

Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The change made replaces the comma and space after "Broadcom" with a period.

Save the file.

Link to comment
Share on other sites

I agree with Andy. The $1 & $$ are placemarkers not just directories used during the setup process and are equivalent to %systemdrive% and %windir%. So $1$ is meaningless.

I also strongly suggest you create your default RIS Windows XP install and then save changes in a duplicated directory structure (eg remoteinstall.add) and robocopy this to the reminst share and then restart binlsvc. That way its easy to see what you've added (or missed) Just remeber to delete any files from the live RIS share if you remove them from your add structure. Also makes it easy to replicate the RIS config for other OSes!

Hope this helps

Chris

Edited by christos$99
Link to comment
Share on other sites

I srongly suggest you to remove your CDKEY...and Admin Password... OMG!!!!

I second that! Major mistake!

Andy

PS leenamhee PMed me and told me that the folder name change did fix the problem. However, it looks like he may of inadvertently caused another!

Edited by Fencer128
Link to comment
Share on other sites

Hello everyone..

first of all, i really thank for your answer & interest specially to frencer128. :)

as Fencer128 menthioned, i fixed the problem by changing the folder name from $1$ to $1

until now, there is no problem about progress on ris installation.

(i sent mail to frencer128 involuntarily cause i'not unfamiliar to use this site.)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...