RDP loading drivers which require user intervention - how to eliminate?

[Greg Swedenborg]

I am developing a server build and have included the Support Pack version 7.20a for Windows 2000.

After it runs however, I am still getting prompted for driver installs after the reboot. Specifically, it loads the 82801EB LPC interface Controller 24D0 (PCI.sys driver) as well as the E7525/E7520/E7320 PCI Express root port-A0 (isapnp.sys driver). There are some drivers that load in between these two, but the 2 mentioned here actually install the first, then require user input to click the finished button at which time the others run then stops again on the second driver listed (isapnp.sys).

So far I have only run this on the 380G4 but I assume it will happen on the 360 as well. It has not done this with our previous Windows 2000 builds and it does not do this on the Windows Server 2003 install.

I would like to find out how to automate this or eliminate the need for user intervention of the drivers.

[Gopi Sekar]

I am not a windows expert. All i can give for you now is, why don't you use 7.30 support pack version which is the latest. See whether it is solving your problem.

Regards,
Gopi

[Adrian Clint_1]

If its not fixed with 7.3 then you may need to configure a PSP driver component.

Go into \express\lib\software
and into each PSP directory
run set.exe and look at the configurable components if its there you right click and configure.