The re-image process follows almost exactly the same flow as the capture process from the beginning to getting into Windows PE. After in Windows PE though differences start to occur. After resuming the MDT task sequence and running more tasks, it will then turn control over to Windows Setup, which will actually install and set up the new Windows OS. During this process errors can also occur, and will be more formal. This will occur during dialogs that look the same as normal Windows installation. If errors happen here, the same flow follows to try and look at the logs and search for corresponding errors during Windows setup. Log files related to Windows setup can be found in many places, separate from MDT logs.

 

Potential Windows Setup Log Locations:

C:\Windows\Panther
C:\Windows\Panther\setuperr.log
C:\Windows\Panther\miglog.xml
C:\Windows\Panther\PreGatherPnPList.log
C:\Windows\setupact.log
C:\Windows\setuperr.log
C:\WINDOWS\INF\setupapi.dev.log
C:\WINDOWS\INF\setupapi.app.log
C:\WINDOWS\Performance\Winsat\winsat.log

 

During the middle of Windows installation, another issue can come up which is after the new OS has been installed, then we reboot into that. If drivers are again an issue, there will be trouble booting into the new OS. As with booting in to Windows PE, it will fall back if errors occur. In this case it will fall back to booting to WinPE, so that you can examine logs, and retrieve the OS Driver Binding Grid, which is osgrid.ini.update and can be found in the BigFix client logs directory.

After booting into the new OS and completing the installation, a second multiple action group will run which will clean up the re-image process. This is targeted at machines with a certain registry key that was set up during re-image. This will then clean up files, and normal BigFix action debugging applies if this action fails.