zorphnog

What kind of drive is D:? Do you have write permissions to it?

If you want detailed information about creating SFX files visit the Application Installs forum.

Many people have put a lot of time and effort into figuring out this problem, and no there is not a solution. The problem seems to be that the installation of certain office components and updates somehow disrupts the underlying framework of WPI (mshta, WMI, ActiveX objects, etc.). As this is an Open project you are welcome to contribute any ideas you may have. Maybe you can figure it out, but at this point I don't think you are in a position to complain about it.

All of them. Since its self-extracting there are no compatibility issues. Its just an executable.

You could use the a PE boot and imagex. imagex is a Microsoft's file-based imaging tool and is available for free as part of the WAIK (Windows Automated Installation Kit). The only difference you'll run in to with file-based (imagex) vs sector-based (ghost) is that you will have to format and partition the disks before applying the image. But these differences are easily overcome. I'd suggest checking out the PE forum.

If I understand you correctly, I think you may have misread. You do not install VMWare on the machine that you are imaging. You use a VMWare environment to make your image. Therefore, VMWare will not affect your image or take up any space because it is not actually on the image.

ntrights.exe, part of the Windows Resource Kit. I haven't tried to use it in PE, but that is the way to modify it via command line.

Do the recovery files have different extensions? Use the file extension to determine what application needs to be executed.

Maybe the switches are case sensitive? Personally, I would take a different approach to installing this since it is really a driver. Extract the driver files and install it via rundll32.exe.

Have you even attempted to use the help files? All of this stuff is in ref.chm. Add the following to your sysprep.inf/unattended.txt: [NetProtocols] MS_NetBeui = params.MS_NetBeui

Are using pxelinux on a Windows or Linux server? I use pxelinux as my boot loader and menu on a Windows 2003 server in conjunction with tftpd32. I've had no problems. If you are attempting this on a Linux server using a built-in tftp server then I'm not sure I can help you, although it seems that tftp is working since you are able to execute the bootmgr. I will say that I have ran into this issue sporadically when burning a PE DVD with ghost image files. I was never able to figure out the cause, but it seemed as if as soon as I had over 4GB on the disc the message you are receiving would appear. Its very sporadic though, as sometimes I get the message and sometimes I don't. Have you edited your BCD at all?

I believe the default account is Administrator, as it is in the command prompt title. After invoking a net user command in the PE environment it shows two accounts: Administrator and Guest. I tried using net user Administrator * to set the password. It reports that the password is saved, but psexec still doesn't work.

What exactly are you trying to do? You want to have the adapter installed and configured? You can set up the adapter in your syspre.inf/unattended.txt file.

I'm not sure if this was a typo or not but I believe the Java entry should have quotations in it, like so: REG ADD %KEY%\045 /VE /D "Java" /f REG ADD %KEY%\045 /V 1 /D "\"%systemdrive%\apps\java\java1_5_0_06.exe /S /v\"/qn" /f And another tip to /qb is to use /qb! which will remove the cancel button. I like to use it this way so that users can see progress, but not cancel the installation.

The search functionality of the forum works well... http://www.msfn.org/board/Cd_switching_Utility_t41821.html

Have you tried using setupmgr.exe to create the sysprep.inf file with an encrypted password? Thats how I encrypt my admin password and then fill out the rest of sysprep.inf manually.

Have you tried adding it to RunOnce instead of RunOnceEx. Adding it to the default user hive should work.

I'm confused. What can you not run during RunOnceEx? You have WMI and Win32 capabilities.

Sysprep is more than just preparing for hardware. One of the main reasons for using sysprep is to generate unique SIDs for local accounts. Basically, if you are using the same image for multiple machines you should use sysprep, especially if these machines are going to be on the same network.

Yeah you can ignore my earlier post. I tested it again and it wasn't the CDROM variable as you already knew. I would guess that SP3 would be the culprit.

I believe he said that he installed all packages.

In my experience, I've found that you have to use the full path to the hta file for it to launch. Additionally, you shouldn't need to move mshta.exe as I just call it from anywhere (i.e. - mshta.exe X:\Windows\system32\wizard.hta). You can disable the "Press any key..." functionality by removing bootfix.bin from the boot folder of your CD. You can add a boot menu using bcdedit to modify your bcd and placing that on your boot partition. Just search for bcd and bcdedit to learn more.

I understand that, I like to see what is being installed as well. Thats why I set automatic updates to "notify but don't download or install". I can see whats missing and choose what to download and install. I just really don't like using the web interface, but thats just my opinion.

RunOnceEx? http://unattended.msfn.org/unattended.xp/view/web/31/

What do you do in your sysprep process? Are you adding drivers for the real machines before you sysprep? Are you using the BuildMassStorage section in your sysprep.inf? Are you using bootsect.exe to create your boot sector after you format the drive and before you apply the WIM? Your problem lies somewhere in your implementation.