Scripted installation - K2000 reboots in a middle of postinstallation task
Hi!
I have a bat-script in a postinstallation task, it`s start fine BUT K2000 thinks the installations is done and restart the computer when the scripts is running. Can I delay the restart or something ?
Many thx!
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
SMal.tmcc
9 years ago
can you share your bat script?
Comments:
-
net use x: \\10.102.130.18\c$
set source=X:\Win7\PSTools /y
mkdir c:\PSTools
set destination=C:\PSTools
xcopy %source% %destination%
C:\PsTools\PsExec.exe /accepteula \\10.102.130.18 "C:\updates\cmd\DoUpdate.cmd - Swede 9 years ago
Posted by:
SMal.tmcc
9 years ago
try this
start /wait net use x: \\10.102.130.18\c$
set source=X:\Win7\PSTools /y
mkdir c:\PSTools
set destination=C:\PSTools
start /wait xcopy %source% %destination%
start /wait C:\PsTools\PsExec.exe /accepteula \\10.102.130.18 "C:\updates\cmd\DoUpdate.cmd
Comments:
-
also another thing you can do since you own a k2000 is go to \\ikbox\peinst\winpe_build\amd64\windows\system32 (or x86) and get the file ksleep.exe, add that to your image and that allows you to easily put delays in your scripts (c:\temp\ksleep.exe 30) causes a 30 second delay between steps. - SMal.tmcc 9 years ago
-
Thx, first I will test start /wait commands, have made the changes now and start a new installation. Hopefully it will work now! =) - Swede 9 years ago
-
should do it, pretty sure psexec was being called before everything was copied. I have ran into that problem in the past with some of my scripts - SMal.tmcc 9 years ago
Posted by:
Swede
9 years ago
Did not work with start /wait, scripts start fine, but after about 15-20 sec computer restart and the installation is done.
Posted by:
Swede
9 years ago
Have add one double quote now, maybe is the command file is the problem, not the batch file ?
Comments:
-
You are right it is huge. Checking it in between image tests and I just got back from Vacation so still getting caught up, may take me a few to scan. It could be in the cmd especially with all the err checks that skip to other areas. Something could be causing it to jump to the end and miss major parts very easily - SMal.tmcc 9 years ago
Posted by:
SMal.tmcc
9 years ago
also looking at network share calls from explorer should look more like
start /wait C:\PsTools\PsExec.exe /accepteula \\10.102.130.18\C$\updates\cmd\DoUpdate.cmd
Posted by:
Swede
9 years ago
Maybe I should skip call the cmd-file, and call the Updateinstaller.exe (WSUS) ?