/build/static/layout/Breadcrumb_cap_w.png

Running Postinstallation Tasks Manually (Without Doing Entire Scripted Install)

Another one I covered during my support call yesterday. Again, not much written up on this, so hopefully this can help someone.

John
________________________________

Running Postinstallation Tasks Manually
________________________________

Facilitates running postinstallation tasks manually without having to go through entire scripted install

* use to save time while troubleshooting postinstallation tasks

* can change postinstall tasks in a scripted install (i.e. change order, adjust, etc),
save scripted install, and then follow the steps below to test effectiveness

* particularly ideal in concurrence with virtual machine
* snapshots & ability to roll back to pre-postinstallation state
_________________

From the target machine (for all steps below):

1) Complete the scripted install, to the point of postinstallation tasks (or where they break)
* reboot as necessary to clear stuck installs/processes
_________________

2) Browse to K2000 oemfiles directory:
\\ikbox\peinst\oemfiles
_________________

3) Determine folder used for scripted install
* K2000 - Deployments - Scripted Installations - click on target name

* path in browser's address field will reflect \\ikbox\peinst\oemfiles\#
* i.e. http://ikbox/setup_detail?boot_image_id=5
= \\ikbox\peinst\oemfiles\5
_________________

4) Copy these files into C:\Windows\System32 to avoid path issues:
\\ikbox\peinst\oemfiles\#\$OEM$\$1\KACE\bin

* cmdhide.exe, kb2kping.exe, kdevpath.exe, watchdsp.exe
_________________

5) Copy contents of $OEM$\$1 folder to C: on target machine
* i.e. \\ikbox\peinst\oemfiles\5\$OEM$\$1 (KACE folder & kcleanup.exe)

* Note
* \\ikbox\peinst\oemfiles\#\slipstream is used for drivers

_________________

6) Copy \\ikbox\peinst\oemfiles\#\$OEM$\RunOnceEx.cmd to the Desktop on the target machine,
double-click to run, and reboot the target machine

* Notes
* \\ikbox\peinst\oemfiles\#\$OEM$\RunOnceEx.cmd contains all of the commands
that will be injected into the registry and will be scheduled to run following
the reboot prior to the postinstallation tasks

* a script could be setup to facilitate auto-login following the reboot
_________________

7) Log back into the target machine and the postinstallation tasks will run
* adjust postinstallation tasks and repeat as necessary
_________________

solution provided by Gerald Mack
_________________

2011-12-21 - jv

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

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