I want to trouble shoot post installation tasks but cannot seem to find out where or if a log file is created during post os deployment.

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



He is referring to postinstall (PO) tasks.  The log file being referenced so far is just for imaging/scripted installs.

There is no log file for PO tasks at this time, unless you create them yourself.

There was a great presentation by Patrick Warme at Konference on PO troubleshooting.

You can find all Konference 2012 presentations here:



Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 01/18/2013 by: cserrins
Red Belt

  • Hey Corey, I would like a copy of that please.
Please log in to comment
Answer this question or Comment on this question for clarity



Is this for kimages or wim files? The logs are in petemp and are numbered by the system_image_id

Also for troubleshooting you can caste an image, do not reboot, go to the main menu and choose recovery.  you can then go to the c: drive and look at the kace directory and the Batch/script files, this may also tell you whats going wrong.

You can also modify the file to exit in the pe env and run it manually after to see what is going wrong.  You can remove kcleanup from the batch so the files remain after imaging for tshooting

Answered 01/18/2013 by: SMal.tmcc
Red Belt

Please log in to comment

kimages - where is petemp?  On k2000 or on the machine?

Answered 01/18/2013 by: mopalach
Senior Yellow Belt

  • if you hover your mouse over the deployment you will get the system id
  • petemp is a share on the K2, you can access via unc path \\k2ip\petemp and authenticate with admin and your driver/restore share password, or if in KBE petemp is mapped as the T: drive.
Please log in to comment

petemp is \\ipofyourk2000\petemp

user is admin and pw is specified in your K2 in Settings:General Settings:Driver/Restore Share Password

Answered 01/18/2013 by: tshupp
Second Degree Black Belt

Please log in to comment