For those that would like some more tech detail:
Setupact.log - setup actions during process
setuperr.log - only the error messages - both these need to be read together, and depending at what poitn the failure was, they may be in different locations!
KB927521 has more
cbs.log - DISM commands - drivers, languages, security updates
setupapi.dev.log - %windir%\inf - driver install
netsetup.log - %windir%\Debug - Domain join errors
Windowsupdate.log - %windir% - Windows update, WSUS or SCCM (SUP) errors
wpeinit.log - startup issues in WinPE - gets deleted after reboot
wdsserver.log - WDS - logging is off by default - KB936625
usmtestimate.log - estimation of space errors
usmtcapture.log or scanstate.log - capturing the data
usmtrestore.log - restore errors
smsts.log - task sequence failures (another log that moves)
drivercatalog.log - inport drivers
tasksequenceprovider.log - save or import task sequences
smspxe.log - pxe issues
smsprov.log - save or import task sequences too.
In SCCM you can enable a checkbox for enable command support, if you then hold F8 during winPE you can get a command prompt to go find these logs. If you have got as far as windows setup Shift+F10. Having the command prompt window open, holds any reboot too.
Common issues:
- Bad computer name - more than 15 characters
- Mismatched product key to image file
- Broken domain join - KB944353
- Deploying with a KMS key! (KMS keys are for machines that provide keys to rest of org)
- Crashes - check for stop errors, you may need to turn off auto reboot.
- WinPE - generally networking related
- SCCM - task sequences, hash mismatch (refresh DP - it is a bug MS cannot reproduce so far)
- Make sure you test all task sequences at least one before deploying
- Make sure packages are present (if not push them out)
Finally he mentioned a tool called SMStrace, which has the option to enter error codes, this can be very helpful.
Posts
No comments:
Post a Comment