Ctrl-X

Contact your local Microsoft representative. I'm sure they'll be able to provide a new CD.

A faulty printer driver could cause all sorts of problems with the Print Spooler. I'd start by upgrading all printer drivers to the latest & greatest version.

These are usually devices that were once connected to your computer, but not anymore. Windows "remembers" these devices so they can be reactived quickly when they are reconnected. You can always try; they will automagically come back if needed. If that were the case, these USB sticks would also appear as hidden devices under the "Disk drives" node. But just connecting a single USB stick to three different USB ports will already result in three different generic volumes. The same goes for USB mice, keyboards, etc. Hmmm, it's possible that this is a device that is present, but is intentionally kept hidden by Windows. In "Network adapters" and "Sound, video and game controllers" you can usually find many examples of such devices. Absolutely.

If these systems are in an Active Directory domain, you can configure this through Group Policy: User Configuration / Administrative Templates / Control Panel / Display. You'll need to set the "Screen Saver", "Screen Saver executable name", "Password protect the screen saver" and "Screen Saver timeout" options.

There's no need to add/integrate DirectX 9.0c... It's included with XP SP2.

I see, thanks! Can't find any information about this option in the Preinstallation Reference though... After a bit of searching I'm guessing this is a leftover option from the Windows NT 4.0 days?

What does the AutoConfirm=1 in your winnt.sif mean? I can't find any reference to this in the documentation. I'd leave out the registry entries you mentioned in hivesys.inf if I were you; as far as I know these shouldn't be necessary and may very well be the cause of the problem.

I'd be surprised if Asus didn't include the HDA bus driver with their driver package... Unzip the package and look for a file named kb835221.exe or kb888111.exe. If it isn't included, the update can be downloaded from various locations; *here* for instance.

It looks OK... Did you get an error message?

You could remove the service manually from the registry, but you might try removing it using InstSrv (part of the Windows Server 2003 Resource Kit Tools).

If this is a Windows XP image, you'll need the "special" e1000325.inf file in the i386 folder. There's another one for Windows 2000 which is called e1000nt5.inf, so if this is a Windows 2000 image you'll need that one. You say you've removed the drivers from the i386 folder. Does that mean you removed the corresponding .sys file as well? You'll need to keep that; just replace the "real" .inf file with the "special" one. Don't forget to restart the Remote Installation service (BINLSVC) on the RIS server after replacing the .inf file in the i386 folder. BTW: in my opinion this question belongs in the unattended RIS installation subforum.

Press Ctrl-Alt-Del twice from the Welcome screen (source).

That's correct, you won't be able to add users to the group locally (actually you can, but they will be removed again the next time the GPO is applied). You could add the domain admin (or the Domain Admins group) of the child domain to the GPO as well. Do I understand correctly that you add only the regular user of each workstation to the local admins group? You won't be able to do that through a GPO... You'll probably have to script it one way or another like allen2 suggested.

There's about 20 different suggestions on the page I linked to that you can read without having to subscribe. If people refer to MS Knowledge Base articles, just type the URL yourself: http://support.microsoft.com/kb/<article ID number>.

No need to shout! First of all, you never mentioned T-37 in your post. Second, you didn't post your entire winnt.sif file, so there was no way of knowing what's in it and what isn't.

Did you even read my answer to your question?

No, for RIS setups it definitely needs to be outside the i386 folder. It's in the article I linked to earlier in this thread: How to Add OEM Plug and Play Drivers to Windows XP. I admit it's confusing...

Now I'm confused Is the OEM Reference at the Unattended site for RIS or "all other installation types"? It shows the $OEM$ folder at the same level as the i386 folder. I know... Apparently the information in the OEM reference is correct, or it would have been corrected long ago. But according to Microsoft documentation this folder structure is for RIS installations only. We have been using RIS for over five years now and I know for a fact that the $OEM$ folder needs to be at the same level as i386

Check out this list of tips.

The maximum number of simultaneous connections to a Windows XP Pro system is ten. However, if that were the problem, you would get the error message "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept" (check Inbound connections limit in Windows XP). Are you sure the clients that can't connect to the share have all the necessary network components installed (Client for Microsoft Networks, correct network protocol etc.)?

I like GSAR better... Personally I think it's easier to use.

It's the other way round... For RIS installations, the $OEM$ folder should be at the same level as the i386 folder. For all other installation types, it should be a subfolder of i386. Check How to add OEM Plug an Play Drivers to Windows XP for details.

Add "OemSkipEula=1" to the "[unattended]" section.

If that's the exact statement you're using, you've left out the "/f" after "for". But I've tried it myself and I'm getting the same error, so I'm afraid you're right. What string are you trying to retrieve from the output of the "ver" command? I'm not too familiar with the use of "sed", so I can't really figure it out myself.

Sounds like a problem with the SCSI driver disk... Are you sure the disk isn't damaged? Are you using the correct driver version? Have you tried downloading the latest version?