cmowl

Hi, I had a similar problem, until I noticed that the installer complained about a file missing. The installer wants to run LUSETUP.EXE during install, so just download the newest LiveUpdate from Symantec, rename it LUSETUP.EXE and replace the original in the installer folder. Thanks, I only have these files in the install folder: data1.cab, SAV.msi, VDefhub.zip Is there more to it now? Isn't the LUSETUP.EXE in the SAV.msi? Also, do I need the msiexec /i before the actual command? as in msiexec /i c:\Apps\SAV\SAV.msi ADDLOCAL=SAVMain,SAVUI,SAVHelp,EMailTools,OutlookSnapin NETWORKTYPE=2 REBOOT=ReallySuppress /qn I am also using SAV build 10.1.4.4000 with the following command (using runonceex.cmd) "%systemdrive%\install\sav10\symantecantivirus.msi NetworkType=1 Servername=parentserver /qb" in the sav10 folder I have the pki folder (with certificate for parent server), 0x0409.ini, Data1.cab, grc.dat (from parent server), instmsiw.exe, lusetup.exe, setup.exe, setup.ini. symantecantivirus.msi, & vdefhub.zip I grabbed the grc.dat straight from the parent server's VPHOME share Works fine. Also install a point patch after the install completes and a reboot is done "%systemdrive%\install\sav10\sav10.1.4.4020.msp reboot=reallysuppress /qb"

Do you have the link? I'm not finding it nor is google. it's a utility on the Lotus Notes CD, IBM either doesn't make it available on their website, or make it impossible to find because IBM sux big rocks. When I built my RIS image I had to jump through all of these hoops to make Notes install silently (multi-user) with the Lotus Notes Single-Sign On service installed by default. Even then I still have to launch notes and walk through the initial user setup. Longing for Exchange/Outlook.....................

The $OEM$\$1\Drivers\NIC path is for OEM-based GUI drivers (ie the drivers needed after text setup) You need to copy the *.inf, *.sys, & *.cat NIC driver files directly under the I386 folder of your image. Other drivers such as Video, Audio, GUI NIC go under the $OEM$ path Once done, run a "net stop binlsvc" and "net start binlsvc" on your RIS server so that it will re-read the NIC driver settings.

I'm sure this gets asked frequently and I've searched previous posts but I'm still somewhat confused. I am a n00b so be nice I am building out scripted RIS installs (not RIPrep images), rather the flat OS images. I have most everything else working (sans a few bugs) but here is my question. I will be deploying a Windows XP SP2 flat image to a multitude of Dell hardware. Specifically OptiPlex GX260, GX270, GX280, GX560, & GX580 computers. All have Intel Graphics chipsets in them, such as the 82845, 82865, 82915, & 82945 chipsets. All driver files have the same name (ialmnt5.inf, igfxnt5.cat, & ialmnt5.sys). If I create a directory structure as follows i386 $OEM$ -$1 --Drivers ---Video ----82845 ----82865 ----82915 ----82945 ---NIC ----subdirs ---Audio ----subdirs ---Other ----subdirs my SIF file has the following line: OemPnpDriversPath = \Drivers\Video;\Drivers\Nic;\Drivers\Audio;\Drivers\other yet no directories are searched and/or no drivers are being detected!? What is the "proper" way to do this? Do I have to create a separate image for each set of separate hardware? If so, what is the advantage of doing all this work when you can use Ghost? Please help