MarkAtWag

Yes, this boot image is for windows setup in WDS, not my capture image. Edit: side note, i also thought that i might need to install some packages, like peimg /install=WinPE-Scripting-Package D:\winpe_x86\mount\Windows i get the 0x80070002 error - only thing i could think it because its mounted on D, and AIK installed on C - just a thought

I tested this with the following in my windows\system32\winpeshl.ini [LaunchApp] [LaunchApps] x:\windows\system32\DISKPART.exe "/S X:\windows\system32\deploy.txt" but not luck. I'm wondering if somehow the WDS part of my WinPE is loading first (Install Windows screen) even though i have winpeshl file in system32.

Thanks for the help, I seem to be getting closer. I tried with just the startnet.cmd , putting wpeinit DISKPART /S X:\windows\system32\deploy.txt deploy.txt has SELECT DISK 0 ,CLEAN, EXIT. I never saw the command prompt come up, and I can tell it didnt run. -- I tried the winpeshl.ini way, (cleared out startnet.cmd except for wpeinit) So in winpeshl.ini i have [LaunchApp] [LaunchApps] X:\Windows\System32\deploy.cmd same thing, didnt run. If I Shift+F10 and search under windows\system32 I do not see my files , yet if i unmount the image and browse it I see them all. - i know im booting and mounting to the correct ones. I'll bake a pie for anyone who leads me to solve this =)

Sweet, yeah that was easy to make another instance. Now, I can AIK mount that wim to edit it to make the changes that I need. However, i just cant wrap my head around how i can force that script to run. It will boot to the deployment screen, but i want to force the following to run before we log in to deploy an image. DISKPART SELECT DISK 0 CLEAN CREATE PARTITION PRIMARY EXIT EXIT *Edit - essentially i want to run an autoexec.bat when the boot image loads.. but dont know where to put it.

After we switched vendors for laptops, the new ones have some sort of hidden oem partition that goofs up the boot manager after imaging (<Root Windows>\system32\hal.dll is missing or corrupt). I found a great fix that can be run in WDS before imaging and it makes the rest seamless. http://social.technet.microsoft.com/Forums...a5-db8af038fb0c What I would like to do is integrate the commands into a new boot.wim. So ideally when we PXE boot to wds, it will allow me to select Dell or HP; just like it does when we enable the capture boot wim. Since I didnt create the original boot wims im a little stumped. I see there is just one boot.wim and the rest (including our capture) is boot.wim.bcd . Any pointers on how to create a new boot option that can run a script before logon would be helpful! If im going about this all wrong let me know too ) Thanks again MSFN!

I have an interesting printing task at hand. I have computers going out to remote locations which will not be able to add their local printer once it is in place. Here’s the kicker, the printers are peer shared. I need to find a way to configure these shared printers, while they are at my location (different subnet). If I try to add it as a network printer > Connect to this printer: \\<computerName>\shared printername it looks for that printer, and will not allow it to install or configure with the driver. If I try to add it tcp/ip locally with the computer name or ip has host, and the printer port, it doesn’t work. We’ve tried this in a test environment. Is there a way though Add Printer Wizard to do this?

Ok, yes it seems that the res looks at the wims to see what changes etc to make to the image. res then contains all the windows and program files. For this case it seems i wont be able to even try this, since for laptops our res is 9gb .. too big for the dvds we want to distribute. I have access to our wds, but i just want to create dvds for the remote site which are yet to get a server built for them and need to start using our images. Thanks for the help!

related question, I'm going to be sending these out to a remote helpcenter, and want to load as many images as i can. Most of our .wims where uploaded strait to wds, and the file sizes are under 2mb. The image i just deployed was the full 2+gb one. Are the wds ones so small because they use the res.rwm file? if so would we need to burn the res.rwm and the small .wim files, assuming those just contain the differences within that image catagory.

Good call there... noob mistake Works perfectly now, deployed my custom image via winpe dvd. Thanks!

Thanks for the helpful guide, "Creating WIM images of Windows XP for system deployment using Windows PE" After reading this I created a bootable winpe DVD , which included a wim image. This syspreped image works fine when deployed from WDS. When deploying from the DVD WinPE boots, images to 100%, and completes, when the mini setup starts i get the error message Fatal Error An error has been encountered that prevents setup from contining. Windows is unable to start because the registry could not be updated. to address the problem contact your manufacturer. windows must shut down now =( I've read what microsoft has to say about this, and from some other forums that said to delete C:\windows\system32\microsoft\protects-1-5-18-user before sysprep. I checked my image and there was nothing in there. Any ideas? edit: i am Not using don't regenerate sids