m.i.l.e.s

Well it would be great if someone more experienced did post in here. Dont know why i bother with this place to be honest I have had several problems, searched the forum to no avail and posted up a question (as per the rules) I know not everyone integrates so many drivers into an image but someone must have had a similar problem. Thanks for your time to read this question though MadBoy Regards, Miles au revoir to the forum that never replies!

Hi people. I am creating a new set of 2K3 RIS images for deployment at work. Originally i had intended to have images containing the NIC/RAID/CHIPSET/VIDEO etc drivers for both our current platform (Bensley) and our old platform (Lindenhurst). I ran into problems however when Lindenhurst drivers had the same filenames as the Bensley drivers. So.....i decided to have two sets of images - one for each platform. One set of images contains all of the NIC/RAID/CHIPSET etc etc drivers for the Intel Bensley Platform - this is done and works fine. The next problem comes when i discover that there are Lindenhurst drivers with the same name, for example two drivers using symmpi.sys, and two using nodev.inf and txtsetup.inf etc etc. The problem comes of course when copying the .sys, .cat, .inf files to the TEXTSETUP and i386 directories and being prompted to overwrite. Is there any way around this??? its driving me crazy now - i dont want so many images that the people relying on the server dont know whats in each image but i dont think you can just rename files or add directories under the TEXTSETUP and i386 folders. Any help is much appreciated. Thanks, Miles

Hi people, I have started playing about with WDS. I am very familiar at adding drivers into an XP, 2K3 image etc etc with RIS but what i need to do now is add drivers to my new 2K3 images that i am deploying with WDS. I have used BDD to add the mass storage drivers to the "out of box" drivers store and ensure that the build and deployment point are set top use these drivers. I havent created any unattended.xml files yet. My test system with SAS software RAID keeps blue screening because it cant find the drivers - any ideas? Do i need an .xml file which also specifies the drivers to be installed? Any help is much appreciated cos i havent a clue what i am doing wrong. Thanks, Miles

Cheers for the reply I understand everything fine and know what i need to do but having never done anything with XML before i just wanted an example unattended.xml file as a reference for syntax and layout etc Would be unbelievably grateful if someone could post up a complete XML file for both parts of the process - imaging and initial welcome Thanks, Miles

Hi people. I have a lab environment at work which i am transitioning over to WDS from quite an extensive RIS system. Problem i am having at the moment is automating the initial stages of the WDS menu's where the user is prompted to enter the language and login credentials. i have found some info from Microsoft as to the entries i need to create in an unattended answer file but i cant find anywhere an example file to use as a reference. So far i havent created any .xml files and could do with some examples to use as a reference - for both stages of unattended setup (images/wds welcome) Also....my system is currently in mixed mode so that the existing RIS system works for all the Redhat, Suse, Fedora, ESX etc etc images i have. The menu option for this is currently "REMOTE INSTALLATION SERVICE" does anyone know how to change this text?? Thanks for your time Miles