Br4tt3

Oki.... so I have read the deploy.chm now and it states: As long as u run MS drivers supporting your RAID / SCSI boot devices u r all clear. When u add the entry [MassStorageDrivers] to your sif / txt answer file u better have a list of all the cards that u are gonna support with that image because RIS will only install drivers listed in this section and not merge (as i thought) the search with existing MS native supplied drivers. So.. I guess that some1 has had this problem before. Otherwise I will have to go through the HCL and see which cards are support by win2003 and which files they correspond to in the installation... gonna be a huge list i guess. Plz reply if u know a link or if u have already done this... otherwise cu in months!

Hi there.. I have been working with the mass storage driver fx for RIS / unattend for a while now.. and i am amazed that i cant seem to get around the fact that I need to have a single file named txtsetup.oem in the root of the textmode directory when adding supported raid cards for the text mode phase of the installation.... Supporting 1-5 raid cards will be oki, but adding a 20-30 raid cards... the text file will be huge! Any1 have some solution to this ?? How can u divide it in to subdirectories and reference many diffrent txtsetup.oem files at the same time... ??

Well... if u r set to use several images, all with diffrent folder structures and driver sets.... there are not much to do as i can see it except, associating an (1) image with several sif files. My recommendation is to keep it simple (dont over work yourself )... one basic image with all drivers $OEM$ and so on... if u want diffrent config for the machines. then just associate the diffrent sif files to the one image... keep truckin...

Yup, it is in there... however... But with means of scripting u can even predefine OU level placement of the computer object for the ris installed machine in conjunction with the name u r given it. This can be handy sometimes..

Hi dude just had a quick look at it and from what i can see u r trying to launch well known MSIexec switches (/qn) for example on .exe files... Maby the specific appz recognize these switches bu i doubt it.... seems as if u r using a tutorial for adding unattended quiet msi files, but r using .exe files from what i can see.. setup.exe /? would be a good way to find out if the specific appz accept those switches to are trying to use... also, repackage ur appz into msi if u still r up for it.

For RAID stuff and SCSI: http://support.microsoft.com/default.aspx?...duct=winsvr2003 & http://wug.lutteman.se/articles/ris-add-storage.htm hope this helps...

Hi mike First: there are tons of info about this all over the forum. Second: Specify all stuff required for an unattend install within ur answer file regarding $OEM$ folder structures and and placement of drivers there within. be sure to read everything regarding NIC's to... Thirdly: for the RAID controller part.... http://support.microsoft.com/default.aspx?...duct=winsvr2003 & http://wug.lutteman.se/articles/ris-add-storage.htm keep truckin...

if u cant find another way to make u can always use snapshot / msi (wise etc etc) to get around it... although this should be last resort as snapshots tend to be static in their deployment.

The only thing I have run into with SAV and unattended installations is that u need to have installshield installed before running the of the shelf SAV installation... To disable windows mess in the unattended install: [components] section in the answer file.... lookup the name of the component for windows messenger and set the value to = no Hope this help some...

I use WISE but then again some other ppl prefer other appz...

Almighty Lord of Laziness... since u r lazy... if it for home use or is it production enviorment? single dc config or multiple dc's configuration? if 1 u can just uninstall ad (dcpromo) and run it again to get back to square one.

Hmm... Dunno what u r really asking here but lets give it a go! From the unattend file (.txt / .sif ) u envoke parameters for the installation of the Windows installation. You for example specify the custom driver files for ur raid card as u have done. Windows will try to search for those files in the $OEM$ / textmode folder structure as also specified in ur answer file (pnpdriverspath etc etc )... If windows finds a matching driver file, it will read the content of it to try to locate the required files for the whole installation of the software driver. i guess u have to modify ur driver information files and see where it all ends up. Sorry for not being of more help at the moment karooo.

I used this link atleast: http://support.microsoft.com/default.aspx?...kb;en-us;288344

Well... kind of hard to say but.. when i did it as i can recollect I had to add the some entries to unattended section of the answer file. U have OEMPreinstall = Yes but no OEMPnPDriverPath entry and so on.. build the $OEM$ folder structure and make the corresponding answer file entries. Also, as i can recollect, i had to place a testmode directory below the $OEM$ folder structure where i placed these masstorage drivers specified in the answer file.... and then edited the inf file to point into that directory, dont know if that is the correct way but it worked out for me atleast. Good luck dude

for an unattended installation or what? i guess these will work as well for unattend as for ris.... u often have to manually edit the driver inf files... atleast i had to links: http://support.microsoft.com/default.aspx?...duct=winsvr2003 2:th: http://wug.lutteman.se/articles/ris-add-storage.htm

ooouupps... wrong one! Soz

And the other... http://support.microsoft.com/default.aspx?...duct=winsvr2003

I have had a similar problem where the RAID controller was not detected by Win2003.... solved through using this link and a MS link.. search support.microsoft.com for it, dont got it here.... here is the other one: http://wug.lutteman.se/articles/ris-add-storage.htm

I would also recommend WinPE ( if u got it )... the disk support options in RIS / unattend are not that great. Havent tried the vendor specific tools...

So got a question... 3 site with 1 main site. 1 domain structure. Site 1 DC = Infrastructure / Schema / Domain naming / Bridgehead DC = PDC emulator / RID / DC DC Site 2 DC = Bridgehead / DC Site 3 DC = Bridgehead / DC ********************************************* Question: when i run statistic's on the DC's.. the only machines that generate outbound / inbound repl. traffic is my bridgehead servers.. except my PDC emulator which generate outbound traffic aswell.. in which circumstances can they do this??? Also. all kerberos traffic seems to spread evenly on the DC's but I would assume that the PCD emulator would server most NTLM auth.. in my case the PDC almost doesnt serve any NTLM auth. Why? Any 1 got a hint on this? Ohh... and i use win2003 on all the dc's... xp and some win98 on the clients Regards

Package your appz into msi packages (and dont use snapshot tech), distribute them from a network share, use GPO / SMS / Login script to deploy them silently remotly to the clients... thats one way. I would say there are 10 things u prob can do to solve this matter all in diffrent ways and with diffrent benefits. Regards

dunno for sure... i guess that it can be the fact that u have ur primary drive devided into 2 partitions.. in the sif file, do u use repartition=yes ?? that would repartition the primary disk to one big disk and change the drive letters... try using diskpart, u can script that aswell.... it sounds as if u have something going on in ur answer file to the unattended win file that messes with ur overall idea over how the disks should look like when done... keep trucking man.

k... most common files for drivers are these: *.cat / *.sys / *.inf then again.. there are no guarantee that it is in this case (your drivers) I guess u have to seperate the files and try to install them just using them one at the time to see if u gotten the right source files... when that is cool, u build an $OEM$ folder structure like MENTIONED in forum just about everywhere... also, edit your sif file to comply with the folder structure u build for the drivers.. then again... i have had a lot of troubble with just dell drivers since they tend to wrapp the drivers in an .exe file using installshield which makes it hard to extract them... good luck dude...

if u r just after the input language... leave that entry out of the sif and let the answer choose... if u mean a 2 diffrent hardcoded copies of windows with diffrent languages... that will mean 2 i386 folders, 1 for each language version... maby if u go about adding a MUI to the installation to get around the problem for the two languages.... Take care!

Not unless u have forgotten to specify the corresponding entries in ur answer file that enables windows to search for $oem$ folder structure...