Ctrl-X

It looks like sysocmgr is started multiple times, but I can't figure out why that is happening. You'll have to be more specific. The first "runas" script is used to start the second script, right? So that second one is the "\\server\share$\Script.vbs" script, correct? What is the name of the first script and how does it get started?

Have you made the XP station a member of the same domain as the NT server?

The "permission denied" error is generated by line 13 in the script. This is the line where you're trying to create the "c:\windows\inf\wmdtocm.txt" file, so presumably the user running the script doesn't have the necessary NTFS permissions to create the file.

Run Risetup.exe on the RIS server and select the "Check this remote installation server for errors" option.

You've left out a space in the runas statement: WshShell.Run "runas /user:administrator@domain""cscript.exe \\server\share$\Script.vbs""" This should be: WshShell.Run "runas /user:administrator@domain ""cscript.exe \\server\share$\Script.vbs""" Note the space after "administrator@domain".

Check the policy settings in Administrative Templates \ Windows Components \ Internet Explorer and below, both in Computer and in User Configuration.

Don't think so... The last user name that is displayed by default in the logon window is read from a single-string registry value, so it's most likely not possible without replacing the default MSGINA.DLL.

Yes, that's why I linked to an article that applies to Windows XP in my last post: How to remove and reinstall IIS 5.0, 5.1 and 6.0

Run Older Programs on Windows XP

The article I linked to appears to be applicable to Windows server versions only. The easiest solution for you would probably be to remove and reinstall IIS. This would recreate and configure the necessary accounts. Instructions can be found *here*. Make sure you backup your configuration first!

I dunno, have never tried it... I prefer to integrate service packs.

That would generate an error message; it wouldn't cause Setup to hang. I've seen buggy drivers cause this behavior; especially Realtek NIC drivers spring to mind. Start with the working .sif file and change the Drivers subfolders one by one, testing every time, to see if you can pinpoint the offending driver.

Consider installing the Service Pack from Cmdlines.txt or RunOnceEx.cmd instead.

Looks like your IWAM-account may not be configured correctly. Check PRB: Configured Identity Is Incorrect for IWAM Account for a solution. By the way: next time, click the link(s) in the event description. Chances are you'd find a solution immediately.

http://www.microsoft.com/technet/security/current.aspx

The Unattended Windows Guide has all the information you need to build your own customized XP installation CD. I doubt that anyone here is going to build one for you...

Once again: the error message refers to the event log. You should be able to find more information there. Without a detailed description it's impossible to solve this problem. Find the error message in the event log!

When booting from PXE, the client doesn't actually issue a DHCP request but a BOOTP request. Is the DHCP server configured to respond to BOOTP requests as well?

In short: Create the new GPO and edit the settings as needed; Select the "Scope" tab for the new GPO, remove "Authenticated Users" from the "Security Filtering" box and add the group(s) and/or user(s) you want the new GPO to apply to; Link the new GPO to the desired OU, placing it above the original GPO so it has higher priority. Refer to the article I linked to earlier for details. If you need more information, Google for "group policy security filtering" to get some more articles on the subject.

It doesn't... I've tried

I'd create a primary partition on the 2nd hard disk. Don't make it active unless you want to boot from it.

I'm not sure, but my guess would be the Application Event Log. If it's not there, try the System Event Log.

Add the "hash" command to the newftp.txt file to turn hash mark printing on.

I don't think so. They are probably copied down just fine, but then get overwritten by the original files during Windows setup. You may be able to replace them after Setup is done by running a copy action from one of your post-install scripts.

If those files are subject to Windows File Protection, you won't be able to replace them. What files are you trying to replace and where are they located?