I am trying to create a system image and having a problem running my post installation tasks. The system image is a Windows 7 image that has been sysprep'ed. Do I need to add something to the sysprep file to kickoff the post installation tasks? My tasks are pretty simple:

  • Rename computer
  • Reboot
  • Install DameWare Mini Remote Control
  • Install KACE Agent
  • Join Domain and reboot

If I look at my C drive I have a KACE directory with all the tasks in there so I'm assuming they are not getting run at all.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
@jrscribner

Go to the system image details page and click on the browse image button. Go to c:\windows\setup
Is there a scripts directory in this folder?

If so, delete that folder, close the folder and commit changes. Then try again.

Let me know,

Corey
Answered 05/27/2011 by: cserrins
Red Belt

Please log in to comment
0
@Corey

I checked the C:\Windows\setup directory and the only thing in that folder is directory called State. I am going to go back to the basics and use a simple sysprep file and only a single post installation task and see if that works.
Answered 05/27/2011 by: jrscribner
Purple Belt

Please log in to comment
0
@Corey

I've determined that it is running the Post Installation Tasks up to the point of a system reboot (i.e. after naming the computer) and then not running any of the remaining tasks. I've read other threads that say I need to reinsert a run command to kick off the remaining jobs but I'm not sure how to do this.
Answered 05/31/2011 by: jrscribner
Purple Belt

Please log in to comment
0
I opened support case and there solutions was listed in the KACE knowledge base (http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=763&artlang=en) Don't know how I missed that one.. I kind of figured their solution would involve the steps they outline in the KB. It seems like a lot of steps to complete a simple task, I wish the Post Installation Tasks would pickup where it left off after a reboot. I think my solutions will be to inject the computer name into the sysprep process to eliminate the reboot to set the computer name, then I only need the final reboot.
Answered 06/01/2011 by: jrscribner
Purple Belt

Please log in to comment
0
I agree I just did what was said in the KB but still cannot rename the machine when joining to the domain.
It does seem a lot of work for a post install.
Answered 06/02/2011 by: sen
Senior Yellow Belt

Please log in to comment
0
@sen

Following their suggestion works fine for me it is just a lot of steps. My testing on injecting the name into the Sysprep file is going really well you might want to explore that as an option then the computer is already named and all you need to do is join it to the domain. After I clean up my sysprep injection script a little more I'll share it.
Answered 06/02/2011 by: jrscribner
Purple Belt

Please log in to comment
0
KBOX will not run postinstallation tasks after a reboot unless you specifically inject the proper registry keys to run something else after a reboot. I have been told by multiple Kace Techs and Engineers this is a flaw in Win7, but I don't see it that way. It's a flaw in the KBOX design that I thought would've been fixed by now.
Answered 06/08/2011 by: dyehardfan
Second Degree Blue Belt

  • What Registry key do you need to inject??
Please log in to comment
0

@dyhardfan: What registry keys do you need to inject to kick of the post installation tasks??

Answered 06/20/2012 by: tpana
Senior Yellow Belt

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

Share