OS Deployment - Analyzing logs

Version 7
    Share This:

    It's not always easy to know where to look at o find interesting logs when your OSD project fails.

     

    1- FPAC logs:

    The first thing to do to check logs is to know your project number:

    - Compile your project

    - Select your project in the console, click on the tab "Log File" and look for a line like this one at the very begining:

    Wed 08/28/2013 - 15:13:44.06: I   ProjectId=  1010

     

    If the project compilation fails you'll find logs in \\_YOUR_OSD_MANAGER_\\c$\Program Files\BMC Software\client\data\OsDeployment\log\ (e.g. \\10.5.152.92\c$\Program Files\BMC Software\10.1\client\data\OsDeployment\log\build.amd64.1008.log) or simply select your project in the console, click on the tab "Log File".

     

    Capture or deployment logs will be found in \\_YOUR_OSD_MANAGER_\_YOUR_PXETFTP_SHARE_\log\_YOUR_PROJECT_ID_ (e.g: \\10.5.152.92\pxetftp\log\1008). These logs will probably tell you why you couldn't deploy or capture (e.g. not enough disk space on the share you want to copy the captured wim to)

     

     

    2- Windows logs:

    The OSD manager downloads some panther logs from the target device since FPAC 11 but sometimes the project fails before the module can download them so it might still be interesting to know where you can find them:

    - XP :

    C:\Windows\setupapi.log (logs driver installations)

    C:\Windows\setupact.log (logs install actions)

    C:\Windows\setuperr.log (logs install errors)

    C:\Windows\Debug\netsetup.log (logs domain joins)

    - Vista/7/2008:

    C:\windows\Panther\setup*.*

    C:\windows\Panther\UnattendedGC\*.*

    C:\windows\System32\Sysprep\Panther\setup*.*

     

    In some case (when the runsysprep.bat would not work) i have found it usefull to have a look at this log:

    %SystemDrive%\Windows\DtcInstall.log

     

    To be able to read these logs if you only have the MS-DOS windows available you'll have to:

    - go to the project properties and select "None" instead of "Shutdown" or "Reboot", then recompile and restart the device or rerun the runsysprep.bat.

    - when the project will have failed you'll be able to use the MS-DOS window (if not you might want to try "Ctrl + Tab" or "Shift + F10 i think, to launch a new one)

    - type notepad in and edit the logs you're interested in.

     

     

    Note:

    - This article applies to FPAC =< 11.6.

    - This article should be updated for 11.7 starting from the fact that the OSD logs are now stored in the device's main log folder

     

     

    Please consider marking this post as correct or recommandable if you found it usefull.