Ctrl-X

Add "AutoConfirm=1" to the [Display] section. Add "UnattendSwitch=Yes" to the [unattended] section. Most of these should be solved by setting UnattendSwitch to Yes (see above). The Install.cmd probably isn't executed because you've set EncryptedAdminPassword to Yes. This disables the Autologon feature.

This sounds like a hardware issue to me... Have you tried using another drive and/or CD?

Start menu folders are folders like any other and can be created using the "mkdir" (or "md") command. For instance: to create a "My Apps" folder in the All Users profile Programs folder, use mkdir "%ALLUSERSPROFILE%\Start Menu\Programs\My Apps" You can't create shortcuts directly from the command line or a batch file without using a third party program such as XXMKLINK.

When does this happen exacly? When you left-click the item? Single or double? What happens when you right-click the item?

See if installing the User Profile Hive Cleanup Service solves the problem.

The latest SMS 2003 OSDFP Update adds support for the Vista WIM file format. Don't know if the OS image capture component uses the same format though.

When you create this .zap file do you just create the contents as in the article then save that file with the extension .zap (just thought to check as i assume ths is the case) Yup

What cluberti means is: remove a test computer from the domain by joining it to an existing or a new workgroup. Create a local user account and make it a member of the Network Configuration Operators group. Log on using that user account and see if you can change the IP address. If you can, then the problem is caused by one of the domain policies.

Right, that one can't be ignored except through the registry tweak mentioned by cluberti. Don't forget to configure whatever it was that needed configuring though!

RunOnceEx.cmd does work with Windows 2000, as long as you add REG.EXE to the installation image. AFAIK it's included in the Resource Kit tools.

How to publish non-MSI programs with .zap files

Yes it does. The ActiveX control kill bit is supported by Internet Explorer 5.01 SP2 and above, so as long as you're running a supported IE version, the operating system version doesn't matter.

Although the MS KB article does not explicitly list it, I assume this works with Win 2003, too. Does anyone know for sure?It does

Could the disabling of any of these services be the cause of your networking problems?

Someone posted a quite extensive description and troubleshooting guide for this error at Experts Exchange.

How to publish non-MSI programs with .zap files

At the bottom of the "Configure your server" windows, there's a "Don't show this again" option. AutoLogon is explained in http://unattended.msfn.org/unattended.xp/view/web/27/ (bottom of the page).

"Only" 670 Most of the suggestions seem to be permission related. Have you checked these? A fresh install is no guarantee for a trouble-free system, as you have now discovered.

XP LogonUI & Boot Screens forum

Google is your friend

I wouldn't be surprised if SP3 turns out to be nothing more than a security update rollup, just like they did with Windows 2000.

As long as you don't distribute your modified version I think it's allowed. But if you want to be sure, contact Bart himself at http://www.nu2.nu/contact/bart/. Also, there's a license agreement at http://www.nu2.nu/pebuilder/pebuilder.txt.

I still suspect the CD: http://forums.techguy.org/windows-nt-2000-...xp-install.html

While testing, remove the "/s" after "regedit.exe". That way you'll get feedback when the command runs. Regedit might not be able to find the settings.reg file as gugutz suggested.

Sounds like a policy setting is keeping you from changing the home page... If you're familiar with group policies, run gpedit.msc and see if any restrictive policies have been set. Did you install Windows and the other software using your own media? What version of IE are you running? If it's IE 7, did you install it yourself or was it installed via Automatic Updates?