Hello @jgsims, @mickgrant, @fneidhardt and @ematos, if I missed someone else, my apologies. Just fire off an email to mconners@madisoncollege.edu if you already haven't done so. My entire goal in this documentation was to help others get into my thought processes. I am by no means an expert on all things Jamf, but what I have developed works really well for us. Sometimes, we can see the end results and revel in it, but to share with others on HOW or WHAT I was thinking can be enlightening.

As I have mentioned to others, empowering others to be empowered only strengthens our community as a whole.

I find it inspirational when my colleagues at our college in the Windows environment using SCCM are trying to figure out how I have done things so well with Jamf. Using Jamf has freed up some of my time and because of it, I have been afforded a luxury this summer to put all of this together.

If it is at all helpful, provides guidance or generally useful in any way, I am happy to share.

@mconners I sent over an email to you. Again, thank you for your help on this. I appreciate the jamf community on empowering us with the knowledge to control our whole Mac fleet with all these different types of resources!

@mconners me too please I'll send you over an email. Really appreciate it.

@mconners, I also just sent off an email. You might want to set up an auto-reply rule based on some subject line. :)

Thanks @musat I have been getting a lot of responses. Quickly frankly, I have no problem helping people out. I don't have everything documented. Things like scripts and packages haven't been touched yet. I hope to round out things this winter in these terms. When I go to JNUC this year, I am meeting up with a couple of Jamf folks to get their ideas on how to tweak things. Thanks for the interest.

@mconners I just sent you an email. I'll buy you a beer at JNUC this year!

I have build an 'all encompassing' wiki for my Jamf Pro installation. I'll attach a few screenshots here.
The wiki documents (nearly) everything in and about jamf.

From architecture, setup, configuration, management and solutions. Content is documented and cross referenced when possible.

This wiki is open, in read only, to a wide group of people. There are a few restricted pages, with sensitive info.
Although this represents a significant effort it allows documentation to be linked and cross referenced. For example, A policy may have a couple scripts and a package in it and may have been initiated by a service request from SecOps. All aspects are documented.
The Solutions section describes particular items that will be helpful when someone asks "How does that work?" "Why is that in there?", or the helpdesk techs want to know why an item doesn't show up for one user but does for another.

Here is one detail page.

@PeterG Hey I like what you've done there... but are you manually updating that beast or have you set some automation in place? To some extent as discussed in my team we feel that to some extent Jamf documents itself, however it requires too much digging in to find details and connections, there are some weird gaps. For example, why does a Policy not links to any scripts or packages used? One could use the API to extract a lot of that, and the explanation of the why, well, that's really the tough part of documentation isn't it?

@mconners .. would appreciate to also get a copy of your documentation on danko@gmx.at.

Thank you in advance..

Best,
Danko

Hello @Danko thank you for your interest. I wasn't sure if that was your full email address or not. Feel free to drop me an email at mconners@madisoncollege.edu, thanks!

I’m looking forward to seeing what everyone is talking about! Thanks for sharing your JAMF knowledge with all of us!!

@Sterritt My documentation is all done manually. Documenting is integrated into the processes as jamf 'elements' are being created. I have found that if you 'intend to go back and document' you just don't do it so we do it inline with the jamf work itself. If you consider the external benefit that the Helpdesk staff, Security Operations or even the general public get from complete documentation, it becomes worth the effort. It also allows for documenting changes over time, to a package or policy.

@mconners Thank you for the email and information!

@PeterG How can I create something similar to your monster Wiki that is amazing work man.

@mconners I emailed can you share me document. Thanks in Advance.

@mconners Im going to send you an email as well if thats ok

Hello @srini I thought I sent you an email yesterday, did it not get through? If not, send me another email, I will see if I mistyped something.

@PeterG Aah, yes, process is so important.
@JarvisUno Process is your friend!
@mconners This is so popular perhaps you could just throw up a sample page somewhere abstracting out your proprietary secrets and link it here... might be faster than replying to a bunch of emails! :-)

Hello @Sterritt the replying has been super easy for me. I don't mind the time away from work to send things out.

Like @jstillio, my team transitioned to Office 365 OneNote for almost all our team documentation. We created an Office 365 Group for the IT Team, and it automatically provisioned a OneNote group notebook. Then, every member of the team has access to this notebook from the OneNote desktop app, the web, the MS Teams collaboration app, and mobile OneNote app.

We create sections for each major topic. For example, we have sections on JamfPro, Office 365 Management, RHEL/CentOS, MacOS, VPN, etc. Under each section, we have pages that cover a specific sub-topic. Some of them are full-on step-by-step instructions, and some are just helpful commands and explanations.

OneNote has enabled us to have nicely formatted documentation with graphics, external reference URLs, and we can even drop in PDFs. It's been very handy when you're in the server room, and need to look up something quick from the smartphone.

@mconners : email sent.

@mconners I'm a little late to the game here, but this very topic just came up in a staff meeting, so I'm sending an email now.

Nice work Peter G, seems like overkill.

@mconners I'm a VERY late to the game here! Very much interested, I am sending an email, Thank you in advance!