wigadore

The Blue Screen is caused due to the VPN Client period. It's not supported. Install it after you've completed the RIS and you'll be fine.

I would say that not all the fixes where slipstreamed correctly. If they where then they would not be asked for again.

I never had much sucess with the RyanVM Pack and the machines I use. Instead I use the drivers for the machine and make a seperate sif for each model and include the drivers in the OemPnpDriversPath instead and I have no issues. Only issue with a driver I had was ith a broadcom and there is plenty of help online to fix the driver error on that one.

Agreed. There is nothing you can do that will stop someone from copying the contecnts of your CD. If there was Microsoft would be richer!

I am not sure if you can do this on CD as there is no OS Chooser that the RIS uses. If this is possible I would like to know as well as I make backup copies for remote users.

Multiple sif's for one image As soon as I saw it I thought why didn't I try that first! I have 10 builds now working with one Ris Image just like this. If you need further help let me know

LOL. No sooner had I posted this question the next google search I found my answer. I now have multiple sif files in the template folder and I have changed the OemPnpDriversPath to the specific machine and changed Description under the [OSChooser] to the name of the Specific PC Model such as Dell 745 or Dell 620. Voila I get a prompt for which hardware I want to install on!

I have one RIS image that works beautifully on the Dell Optiplex 745 which was the model we where buying from Dell. Now it is the EOL and the new Optiplex 755 is on it's way. What I am wanting to try to do is have one flat image that I can point to multiple sif files which will cover all the models I have in the building. This will include all laptops and desktops which I have about 5 models. Is this possible and how? Your help as always is much appreciated.

scott6191, I have just changed the way I do drivers. My OemPnpDriversPath was getting too long and some drivers where not loading. I now use nlite and slipstream the drivers into the OS CD and used that CD to make an image. As for what version of chipset driver I use...it depends on the model. Each model does not have the same chipset so I cannot use the same driver. I have the drivers for each machine loaded into the image and it works without a hitch. Perhaps I am doing it wrong this way...but it works. Only issue I have is the sound driver. It's an exe and I have not quite figured out how to load them as the inf's do not work like the other drivers.

Thanks Cancerface. I have been trying to find it to save it as a fav so if I ever loose it.

I name all my PC's on the network to the Dell Service Tag, and when I turned to RIS I found that to acheive this was rather difficult to automate. There where a few threads that explained how to pull it out using WMI or something that was hard to follow and implement. I found an easy method that I thought I would share. If this has been shared in the past please forgive me as I have not been able to find it. My first RunOnceEx.cmd only responsibility it to rename the PC, import a second RunOnceEx.cmd, and reboot. Here is the Code: @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Customize Computer Build" /f REG ADD %KEY%01 /VE /D "Rename PC to Dell Service Tag" /f REG ADD %KEY%01 /V 1 /D "%systemdrive%\apps\rename\compname.exe /c ?s" /f REG ADD %KEY%02 /VE /D "Setup Step Two" /f REG ADD %KEY%02 /V 1 /D "%systemdrive%\apps\step2.cmd" /f REG ADD %KEY%03 /VE /D "Reboot PC" /f REG ADD %KEY%03 /V 1 /D "%systemdrive%\apps\reboot.cmd" /f EXIT In my $oem$\$1\apps folder I placed a rename folder with a program called compname.exe. Simply put /c ?s changes the name of the PC to the System Serial Number, which in Dell's Case is the Service Tag. When my PC runs this and reboots I have a PC named ready to load apps in phase two and then join the domain using netdom.exe For those who may need it I will attatch the compname.exe as I cannot remember where I found it, but it is freeware. compname.zip

I am sorry to say there is NO WAY that your winnt.sif is 384mb in size. It should be more like 2-3kb in size. Go over this part of the tutorial again and recreate our winntsif Creating a Basic Unattended Setup

Change all the Off to off as it almost looks like they are Zeros, other then that it looks just like mine and mine works. As for the [Display] issue try something like this [Display] BitsPerPel=32 XResolution=1024 YResolution=768 VRefresh=75 AutoConfirm=1

I made one edit on my autologin.reg and the issue went away. I added: "ForceAutoLogon"="1" Many documents state that XP does not need this line...but it seems to have fixed my issues. Thoughts anyone?

@dj_mix Arie is 100% correct. Use the 000 numbering scheme and all your installs will go in order as you want.