I currently have a small handful of PI tasks as well as the PI Task Coverter as a mid-level task, but still, none of my PI tasks are executing at all. When deployment completes, I am left with the C:\KACE directory intact, as well as C:\kcleanup.exe in place. The first, and most important PI task - the K1000 Agent - isn't even running.

Anyone have any tips for how to troubleshoot? I have tried a dozen deployments with the PI tasks ordered every which way to no avail. Is there even a log somewhere I can check to trace the issue? It would be wonderful if Kace threw an error somewhere for this sort of thing. Please advise, thank you!

6 Comments   [ + ] Show Comments

Comments

  • look at the batch file in t he c:\kace directory and follow the steps in it manually.
  • Just curious but is this a Sysprep'd system image?
  • It is a sysprepped image. Although interestingly enough, when I run the run-once coverter's exe, it throws an error saying it will not work on an unsysprepped image. A point of concern may be that I harvested this image with C: as the system recovery partition, and D: as the OS. I'm recapturing the image with C: as the OS as we speak to see if that makes a difference.

    When I run the installcmds.bat file, whatever PI tasks I have in there work just fine. I know it's not a problem with the tasks - something is getting list in translation between my image and the kbox. Will report back with the results from above shortly
    • Definitely recommend only capturing a single partition for Win7 images.
      • Can you elaborate on that a little bit? To be honest, the main reason I'm capturing as dual is because we're migrating to Kace from Altiris and we were using Dual with that
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
  • Mostly because the extra partition requires special scripting and sometimes it can put an extra kink in otherwise perfectly functional tasks. In a large-scale environment, if a computer gets messed up you just image it, you typically don't bother with recovery tools. At least that's how we do it for our 30,000 computers.
  • I'm now capturing only one partition and am still having the same problems. It looks like the runonce converter is still not executing at all.

    What does this exe check to determine if the machine is sysprepped? I really can't imagine why it thinks the machine is not sysprepped. As far as I've known, the machine is either sysprepped, or it isnt, and this image is most definitely sysprepped.

    and just for good measure...................SYSPREPPED.
  • runonceex_converter seems to be checking here:

    $SYSPREP = RegRead("HKLM\System\Setup", "SystemSetupInProgress")
    If $SYSPREP = 0 Then
    $ISSYSPREPPED = "False"
    Else
    $ISSYSPREPPED = "True"
    EndIf

    This value was initially at 0, for what reason I do not know. Even after setting it to 1, however, runonceex_converter is still throwing an error suggesting that the image is not sysprepped.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
Please log in to comment

Answers

0

In case anyone bumps into this issue, and is coming from an Altiris DS 6.9 environment - it could be that the dagent that is installed on your image is preventing something from executing properly during mini-setup. 

I created a new image without the altiris Dagent, and created a brand new unattend file with the new version of the sysprep creator, made some changes to it specific to my environment with WAIK, and captured the image again (as a single partition per a prior recommendation). Either of these, or possibly the combination, seems to have entirely resolved my issues.

Thanks to everyone for the feedback

Answered 07/02/2013 by: dgretch
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity