/build/static/layout/Breadcrumb_cap_w.png

Agent can't run programs

I'm running kbox agent on windows 7 64 bits and UAC disable but if I try something like this:
VerifyLaunch “SYS\xcopy.exe” with params “$(KACE_DEPENDENCY_DIR)\backgroundDefault.jpg $(KACE_DEPENDENCY_DIR)\two.jpg”.

nothing happend...No copy.. no error screen.... also bat files don't work.. on my client I can see a fast d.o.s screen and on information.
any idea for me???
Best regards,
Rildo
Edit[/align]

0 Comments   [ + ] Show comments

Answers (12)

Posted by: airwolf 14 years ago
Red Belt
0
That script will copy backgroundDefault.jpg to two.jpg in the script download directory (i.e. C:\Program Files\KACE\KBOX\Downloads\1234). Is this what you are trying to do? No batch file will run, because it doesn't look like you've set one up.

Also, I can't see the images you tried to embed for your verify statement.
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
I like to copy a file for c:\temp with this command:
VerifyLaunch “$(KACE_DEPENDENCY_DIR)\xcopy.exe” with params “$(KACE_DEPENDENCY_DIR)\backgroundDefault.jpg c:\temp”.

and it is not working... the folder c:\temp is there everyone have full permission there and still don't work.
I can see the jpg file is there on the kbox folder on the client and if I go there and open a cmd and make the same xcopy command I can copy the file, just the kbox agent can't do a xcopy.
I'm a new user of kbox and I don't think it is normal not to be able to copy a file to a folder on the client.
Posted by: airwolf 14 years ago
Red Belt
0
The images you are attaching to your posts are linked directly to the admin console in your KBOX - which nobody else can see, because we cannot authenticate to your KBOX.

According to your latest post, you're trying to access xcopy.exe from the dependency directory, and this won't work unless you are actually adding it as a dependency to your script. For the "Launch" command, try just using "xcopy.exe" with no preceding directory. The OS will automatically look in the system folders to find it.
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
Hi Andy,
Thanks for try help me...
I made the changes and now I have this error:
Unable to launch program (because file does not exist): \xcopy.exe C:\Program Files (x86)\KACE\KBOX\\packages\kbots\53\backgroundDefault.jpg c:\temp\two.jpg True?
Error creating process: \xcopy.exe C:\Program Files (x86)\KACE\KBOX\\packages\kbots\53\backgroundDefault.jpg c:\temp\two.jpg, System Error Code: 123 The filename, directory name, or volume label syntax is incorrectI also made a other test with the command dir:
On SuccessLaunch “SYS\dir” with params “c: > dir.txt”.

Launch “\dir” with params “c: > dir.txt”.
and now I have this error:
Unable to launch program (because file does not exist): SYS\dir c: > dir.txt True?
and
Unable to launch program (because file does not exist): \dir c: > dir.txt True?
Error creating process: C:\Windows\system32\dir c: > dir.txt, System Error Code: 2 The system cannot find the file specified
Error creating process: C:\Windows\system32\dir c: > dir.txt, System Error Code: 2 The system cannot find the file specified

Is like agent is not able to run any dos command.


Edit
and

[/align]
Posted by: airwolf 14 years ago
Red Belt
0
For your dir dumps, you should use this instead "$(KBOX_SYS_DIR)\cmd.exe" with params " /c dir > C:\dir.txt".

For the xcopy, try changing the directory to $(KBOX_SYS_DIR) and the file to xcopy.exe, so it runs "$(KBOX_SYS_DIR)\xcopy.exe".
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
Still not work..
now he find xcopy and run, but nothing happend... i just tested in a win7 32 and 64 and I have the same issue... it is impossible to copy any file.
I can see a xcopy windows on my screen for 1 second and it is closed without and information... just a black d.o.s screen on me monitor for 1 second.
Now I'm using this command:
VerifyLaunch “$(KBOX_SYS_DIR)\xcopy.exe” with params “$(KACE_DEPENDENCY_DIR)\backgroundDefault.jpg test.jpg /y”.
and I have this log:
Status Log START
FINISH (in state 'verification_success') Activity Log Launching program: C:\Windows\system32\xcopy.exe C:\Program Files\KACE\KBOX\\packages\kbots\53\backgroundDefault.jpg test.jpg /y
but still nothing happend.... it is normal for kbox or I need to open a case?
Posted by: airwolf 14 years ago
Red Belt
0
It sounds like a scripting configuration issue. Can you take a screenshot of your script task and post it?
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
Take a look, any ideas are very wellcome...

Posted by: airwolf 14 years ago
Red Belt
0
Since your parameters are being sent to xcopy, you may need to wrap $(KACE_DEPENDENCY_DIR)\backgroundDefault.jpg in quotes, so the run command would look like:

$(KBOX_SYS_DIR)\xcopy.exe "$(KACE_DEPENDENCY_DIR)\backgroundDefault.jpg" C:\TEMP\test.jpg /y

EDIT: To further explain, $(KACE_DEPENDENCY_DIR) contains a space in the "Program Files" part of it.
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
I made a test with your command's and it still don't work.
In a computer with windows xp I used only for test it is working fine.
I will open a case on kbox.
Thanks for try help me.
Posted by: rgiroux 14 years ago
Senior Yellow Belt
0
Hi Andy,
Do you know if kbox have any problem with win7?
Best regards,
Rildo
Posted by: KevinG 14 years ago
Red Belt
0
Create a batch file and add it as a dependency.

The contents of the batch file: (mybatch.bat)

C:\WINDOWS\system32\xcopy backgroundDefault.jpg c:\two.jpg

Launch a program...
Directory: $(KACE_DEPENDENCY_DIR)
File: mybatch.bat

Check : Wait for startup

Parameters: *** Leave this blank
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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