/build/static/layout/Breadcrumb_cap_w.png

Which runs first: sysprep login cmds, post install tasks, win7 setup scripts

I'm doing a syspreped install of Windows 7.

Currently I have my unattend file execute a bat file that joins the domain and restarts the computer as part of the synchronous first login commands. (can't use UNATTEND JOIN cmds in unattend.xml because computer prompts for name)
I also have a .cmd in windows\setup\scripts to delete my unattend.xml because it has passwords.

both of these work very well.

however, I would like KACE to do some (alot of) post-install tasks for me on first login and if I try to execute my bat file as a post install task instead, it just doesn't seem to run properly.
The thing is my shutdown is on a timer and rather than guessing at how long it would take to install all my post install tasks. I want to guarantee that restarting is the last thing these comps do.


I was wondering the order in which following things occur
Post-Install tasks
First-login scripts in unattend.xml
windows\setup\scripts\

I think this info could help me choose where to put my batch file

0 Comments   [ + ] Show comments

Answers (1)

Posted by: airwolf 12 years ago
Red Belt
0
If your concern is the reboot, then just move that to its own post-install task at the end of the list. It will be the last thing to run.

To answer your question, post-install tasks run last.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ