Installing Bart-PE on MS RIS Server

Using Intel Pro 100 LOM Adapters

Please note: These instructions were created for Windows 2000 Server and may no longer apply

I am currently working on a BartPE setup using the fabulous BTS Driver Packs. I will update this page as soon as I am satisfied it all works. I already know the Sherpya XPE shell will not work 'out of the box' with the MS RIS setup, but I will persevere with the build.

Many NIC manufacturers have drivers with RIS text mode issues. You receive a warning when you try to RIS build a machine, or run your Bart-PE environment which says:
"The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your system administrator."
This has happened fairly frequently, and will continue until NIC manufacturers get their act together and produce decent drivers for their hardware, or until Microsoft produce a better mechanism for RIS. If you have this difficulty and don't fancy hacking drivers about as shown on section 79of this Broadcom page, you may want to download this archive (MD5 Hash: B4FEA7A9906268E29443B6E5A68545DE) of working text mode drivers. Just add them to your i386 folder then follow the usual steps to remove any .pnf files and restart the Remote Installation Service. You could also download the plugin (MD5 Hash: 7D17B68F9B9DCF4770A8C8BA0FF660D3) for Intel Nics, and build it into your Bart-PE iso.

Despite being a huge favourite with motherboard manufacturers, the Intel Pro 100/1000 LOM (LAN on Motherboard) family of network adapters does not work with Microsoft Remote Installation Services without a few alterations. The same alterations can be applied to your Bart-PE environment to allow it to be booted from your RIS menus.
I have heard that with Server 2003, Bart-PE can be added to the tools menu, but I have yet to try this. In the meantime these instructions will allow the Bart-PE environment to be booted directly from the Automatic Setup menu of Windows® 2000/Server 2003 RIS.

Install Windows® 2000 Service Pack 4 on your RIS server or alternatively install RIS server side fix 24238_ENU_i386_zip.exe as referred to in Microsoft Article Q315074. If deploying Windows® XP Professional Slipstreamed with SP1 (integrated SP1) then you will also need to install the patch referred to in Microsoft Knowledge base Article Q327536, entitled Q327536_W2K_SP4_X86_EN.exe.
On the RIS server right-click on your server-name in Active Directory Users and Computers and click on Properties
Next, click on the Remote Install -- Advanced Settings -- Images tabs and click the Add button.
Click on Add a New Installation image to start the wizard
Insert your Windows® XP installation CD and point the wizard to the \i386 directory of the cd.
Name the folder e.g. X86Bart_PE. (It is important to have this folder last in the list of RIS image folders)
Type a Friendly description and help text to identify the image (this will be the text displayed in the menu).
Proceed to file copy stage and finish the Wizard.

Create Bart-PE RIS Structure

Fairly simple, copy the entire Bart-PE cd into the \RemoteInstall\Setup\English\Images\X86Bart_PE folder on your RIS server.
Delete the following from the root of the folder

AUTORUN.INF
README.HTM
SETUP.EXE
WIN51
WIN51IP
spnotes.htm
win51ip.SP1

These files are not needed

Applying the Microsoft Bootloader Fix (This is not always necessary)

The MS bootloader file (ntldr) from the RIS OS installation set may try to run the original XP setup routine, particularly if updates have been applied to your Windows® installation. In order to prevent this, and boot directly into native Bart-PE mode:-
Copy the file setupldr.exe from your Bart-PE CD i386 folder, to the following directory
\RemoteInstall\Setup\English\Images\X86Bart_PE\i386\templates
Rename the file ntldr to ntldrold
Rename setupldr.exe to ntldr {ensure that ntldr has no extension}.

Installing Intel Drivers

Download the Windows® 2000/XP driver set from the intel site. Extract the pro2kxpm.exe file to a temporary directory
(Note: these drivers will be used only for the text mode portion of the setup, newer drivers are installed in later steps).
In Windows® Explorer create the following directory structure in the \RemoteInstall\Setup\English\Images\X86Bart_PE directory:

Copy the intel driver set files into the \RemoteInstall\$oem$\$1\Drivers\LAN folder.
Edit your system information file (.sif), normally found at \RemoteInstall\Setup\English\Images\X86Bart_PE\i386\templates\
to look similar to the example below:-

[data]
floppyless = "1"
msdosinitiated = "1"
OriSrc = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
OriTyp = "4"
LocalSourceOnCD = 1

[SetupData]
OsLoadOptions = "/noguiboot /fastdetect /minint"
SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[Unattended]
OemPreinstall = yes
OemPnPDriversPath = "Drivers\inf;Drivers\VGA;Drivers\LAN;Drivers\Audio"
FileSystem = LeaveAlone
ExtendOEMPartition = 0
TargetPath = \Windows®
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

[UserData]
FullName = "%USERFIRSTNAME% %USERLASTNAME%"
OrgName = "%ORGNAME%"
ComputerName = %MACHINENAME%

[GuiUnattended]
OemSkipWelcome = 1
OemSkipRegional = 1
TimeZone = %TIMEZONE%
AdminPassword = "*"

[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 60

[Networking]

[NetServices]
MS_Server=params.MS_PSched

[Identification]
JoinDomain = %MACHINEDOMAIN%
DoOldStyleDomainJoin = Yes

[RemoteInstall]
Repartition = Yes
UseWholeDisk = Yes

[OSChooser]
Description ="Bart-PE Diagnostic Environment built by PE-Builder"
Help ="Remote Boot Windows® XP PE environment with tools. This does not format or install anything on the hard disk and may take some time to load."
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType =Bart-PE
Version="5.1"

For Windows®® XP and Windows®® Server 2003 - e100b325.xxx and e1000325.xxx

Due to an issue with the Intel text mode drivers and the Microsoft parser, you must use different .inf files in the i386 folder for XP and 2003 than the XP/2003 base driver .inf. These modified .inf files can be downloaded from Download Finder. Download E1000325.EXE for the PRO/1000 adapters and E100B325.EXE for the PRO/100 adapters.

1. Download the appropriate file for your adapter(s)
2. Save the file in the i386 directory.
3. The e100x325.inf files in PRO2kxp.exe are still correct for the $oem$ folder.
4. Search your RIS i386 folder for files *.pnf
5. Select all *.pnf files and delete.
6. Stop and Restart the services associated with RIS by typing at a cmd (prompt):
net stop binlsvc
net start binlsvc



Well it worked for me anyway! ;o)