sysprep "new hardware" behaviour

demesmaeker

Reputable
Jun 4, 2014
2
0
4,510
Hi there,

I made an image with WIndows 8.1 (Sysprep) using an unattend.xml and a cmd file that does a few things like activating Windows & Office and installing certain programs after an internet connection has been established.

With Windows 7, sysprep installed all drivers before giving you the chance to log into the computer.
With Windows 8.1, sysprep starts installing new drivers, but already gives you the chance to write computername & username, and log into the computer while Windows installs all drivers

The result is, that not all drivers are already installed onto the computer yet when a user logs on to the computer. When the batfile then starts, it also installs a program with a driver in it (for a Touch Screen board for teachers). This messes up the PNP process (at least until the next restart)

Now I wonder about two things...

1) Is it possible to do a query (with or without command line third party tools) to check if Windows is busy installing hardware? I tried finding the PNP process with tasklist, but could not find a process that was constantly busy while installing hardware. A few PNP dlls & exefiles opened and closed several times, so I could not just check for that.
I tried finding a registry key that might tell Windows that it is busy doing PNP

2) Is it possible to make the installation of Windows wait before continuing until all hardware is installed? Like Windows 7 did? This would also solve the problem.

I know that I could just make the computer wait 5 minutes, but I rather want to solve it a better way.

Thanks in advance for any help or tips!

Friendly greetings,
Demesmaeker


 
Solution
Are you using FirstLogonCommands or LogonCommands? FirstLogonCommands should be used when you need an operation to complete before the next operation is undertaken.

A better way to do it would be to use the Microsoft Deployment Toolkit (MDT) to automate the application installation. With MDT you could add a pause, install after deployment, reboot the computer after installation, create deployments to varied devices with different drivers or different sets of applications, and quite a bit more. MDT is the recommended way to deploy Windows. If you are unfamiliar with MDT, I highly recommend watching the Windows 8.1 Deployment Jump Start, it really shows you what MDT can accomplish.

WinOutreach2

Distinguished
Mar 3, 2011
413
0
19,160
Are you using FirstLogonCommands or LogonCommands? FirstLogonCommands should be used when you need an operation to complete before the next operation is undertaken.

A better way to do it would be to use the Microsoft Deployment Toolkit (MDT) to automate the application installation. With MDT you could add a pause, install after deployment, reboot the computer after installation, create deployments to varied devices with different drivers or different sets of applications, and quite a bit more. MDT is the recommended way to deploy Windows. If you are unfamiliar with MDT, I highly recommend watching the Windows 8.1 Deployment Jump Start, it really shows you what MDT can accomplish.
 
Solution