IcemanND

do you have a way to make a bartpe cd (preferred) or connect the infected drive to another machine?

is the file actually missing from c:\windows\system32? Ir is it the registry value that loads it that is missing?

Try Offline Sysprep, http://www.911cd.net/forums//index.php?sho...0&start=120

Which BSOD do you get 0x0000007b?

It won't get it directly from the offline registry, but you can launch regedit, select the HKLM root key, go to file select load hive, select e:\windows\system32\config\software, enter PE for the key name. then in keydecoder go to the settings menu, select the offline registry key name option, then enter PE and click decode.

imagex /info Imagefile.wim Replace Imagefile.wim with your wim file name. Will return Windows version and SP information in the version section of the XML data.

http://www.msfn.org/board/index.php?showto...mp;#entry383775 The pro version will let you pull the license numbers from machines and registry files in numerous ways.

No need to double post, the triple post I'll mark up to an accidental double click. Since you are using nLite I'm leaving the one post here. if you get a blue screen stating windows\system32\config\system is missing or corrupt it either can't find part of the registry to load or can't find the hard disk. Have you been able to successfully boot this build at all?

The way to do this is to Boot from Windows PE, then partition and format the drive, and finally kick off the installation of windows using winnt32.exe. That is if you want it all to be unattended.

When adding RunOnce keys via an INF install they are run immediately after the INF install completes. From: http://support.microsoft.com/kb/281820 Further down the same page: You should be seeing one of two things when you run the INF you provided, either an error that myfile.bat is not a valid win32 application, or you see you bat file flash on the screen as it runs.

While the file locations are nice, I have no way of connecting to your machine to look at them as you provided no information to do so. It would be more helpful to just post the BSOD information you see, Stop code module name etc.

One of two things is happening, and without the BSOD you are not seeing do to the reboot it is hard to say which it is, usually this behavior is due to the mass storage controller as stated earlier, or by an incompatible HAL. When you boot to safe mode what happens?

No not included. Much easier to use a portable version of firefox. But if you have to use IE, check out winbuilder.net, they may have the scripts in one of the many PE build options that can add IE.

Um, Trip....What script???? Anyway, I use an AutoIt script using the functions here: http://www.autoitscript.com/forum/index.ph...changescreenres

Gnomeofdeath- How are your doing the domain join? If you are doing it via script, instead of answer file, you can run you net local group commands before you send the reboot command. So... Join domain (no reboot) Add users to local groups reboot

And on that note topic closed.

Question remains, what steps did you go through when you partitioned the drive? Do you get an error when you try and boot, what is it?

What commands did you use when partitioning the drive with Diskpart?

How are you deploying? What do you need to add the scsi drivers to? The Windows PE boot image, the System Image, both?

VirtualCloneDrive - http://www.slysoft.com/en/virtual-clonedrive.html Have not tried it in Server 2008, but it works great in Vista x64.

See printer install script here: http://www.msfn.org/board/index.php?showto...st&p=794768 I haven't tried it as am SMS install, but there is no reason why it would not work as such.

The guide that is stickied at the top of the PE forum gives you step by step instructions and info on creating a PE cd.

And with that, Let's not discuss warez any more please. CLOSED.

get the latest version 4.5.4, see the options on the Automatic Install tab. For more information check the help from within the app. And yes it works with compressed Driverpack drivers, that was what it was designed for.

same way you would from the command prompt in XP or Vista. Once you confirm the network drivers are loaded and you have network connectivity use the NET USE command.