Casper Feature Requests

I’ve gotta say that these two below would be on my wish list.

It drives me to no end that I have to put TEXT into a file for it to be read and run by the binary. I realize that there are some really complicated scripts, but for many of them all I need is a simple text window in the JSS to write it up and save it.

Right now you gotta:

Open text editor of choice Type up your script Save the file Launch Casper Admin Upload file Configure the options * And save

I’m sure it has something to do with the command line pointing at the actual script file to run, but I think that could be generated on the fly.

A lot of my needs for scripts are to run some simple one-liner commands at the beginning of a policy, so I have to put them into a script to do that. I know that I already asked to have two sections on the advanced tab for: Run Command(s) Before, Run Command(s) After. If I had that I could probably cope not having to write scripts through the software.

The other one that came to mind that I’ll revive is after a FirstRun install of an Adobe install completes to also run a patch process since the screen is already locked out and a user logged in. I think I had asked that another tab be added to an Adobe Install that listed all available Adobe Updaters that you checked a box to have them run after the install.

Should be interesting to see how CS5 goes...

Keep the ideas coming folks!

Craig E

I agree on that two

Hi William,
"Smith, William" <William.Smith at merrillcorp.com> wrote:

I'd like to say "me too" but only if the feature can have a way to validate/confirm script syntax and changes.

BBEdit has syntax coloring...a great visual indicator when writing/troubleshooting.

Combining both would be great.

Don

I would disagree with doing that. I don't feel it's Casper's place to
On 3/29/10 2:33 PM, "Don Montalvo" <donmontalvo at gmail.com> wrote:
validate the syntax. While it would be nice, it's not meant to be a script
editor. Better tools exist for doing that and Casper would never come close.

I'd just like to see scripts stored in the JSS for the sake of easier
management, not easier development.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

I would most likely write in BBEdit and then copy and paste into JSS/Admin,
I'm just looking for a functionality like we have with the Extension
Attributes, being able to paste a script right into the window and have it
work.

--
Alan Benedict
?
Macintosh Technician
The Integer Group
O: 515-247-2738
C: 515-770-8234
http://www.integer.com

I would love to be able to edit my scripts on the fly as well. Many
times I will need to update a script to reflect an OS change, account
change, or even say the difference between 10.5 and 10.6. Being able to
modify scripts on the fly, and have Casper Admin automatically remove
the old version and update it with the new one (since scripts are tiny
file size wise) to all distribution points would be awesome.

Now if you could only get Casper to brew me a pot of tea or coffee in
the morning.

-Tom

I have a feeling that JAMF didn't mean for scripts to be so utilized in the
product so they haven't really expanded upon the use/implementation of these
features. Myself, I'm an under-the-hood kind of guy and if it can be done
with a script, I'll do it. I'd love to see these changes too.

j

I mentioned to Zach or someone at JAMF a couple of years ago that I'd like
On 3/27/10 8:51 PM, "Alan Benedict" <abenedict at integer.com> wrote:
to see scripts stored in the JSS rather than in files. This would be
possible to do with shell scripts but I doubt possible for AppleScript
scripts.

Adding a "me too" to this thread for more advanced script support.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

I mentioned to Zach or someone at JAMF a couple of years ago that I'd like to see scripts stored in the JSS rather than in files. This would be possible to do with shell scripts but I doubt possible for AppleScript scripts.
"Smith, William" <William.Smith at merrillcorp.com> wrote:

Adding a "me too" to this thread for more advanced script support.

Hi William,

I'd like to say "me too" but only if the feature can have a way to validate/confirm script syntax and changes.

BBEdit has syntax coloring...a great visual indicator when writing/troubleshooting.

I would disagree with doing that. I don't feel it's Casper's place to validate the syntax. While it would be nice, it's not meant to be a script editor. Better tools exist for doing that and Casper would never come close.

I'd just like to see scripts stored in the JSS for the sake of easier management, not easier development.

--

William Smith

Good points. I guess a compromise, if possible, would be to integrate BBEdit with JSS? Interoperability, so maybe buttons "New Script" which sends you to your choice of text editors...as well as a "Edit Script" which also takes you to your choice of editors? This way we can continue using BBEdit (or whatever you choose to use) directly through JSS? :D

Don

While we are doing feature requests, and I love the script Idea. In fact, if I could just copy/pasta a working and tested script in say a dialog box in the JSS and say, this is a script in X (perl, apple script, shell, php, etc) format and then the JSS would write it to a file with in the Casper share. I could also say, open that file and modify something. One pain I have is when I have my post and pre imaging scripts that contain passwords in them, that if the passwords change I gotta change the script. So, I would love to edit it on-the-fly so to speak and be able to hit an update button and have every copy of the script update across the board.

Also, on a side note in case anyone is wondering, those passwords get destroyed at the end of each script when i clear the logs, flush caches and clear out any evidence of said account being used.

I would also LOVE a manual page for the jssutil command.

Thanks

Tom