<br><font size=2 face="sans-serif">Ric,</font>
<br>
<br><font size=2 face="sans-serif">Here in K-12 land we may do things differently
and I've changed naming conventions only once since starting. I would
be too hard to start over. I set a couple Groups in Casper
Admin for packages and scripts and name them with abbreviations from the
groups. Example, Curriculum is the group and "CUR-" is
the prefix of the package name. We also avoid using spaces in the
package name. I think that Craig might have showed me this process
at our CCA class. Now with Self-Serivce, I might be adding a group
in there that is independednt of the type of package. </font>
<br><font size=2 face="sans-serif">I have these package and script Groups.</font>
<br><font size=2 face="sans-serif">CUR - Curriculm (content
related apps, Comic life, Google Earth, Everyday Math, SmartBoard, etc.)</font>
<br><font size=2 face="sans-serif">ENT -Enterprise Apps (Read180,
FasttMath)</font>
<br><font size=2 face="sans-serif">MM - Multimedia (iLife, Audacity, Adobe)</font>
<br><font size=2 face="sans-serif">OS - OS packages (OS builds, Parallels,
OS updaters )</font>
<br><font size=2 face="sans-serif">PRO - Productivity (MS OFfice, Firefox,
FileMaker Pro)</font>
<br><font size=2 face="sans-serif">UEV - User Environment (dock settings,
etc. )</font>
<br><font size=2 face="sans-serif">UTL - Utilities (Recon, Text Wrangler,
AV, etc.)</font>
<br>
<br><font size=2 face="sans-serif">The ones I've added for Self -Service
Printers, Primary and Secondary (grades) </font>
<br>
<br><font size=2 face="sans-serif">So far this is working, but I'm not
sure it is the best way for everyone.</font>
<br><font size=2 face="sans-serif">-Nathaniel</font>
<br>
<br><font size=2 face="sans-serif">Saint Paul Public Schools, </font>
<br><font size=2 face="sans-serif">MN</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Ric Getter"
<ric.getter@pcc.edu></b> </font>
<br><font size=1 face="sans-serif">Sent by: casper-bounces@list.jamfsoftware.com</font>
<p><font size=1 face="sans-serif">11/04/08 02:41 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
ric.getter@pcc.edu</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><casper@list.jamfsoftware.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[Casper] Advice on package naming conventions?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>We're a large, multi-campus community college getting
ready to deploy the<br>
Casper Suite. We've just gone through the Jump Start and are getting ready<br>
to build our base images, packages and configurations. As JAMF recommended,<br>
we're planning on having a single "librarian" manage the entries
on the<br>
Casper server. <br>
<br>
Having been involved in similar ventures, I understand the value of setting<br>
up a good naming convention system early in the game. We have a good system<br>
for naming computers already in place, but it appears that we're going
to<br>
have a fair number of packages and a potentially huge number of<br>
configurations on file.<br>
<br>
I would greatly appreciate any suggestions or samples you can offer. Feel<br>
free to forward any files or attachments directly to my e-mail address,<br>
ric.getter@pcc.edu.<br>
<br>
Thanks,<br>
Ric<br>
<br>
--<br>
Ric Getter<br>
Portland Community College/Sylvania<br>
Coordinator, Computer Resource Center<br>
(503)977-8036<br>
<br>
<br>
_______________________________________________<br>
Casper mailing list<br>
Casper@list.jamfsoftware.com<br>
</font></tt><a href=http://list.jamfsoftware.com/mailman/listinfo/casper><tt><font size=2>http://list.jamfsoftware.com/mailman/listinfo/casper<br>
</font></tt></a>
<br>