KBE Post Install Task with Win 7 Scripted Install
I am trying to run a couple post install tasks with a Win 7 scripted install before reboot while it is still booted to the KBE, but it appears that the Windows setup is actually rebooting before the post install tasks can run. Anyone know how to get the setup to not reboot and let the K2000 handle it after it runs the post install tasks?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ncsutmf
13 years ago
Yes, and it shows up in the correct spot for a Windows Boot Environment item.
I was watching it as it went, and am fairly certain that the windows setup did the reboot before any of the post install tasks could launch (in this case it was just one task).
I know that the setup.exe could run with a /noreboot option, but not sure what the full command line options the k2000 is using for it.
I was watching it as it went, and am fairly certain that the windows setup did the reboot before any of the post install tasks could launch (in this case it was just one task).
I know that the setup.exe could run with a /noreboot option, but not sure what the full command line options the k2000 is using for it.
Posted by:
ncsutmf
13 years ago
No, I wasn't running a setup.exe, I was referring to the setup.exe from the OS install point on the K2000. However, it appears the issue was with the script that was being called, it was giving an error but it wasn't an error that would have caused the scripted install to prompt me to ask whether to continue or not, and it was happening so fast that it appeared that it was not running. What threw me off is that same script worked fine with K-images on our trial appliance. Still having some issues though, for some reason, now it is not rebooting at all when it is finished. But I have some things I am trying first before I mention the details here.
Posted by:
ncsutmf
13 years ago
It looks like the no-reboot issue is resolved.
I had a postinstallation task that was a couple files with a .cmd file to copy the other files to another location as well as create some directories. The command line was "script.cmd" and when I changed it to "call script.cmd" I believe that is when it started rebooting when finished again.
I had a postinstallation task that was a couple files with a .cmd file to copy the other files to another location as well as create some directories. The command line was "script.cmd" and when I changed it to "call script.cmd" I believe that is when it started rebooting when finished again.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.