IcemanND

the the imagex /prep command.

Technically you can't. At least not in the way you can for Vista. You can add it to your image and add the appropriate scripts to install them via cmdlines.txt, runonce etc.

they are changing the built in administrator account name by local policy. Change it via policy to what you want and it should take care of it.

You don't need DOS if you use PE2. Check this guide out http://www.msfn.org/board/GUIDE_Creating_W...XP_t101383.html check out the appendix it tells you where to put the ghost32 executable. You may not even need to add network drivers but that is described in the guide also.

When you are booted in diagnostic mode the Server service is disabled. The current version of sysprep checks for the Server Service before running and it must be started in order for sysprep to run.

Please don't double post. See responses in first post. http://www.msfn.org/board/Deleting_entries...st_t106681.html CLOSED.

Make the PE image smaller: After installing packages and drivers the Windows PE image is likely bloated with unused items. To remove the unused items run the following where <source wim> is the bloated image and <dest wim> will be the cleaned up image. <dest wim> must not already exist. Imagex /boot /export <source wim> 1 <dest wim> From Imagex Help: IMAGEX [FLAGS] /EXPORT src_file src_number | src_name dest_file dest_name Exports a copy of the specified image to another WIM file. src_file - The path of the WIM file that contains the image to be copied. src_number - The number that identifies the image within the source WIM. src_name - The name that identifies the image within the source WIM. dest_file - The path of the WIM file that will receive the image copy. dest_name - The unique name for the image in the destination WIM. Accepted FLAGS: /BOOT Marks a volume image as bootable. Available for Windows PE images only. /CHECK Enables WIM integrity checking. If not provided, existing checks are removed. /COMPRESS [maximum | fast | none] Specifies the type of compression used when exporting to a new WIM file. /REF splitwim2.swm Enables the reference of split WIM (SWM) files. splitwim2.swm - Path to additional split file(s). Wild cards are accepted. Comments: If src_name is "*" then all images are exported to dest_file. Example: imagex /export d:\imaging\data.wim 1 d:\imaging\newfile.wim "Exported Image"

What exactly are you trying to do? If you want to adjust and change those settings it has to be done programatically.

Why not use Windows PE 2 and Ghost32 from the GSS 2? Then you don't have to deal with the NDIS driver you use windows 32-bit drivers.

What do you use for a boot manager when you need to boot from PE?

try this: Add the following to the end of your sysprep.inf, having only blank lines after [sysprepMassStorage] [Sysprep] BuildMassStorageSection=yes [SysprepMassStorage] Run sysprep from the system command prompt. using sysprep -reseal -mini -pnp nosidgen - does not reset the SID (System ID) activated - does not reset the 30 activation grace period

Actually it is a problem with permissions in the registry where sysprep puts the critical device settings for the mass storage controllers. Easiest way to get around it is as follows: Open CMD window. type: at 13:06 /interactive cmd.exe where 13:06 is one minute ahead of the current system time. A new CMD window will open which is running under the SYSTEM account header will be 'c:\windows\system32\svchost.exe' run sysprep with your desired switches from the new CMD window.

You won't see them in a CMD windows when at c:\ only when in a sub directory, like c:\windows. C:\ has no parent directory (..) As far as I know it is available in any version of windows, and has been around ever since subdirectories were supported by DOS. Some third party file explorers still show . and .. as available folders, not sure how to get Windows Explorer to do it.

Open a command prompt, change into a sub directory and list the directory contents. You will see two directories listed first '.' and '..' '.' refers to the current directory, '..' refers to the parent directory.

With vista there is not much to do, just get it configured the way you want it, add drivers image and deploy. With XP you need to either know all of the hardware you are deploying to will be either ACPI Uniprocessor or ACPI multiprocessor HALs and build your image on a Multiprocessor HAL system and then configure your sysprep file to downgrade it to a uniprocessor HAL which will then upgrade itself to multiprocessor if needed, or script in HAL replacement and build your image as ACPI standard and replace the HAL if required manually (or scripted) before you boot to the image. You will also need to add and SATA/SCSI drivers that are not included with XP that you may encounter to the sysprep massstorage section to have them added to the critical devices database so that windows can boot from them.

I charge $60 hour US. 1 hour minimum. For what you say you did I would charge $120-$180.

it will log to the event viewer, look under the winlogon events.

They must have something that is still running fromthe CD, or that was not transferred to the ram disk before running then. There is a file on the cd that is in use which is why it won't eject. Couldn't tell you which one it is and there isn't going to be an easy way to find out either.

Yes, PE 2 is out of the WAIK. So since that is out, check the winpe help file from PE2005, search the index for 'Ram disk' and read the 'Booting windows pe from from ram disk' article.

I have not found anything to password protect PE other than creating you own application. If you find something let us know but this has come up numerous times over the years and there has never been a good solution.

Working fine here on FF 2.0..0.8

Do you have your PE loading into a ram drive? Otherwise you can't eject that cd for that version because it needs the CD. You could try PE2 which is based off of vista, it loads into memory automatically and then you can eject the cd, but you will need at likely 384mb of memory for everything to work right. Less that that and certain script functions and procedures don't work.

How much memory is in the machine you are testing this on? I have found you need a MINIMUM of 384mb for many things to work right in PE2, 512mb is probably better.

I was a PC Technician for 7 years in a service department. 50% of the job is "fixing" the user not the computer. They expect the computer to be doing something it doesn't, or to do it ina different way than it does. A lot of the time you are just explaining technology to the technically challenged. Problem solving (troubleshooting) skills are the the most needed skill in a PC Tech position. If you can't figure out how to troubleshoot and fix a problem all the tools in the world aren't going to help. I was a maintenance supervisor with an apartment complex before I became a PC Tech, I hadn't even touched Windows 95 yet and it had been out for a couple of years. But I was able to demonstrate good troubleshooting skills and the ability to figure it out which got me the job.

The instructions in my guide do not create a hardware independent image. Only bootable media from which you can create and deploy image files from. You will still need to deal with hardware compatibility issues like, HAL and MSD drives in XP. If your WinPE cd is not booting up it may be an issue with not enough memory on the booting machine or an issue with a driver you added.