However, If i have a lot of files to copy this can cause a wait while robocopy runs. I would therefore like to use the run() command instead and make robocopy not slow my script down.
Code:
run '\\domain\netlogon\robocopy src dest /b /njh /nfl /ndl /E /sec /R:0 /purge /log:c:\log.txt'
The problem is that this only seems to work intermittantly. It always runs without any KIX errors but robocopy doesnt seem to be doing anything sometimes. Soemtimes the robocopy log is normal, but usually it is just an empty file - and robocopy has not run (the files are not there).
If i manualy run the script with run()'s with a logged on user it then always works.
Am I missing something or does windows do something like terminating all my startup script processes automatically once the end of the main script has been reached? Is there any way round this? Can anybody suggest an alternative to run()
#193771 - 2009-05-1108:49 PMRe: using run() instead of shell() in startup scripts (with robocopy)
[Re: Tomarse]
NTDOCNTDOC Administrator
Registered: 2000-07-28
Posts: 11634
Loc: Space
Well you could kick off another script with a run command and in that other script you could shell out (just do it all silently so that the user doesn't know that its running)
Then let the first script exit out on it own normally.
Well you could kick off another script with a run command and in that other script you could shell out (just do it all silently so that the user doesn't know that its running)
Then let the first script exit out on it own normally.
I'll give that a try, thanks. I had tried run()ing a batch file and that stops too. doing something like
Code:
run('calc.exe')
Also results in the calculator running and then exiting as soon as the logon prompt appears.
There isnt a windows security thing where it stops any processes when you press CTRL-ALT-DEL to logon is there?
