internal documentation

[tlarkin]

Hi everyone:

This has come up in discussion lately and well I have had this conversation before. How do you all document what you do with Casper and your OS X Servers, images, client configurations etc?

I have a lot of bad habits when it comes to being a Sys Admin. I openly admit that. For example if permissions are botched on a package, instead of me recreating the package (which is the proper way) I will just write a one or two line script that fixes the problem and then attach it to a Casper policy. Thanks to the divine wisdoms of the Jamf software crew at the CCA training last summer I no longer do that. Mainly it is so the next guy/gal who comes in to work at my current place of work isn't lost with tons of different things I do. I am the type of person that will script out everything in a shell script if I can.

So, when you all build packages a certain way do you document it for your co-workers? Do you have a wiki? Do you take screen shots?

I know this isn't really about Casper, but more of a question do you document your work with Casper.

If you want to take this conversation off list feel free and you can email me directly.

I would like to sometime implement a wiki for internal use where I can document how I do stuff so if I ever go on vacation, leave, or whatever the people I work with aren't left in the dark. Plus it gives me something to do, and I do kind of enjoy writing.

Thanks

Tom

---

Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
blackberry: 913-449-7589
office: 913-627-0351

[Jeff-JAMF]

Setting up a wiki for doing this is a great idea...now if I can only find
time to do that! ;-)

Jeff Johnson
Technology Coordinator
Glendale-River Hills School District
Glendale, WI 53209
jeff.johnson at glendale.k12.wi.us

[jarednichols]

Apple's Leopard Server wiki is really really nice.

[jarednichols]

We have a standard SOP that we fill out for all IT operations. Each OU has their own format, tuned to the types of operations they do, but with in that OU, all of the SOPs follow a standard form.

We tend to break down what is in each SOP by a single function or task, referencing SOPs that are prior to, or follow on the one you're looking at, as well as in the process flowchart that is in each SOP.

J