Utility command fails

Content Authoring
1

(imported topic written by SystemAdmin)

The documentation for the Utility command is vague, so I’m not positive I’m using it correctly. I made a test script which looks like this (actual names removed to protect the innocent).

prefetch file.exe sha1:123456789etcetc size:123456 http://server/folder/file.exe

continue if {exists file “__download\file.exe”}

utility “__download\file.exe”

run “__download\file.exe” -parameter

The action script fails on the utility command. I added the continue if line to prove that the file exists.

The Utilities folder has 4 files totaling 760K, file.exe is 360K

There’s a file matching file.exe’s sha1 in __download, nothing added to Utilities

BES 7.2.5.22

What did I miss?

2

(imported comment written by MattBoyd)

Have you looked in the client logs to see what error you’re getting? I know this shouldn’t matter, but what if you remove the double from around the filename on the utility command?

It looks like you’re doing everything right. Just for reference, here’s an example I have that works

prefetch KeepAwake.exe sha1:bdd0965c09afb76b8d4764400b2d1932821de2f1 size:44544 http://:52311/Uploads/bdd0965c09afb76b8d4764400b2d1932821de2f1/KeepAwake.exe
utility __Download\KeepAwake.exe

And here’s an issue I ran into (downloaded archives don’t work): http://forum.bigfix.com/viewtopic.php?id=6750 .

3

(imported comment written by SystemAdmin)

I initially did it without quotes, added them while testing.

My actions from March 11 didn’t put anything in the client log, which seems strange.

I did 2 new actions today using a different file.exe. Got these results in the log

for this command - utility “__download\file.exe”

Command failed (Unable to mark download as utility.) utility "__download\file.exe

for this command - utility __download\file.exe

Command failed (Unable to mark download as utility.) utility __download\file.exe (fixlet 123456)

Which suggests that it got just a little farther before failing when I removed the quotes.

Is there a setting somewhere that would prevent a console op from designating a utility? If so, how would I find out whether I’m prevented? (Other than asking the master op, which would be a waste of time.)

4

(imported comment written by BenKus)

For strange reasons, I think you might need a capital “D”.

Try:

utility __Download\file.exe

Ben

5

(imported comment written by SystemAdmin)

Thanks, that worked.

“Strange” sounds appropriate.

6

(imported comment written by BenKus)

The strange reasons are related to case sensitivity on unix/linux for folders, but not for Windows… Or it would be fair also to say that it is just a bug we haven’t gotten around to fixing yet…

Ben