bszom

johnhc, what do you see while WPI is installing programs? On my side, when WPI runs for the very first time after the unattended OS install is done, I get the standard WPI window as in your screenshot, but without the "Options" and "Config" options (as it's running from the CD). I then choose which programs I want to install and hit "Begin Install". The WPI interface changes to a much smaller window, listing only the programs being installed and an overall progress bar. This same window is displayed after each reboot, after logon but before the desktop loads. For now I have simply worked around my issue by doing any user-interactive stuff after the first logon, while the taskbar is still visible.

I think the way you've done it is perfectly fine. Another alternative, assuming you're doing an unattended Windows install, would be to put your .reg files somewhere in the <Your CD>\$OEM$\$1\ directory structure. So for example, you could just copy your folder "Printer Scripts" into the $1 directory. This will cause "Printer Scripts" to be copied to the system drive (usually C drive) when Windows is installed, allowing you to reference your .reg files as follows: "%SYSTEMDRIVE%\Printer Scripts\<whatever>.reg". Please note that you must set "OemPreinstall=Yes" in your WINNT.SIF for the contents of <Your CD>\$OEM$\$1\ to be copied to the system drive. More information: WINNT.SIF Reference $OEM$ Distribution Folders

OK, unfortunately Border Type and Style did not have the desired effect. I should clarify: I do see the taskbar after the very first logon, so when WPI runs for the first time. However, a few of the programs I am installing require me to reboot the machine. After a reboot, I log on and WPI resumes installing, but the taskbar is no longer visible. Any ideas?

Hi Kelsenellenelvian, that is the $oem$ package that I am using. Apologies - I wasn't trying to offend, I was just trying to say that if Border Type and Style are indeed responsible for the visibility of the taskbar when WPI is installing programs, then it would make sense to state this explicitly in the documentation. Don't assume that I'm too retarded to read the documentation that is there (though I don't blame you for the urge to shout RTFM).

Hi johnhc, I'll certainly give that a go. I was under the impression that the Border Type and Style applied only to the WPI "configuration window" as such. If these settings do affect the visibility of the taskbar as well, then it would make sense to mention this somewhere. Unfortunately the WPI documentation is a bit lacking in this regard. Anyway, I'll try it out and report back. Thanks! PS: Yes, the explorer switches do have commas in them. Please see here.

Sorry if this has been asked before, I had no luck with searching. Is it possible to have the taskbar visible while WPI is doing its thing after logon? I need users to be able to access things like windows explorer and a few others. Until now I've been using a workaround, by launching specific control panel windows from a batch file, for example. I tried to do the same thing with explorer, but it just seems to hang. Even the batch file fails to continue processing after it tries to launch explorer.exe. I can see that the process has been started when I open the task manager, and killing it allows the batch file to resume, but no explorer window in sight. Please note that this is not the same question as has been asked a few times before, i.e.: getting the taskbar to show while you are configuring WPI. I am talking specifically about when WPI runs after OS installation and logon. Here is a sample batch file that opens the network connections control panel (which works) and then explorer (which does not work): ECHO Start configuring network connections: PAUSE %SYSTEMROOT%\system32\ncpa.cpl ECHO. ECHO Start performing domain controller promotion: PAUSE %SYSTEMROOT%\explorer.exe /e,/root,%SYSTEMDRIVE%\SetupSupport\Domain Controllers\ ECHO. ECHO Reboot and begin installation: PAUSE I assume this has something to do with where in the OS load/logon sequence WPI takes over. Perhaps there is a way to only start WPI a little later? P.S.: I'm doing unattended Server 2003 installations + WPI.