Jazkal

add this to the end of your script, right after your winnt32 setup command: Wpeutil.exe Restart

Another great feature of imagex is single instance storage. As an example, I have 45+ images that have to be maintained, that take up around 90 gigs of space or so. Using Imagex, I have that down under 10 gigs. And if you plan on using Vista or Longhorn when it comes out, your going to be using imagex anyway.

I don't use ghost, but I can say that it isn't diskpart that isn't letting recognize the partition or data. I use diskpart, and lay down my image with imgdeploy or imagex and I can access the data right away.

Personally, I use a HTA or VBS script. The sysprep.inf is on the imaged machine, once you apply the image.

os2fan2, would be willing to share your plugin?

There are two main versions of WinPE; v1.6 (aka winpe 2005) or the newest v2.0 (aka Vista WinPE). Only v2.0 is available to everyone. If you have a SA agreement with Microsoft then you can get the v1.6. Either of these will do x64 installs. It will be a learning curve for either, as they both are different from what you are used to with v1.0. IMO, you should just start with v2.0 and go from there.

In the docs that came with WinPE, look for the article "Walkthrough: Boot Windows PE from Hard Disk"

When you say make changes to the sysprep.inf file, I'm not sure if you are talking about the one in the image file, or the one that is on the system you just copied the image to? My process listed above, i modify the sysprep.inf file located on the system I am imaging (step 3). I make changes to the following sections of the file: [GuiUnattended] TimeZone= [UserData] ComputerName= [RegionalSettings] Language=

here is how I do my Win2k/2k3 deployments using Sysprep/imageX: Capture base image: 1. Prepare master installation with sysprep tool (generalize it) 2. Capture the image of sysprepe'd active partition using imagex (using WinPE 2.0) Deploy Base Image to new servers: 1. Boot system via WinPE 2.0 2. Deploy the syspreped WIM image to target machine 3. Before rebooting machine, make changes to the sysprep.inf file for server name, and other settings. 4. reboot machine and let it finish out the mini-setup

Yes the system BIOS was updated. After rebooting the system, and entering the BIOS, the correct time and date were set. I have not tested WinPE2 on ADS, but I would not think that it would work. You will probably need to use WDS or PXELinux if you want to use WinPE 2.0.

I tested with WinPE 2.0, and net time does work.

These are two seperate settings: 1) BIOS Time 2) WinPE Time (which is based on BIOS Time +/- ) Setting WinPE Time will not hold over to the next reboot. You need to use the HP tools (not sure which one, been a while since I messed with it) to set the BIOS Time.

updated. i could have sworn that it linked to the right page. I just tested the updated link, and it is going to the right page.

It is available on Windows Update catalog now. EDIT: well maybe not. It says it is the feb 2007 update, but the file looks to be the same as the other one.

I would contact the company and ask for a good INF file. But to answer your question, yes you could create an INF, it is only a text file. But the problem is that would need to know what needs to be in the INF. For all practical means, you are going to need the company to provide one.

That is a BartPE plugin INF. Not a system driver INF. You should be able to use the companies normal INF that is used to install the driver on normal windows.

To install drivers, you will need the INF file that goes with the sys file.

Here is a link: KB925720

Totally different. You have to register as an OEM to get the OPK, The WAIK is available to everyone.

Updated the first post with the newest download page with the WAIK Final release, updated today.

Yes, I just checked and it looks like they may be releasing a newer "fixed" version. I will update the links when the new download webpage is released. The first link in the first post of this thread still works if you need to download the whole thing.

Have you tried building your WinPE2005 image with the /PNP switch? Some nics won't work unless it can detect and install other bus drivers first. EDIT: On the 2850, it uses the "Intel® PRO/1000 MT Network Connection" nic. The driver I use for this one, I have attached. This driver INF looks like it is also for the MB nic you use. This is an older version of the driver, but I have no issues with it in WinPE. e1000325.zip

After you unzip the microsoft package, open a command prompt and browse to the i386 folder inside the unziped package. Then run the devcon command from there.

Was it an error that said it wasn't there, or was something wrong? If you need to download it, get it here: http://support.microsoft.com/kb/311272

What model of Dell machine are you using? I currently have Dell Poweredge 2650, 2850, 2950, 6650, and 6850's working on WinPE 2005 based on Win2k3SP1.