bastianbu

here is what i use that entrys allow me to do the partitioning my self during the installation from the ris. ----------------------------------- ;SetupMgrTag [data] floppyless="1" MsDosInitiated= "0" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" LocalSourceOnCD=1 DisableAdminAccountOnDomainJoin=0 UnattendedInstall="Yes" [setupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [unattended] FileSystem=LeaveAlone ExtendOEMPartition=0 TargetPath=\WINDOWS OemSkipEula=Yes InstallFilesPath=\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE% LegacyNIC=1 UnattendMode=FullUnattended NtUpgrade=No OemPreinstall=Yes WaitForReboot="No" OverwriteOemFilesOnUpgrade=Yes DriverSigningPolicy= "Ignore" NonDriverSigningPolicy= "Ignore" [RemoteInstall] Repartition=1,Wait UseWholeDisk=1,Wait

lets say it that way if i am using method 1 i can decid if i want to do the partitioning my self or let the computer do it in a specified way. hm about the speed: i am using method 1 an my laptop: dell c640 (1,8 ghz p4m 1024 mb ram) is installed within 20 minutes including 7zip adobe acrobat office 2003 cool codecs etc. edit: i am using the active directory to deploy the software no kind of problem there. edit2: does anyone know an pxe w-lan card? (minipci or pcmcia or pci)

but riprap is only for one computer or computers of 1 kind if you are using method 1 you can install nearly every computer (that has an supported networkcard or an pxe rom)

@ raymondbreen: so we 2 are getting the beta testers for rising bts driverpacks? @ all: if we are using ris server we are mainly deploying apps with grulies *ähm i dont know the englisch name; sorry* so we are using *.msi files for deploying. Here is a good guid for making msi files and deploying them: http://www.gruppenrichtlinien.de/ *german site; sorry about this ...*

ähm i was talking about method 1 the networkbased installation by the way: setupscreens app installations cmdlins.txt runonceex scripting etc. is working fine on my ris server

Hi Bashrat here is a first info on using a ris server with your driverpacks: the windows internal drivers for Broadcom Lan-cards have to be edited else the will not work with the RIS-Server and your Driverpacks. here is the info about what to edit: http://www.broadcom.com/drivers/faq_drivers.php 79.) How do I install Windows 2000 and Windows XP using Remote Installation Services? Microsoft Remote Installation Service(RIS) Instructions for Adding Broadcom Network Adapter Driver Problem: Microsoft Remote Installation Service (RIS) installation fails to load Broadcom Network Adapter driver for both Windows 2000 and Windows XP. Solution: Follow the steps below using excerpts from Microsoft Article Knowledge Base, "How to Add Third-Party OEM Network Adapters to RIS Installations (Article Nos. 246184 for Windows 2000 and 315279 for Windows XP)." On the RIS server, copy the supplied driver files for the Broadcom network adapter to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. This includes the B57win32.inf file, and depending on which operating system is being deployed by RIS, you would include the b57w2k.sys for a Windows 2000 installation or b57xp32.sys for a Windows XP installation. This allows Setup to use the driver during the text-mode portion of the installation. If deploying Windows XP, modify the b57win32.inf file accordingly: 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 the manufacturers section (see the following example). Original [Manufacturer] %BRCM% = Broadcom, NTx86.5.1 Revised [Manufacturer] %BRCM% = Broadcom If deploying Windows 2000, perform step 2b above only if the RIS server does not have Service Pack 3 or later. At the same level as the i386 folder on the RIS image, create a $oem$ folder. Use the following structure: \$oem$\$1\Drivers\Nic. This is where the GUI portion of the Windows installation will search for the driver for our Adapter. Copy the supplied driver files (consistent with step 1 above) to this folder and include the b57win32.cat file. The b57win32.cat is used to show that the driver for the Broadcom adapter is digitally signed. It is important to use the original b57win32.inf file supplied in this folder or the digital signature will become invalid. A symptom of this would be that an unattended installation may be interrupted with a pop-up indicating that the Broadcom adapter driver is not digitally signed or the driver may not load correctly altogether. Make the following changes to the .sif file that is used for this image installation: [unattended] OemPreinstall = yes OemPnpDriversPath = \Drivers\Nic (append if necessary) Stop and then restart the BINL service on the RIS server. To do this, type the following from a command prompt: net Stop "boot information negotiation layer" net Start "boot information negotiation layer" ----------------------------------------------- I´ll add my winnt.sif for use with the RIS-Server later on this day The rest of Method 1 is currently working Method 2 isnt working because the DP-Files arent copied if the arent placed ín $oem$/$1/... The basic network support of the ris server ends with the end of the txtpart of the setup; thats why they arent copied later on

hi method 2 doesn´t work with an RIS-Server :/ but to get it working i got an idee 1. we will have to copy the [RISSETUPMAIN]/OEM dir from the method 2 after running the runme.cmd to [RISSETUPMAIN]/$OEM$/$1/OEM 2. the preparation must be toled that it should extract the Driverpacks form %systemdrive%/oem 3. also the preparationprogrammes have to be runed from %systemdrive%/OEM/bin sorry about my poor english... but i hope that i could help a bit best wishes bastianbu