[Casper] Advice on package naming conventions?

[Criss Myers]

Hi Ric, 

As i like to have all macs with roughly the same configuration and
software and as my macs are used by all the University I probaly set
mine up differently 

I have Configurations based on different usages, 

Development (for my use) 
Digital Dark Room 
Laptops 
Open Access / Teaching 
Project Studios 
Staff 
Lab 
OS Only 
Testing 

I then set my categories based on application types etc 

Adobe 
Apple Updates 
Audio 
Core OS 
Core Software 
Drivers 
Login / Logout Hooks 
Printers 
Scanners 
Scripts 
Staff 
Testing 
Utilities 
Video 
OutDated / Removed 

I then have categories for my polices : 

Monthly 
After Imaging 
Startup Items 
Temporary 

Criss


Criss Myers
Senior Customer Support Analyst (Mac Services)
Apple Certified Technical Coordinator v10.5
LIS Business Support Team
Library 301
University of Central Lancashire
Preston PR1 2HE
Ex 5054
01772 895054

>>> On Tue, Nov 4, 2008 at  9:24 PM, in message
<C53619C8.10B36%ernstcs at uwec.edu>, "Ernst, Craig S." <ERNSTCS at uwec.edu>
wrote:

Hi Ric,

The format we’ve used here is basically how we would organize things in
a “start menu” type scenario, but basically making logical categories.
You’ll find that everyone does it differently.

We have the following categories and description of what they contain in
our system, and most of these pre-date my managing this system:

Adobe * It became so many packages it had to become it’s own, was in
suites, but could even break this down to AdobeCS3, AdobeCS4, if you
like
Classic * OS9 Apps
Common Applications * Applications that get deployed everywhere by
default that don’t fit into any other category (Examples: Google Earth,
SPSS)
Departmental * If specific department requests/purchases software for a
limited set of locations it goes here, it’s like Common Applications
Graphics & Web Design * Graphical applictions and web editors (Example:
Poser)
Hardware * Scanners, Printers, etc.
Internet * Browsers, IM Clients, Telnet, FTP
Languages * Basically the language packs for the OS if it needs to be
delpoyed after the fact
Multimedia * Audio (Audacity), Video (iMovie), Disc Authoring (iDVD),
Media Players (Real, QuickTime, Flip4Mac)
Office * Office suites (Office 2008, Office 2004, NeoOffice, etc.)
OS * Base OS Images
Printers - DUH
Scripts * All our scripts are just in one category, but we never had a
lot of them to deal with to sort them out
Suites * This group was an afterthought, but iLife is the only thing in
here, and could go back under Common Apps
System Configuration * Any packages that modify the operating system and
its settings
User Environment * Any packages that modify a user’s experience and
settings
Utilities * Utility applications like Adobe Reader, KeyServer Client,
Self Service, Recon, Refit, Stuffit, etc.

When we create a package we then (almost always) put the prefix of the
category on the package, or at least an abbreviation of it. Some
examples:

internet-Firefox_3.0.3
office-2008_12.1.4
os-X.5.4
ue-X5_Universal_Dock (Short for user environment, and X5 meaning for
Leopard)
sys-res-1024x768x32x75 (Short for system configuration)

You get the jist of it. The other thing we do with each package is have
a folder at the root of the drive called ‘Shortcuts’, and then we build
a folder structure for these categories and in some instances
sub-categories, and place an alias to the application in the appropriate
folder. We then place the shortcuts folder as part of the dock as a list
so it expands out and does act as a menu for users to access
applications if they aren’t accustomed to browsing the hard drive, using
Spotlight, or whatever people prefer to use. I attached some screens,
but they may not go through so if you’re interested just email me. With
the Shortcuts keep in mind that some categories like Adobe apps and
iLife Suite apps have aliases in different places within the Shortcuts
folder. Is some of it right or wrong sure...again that’s up to you to 
do
what you want. I’m sure we could spend a good day or two here arguing
about it.

Craig E

On 11/4/08 2:47 PM, "Ric Getter" <ric.getter at pcc.edu> wrote:


We're a large, multi-campus community college getting ready to deploy
the
Casper Suite. We've just gone through the Jump Start and are getting
ready
to build our base images, packages and configurations. As JAMF
recommended,
we're planning on having a single "librarian" manage the entries on the
Casper server.

Having been involved in similar ventures, I understand the value of
setting
up a good naming convention system early in the game. We have a good
system
for naming computers already in place, but it appears that we're going
to
have a fair number of packages and a potentially huge number of
configurations on file.

I would greatly appreciate any suggestions or samples you can offer.
Feel
free to forward any files or attachments directly to my e-mail address,
ric.getter at pcc.edu.

Thanks,
Ric

 --
Ric Getter
Portland Community College/Sylvania
Coordinator, Computer Resource Center
(503)977-8036


_______________________________________________
Casper mailing list
Casper at list.jamfsoftware.com
http://list.jamfsoftware.com/mailman/listinfo/casper


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20081105/8d8fddc1/attachment.html