lasswellt

why would you try to delete this file? obviously it's a vital system file or it'd let you delete it. I'd leave it be, and stop trying to defrag and using this as a full time operating system till it's fully released...

1. Download all driverpacks you wish to integrate 2. Download SetDevicePath.exe (google or search this forum for it) & Copy to your sysprep directory. 2. Extract all packs to %WINDIR%\Drivers (do not use tool, just the packs) 3. Remove excess hardware from device manager 4. Run: C:\sysprep\sysprep.exe 4a. Check Use Mini-Setup 4b. Check Detect non-plug and play hardware 4c. Choose Quit from dropdown box 5. Run: C:\sysprep\SetDevicePath.exe %WINDIR%\Drivers This works for me! Let me know how it works for you!

i believe as long as you don't use "start /wait" and put a quit at the end of your cmd statement, it should close your command box up. hope that helps

why include this on each machine? run it off a network share and you're all set...

i too am interested in this. I need a few things added as well...

lasswellt (at) gmail (dot) com thanks!

seen this before, but oh is it so true!!!!

as far as i know, at least with the AMD version, the product is plug and play. I went to a conference where the machine had been built on a single core Opteron and they shut it down, then popped in a dual core, booted it back up, and went into task manager and showed both. most likely it's the same situation with Intel, but I can't speak for the intels.

OK here's the problem, I've sucessfully built an image that works on all my organization's desktops, however when broght down on a laptop it just sits after the bios screen, when trying last known good configuration it gives the \WINDOWS\SYSTEM32\CONFIG\SYSTEM error. Are there any reasons why there would be driver conflicts between a Desktop and Laptop? I use sysprep which should be removing all driver information and using the pnpdrivers variable in sysprep. As I have said before the image works on all different types of desktops, from different manufacturers and completely different hardware (P3 vs P4, etc). Any ideas on why it's failing when being brought down on a laptop would be great! Let me know if you need any more information.

trying to save the options you get an error - attached next when you try to open it again you get Path Not Found and this second error - attached

Yes, I entered the approporiate GUID when adding the computer account, but it still tries to add it as the default for RIS (USERNAME# i believe) which is unallowed in our AD structure. This is very good to know. Maybe the script I ran to uncover the GUID for that machine messed up. I'll try that as the GUID and see if this solves the problem. Thanks guys. Any other hints would be much appreciated, the %MACHINENAME% attrib is being used currently (no adjustments have been made to the stock sif file yet... just trying to get the basics before everything else gets done).

Now my understanding was the prestaging process was to allow for preassigning machine names and having them managed by the RIS server. My network is configured in such a way that the machine name has to be created before it is joined to the domain, which is where I would like prestaging to come into play. What do i need to add to my SIF file to have it make the computer name based on it's counterpart in AD?