IT Documentation Helpers
-
75 pages per host?
-
Here is the Word document Navigation view of what the software generates.
Assuming this system nothing was excluded it seems pretty inclusive.
-
That's quite exhaustive, will take a look
-
@scottalanmiller said in IT Documentation Helpers:
75 pages per host?
In that range, another system I just ran again was 68 pages.
-
Here is some documentation from the SYDI developer.
-
It doesn't have to be that many pages, you can filter out what you want, don't want.
-
-
@Jstear said in IT Documentation Helpers:
Thanks for that, I know it can be shortened.
(not trying to say it couldn't be etc)
-
@DustinB3403 I meant to reply to SAM, as I don't think he liked the fact it was 75 pages.
-
-
@travisdh1 said in IT Documentation Helpers:
@DustinB3403 I use a Drupal blog. Simple and easy to manage.
I've used Drupal for this, production sites, and a ton of other stuff. It's an awesome framework.
I've also used LaTeX for documentation. Formatting is really easy with it.
-
@stacksofplates said in IT Documentation Helpers:
@travisdh1 said in IT Documentation Helpers:
@DustinB3403 I use a Drupal blog. Simple and easy to manage.
I've used Drupal for this, production sites, and a ton of other stuff. It's an awesome framework.
I've also used LaTeX for documentation. Formatting is really easy with it.
I'm actually kinda sad I never learned TeX/LaTeX properly, and haven't seen anything that would drive me to learning it today.
-
@DustinB3403 said in IT Documentation Helpers:
@Jstear said in IT Documentation Helpers:
For existing systems, check out SYDI
I think I've used SYDI before, sounds very familiar....
SYDI is fantastic. We run and store a SYDI report every time we make a server change.
-
You can tailor the application to grab what you want, if all settings is too verbose. Here's one we use for basic app servers with only 10 sections.
-
@travisdh1 said in IT Documentation Helpers:
@stacksofplates said in IT Documentation Helpers:
@travisdh1 said in IT Documentation Helpers:
@DustinB3403 I use a Drupal blog. Simple and easy to manage.
I've used Drupal for this, production sites, and a ton of other stuff. It's an awesome framework.
I've also used LaTeX for documentation. Formatting is really easy with it.
I'm actually kinda sad I never learned TeX/LaTeX properly, and haven't seen anything that would drive me to learning it today.
Ha I didn't either. I just fumbled around until I got it looking the way I wanted lol.
-
SYDI looks really interesting. Going to try to make time to make a look at it.
-
Problem with SYDI is that it is limited to Windows servers, no Linux or other support. Not bad, but an important limitation. Mostly it is Windows that is needing to be documented so it covers a lot of ground, though.
-
@scottalanmiller said in IT Documentation Helpers:
MediaWiki, Sharepoint's Wiki, OneNote are all decent tools for this.
OneNote on Office365 was what we used at NTG and it was great. Different folders for different clients, with credentials for the systems, network info, IP addresses, etc. Until I worked there, I thought OneNote was stupid. Overall, I still do, but I also have seen that it can be extremely useful in many ways.
-
OneNote definitely does some cool stuff, it's great for media heavy, very ad hoc documentation.
-
@scottalanmiller said in IT Documentation Helpers:
Problem with SYDI is that it is limited to Windows servers, no Linux or other support. Not bad, but an important limitation. Mostly it is Windows that is needing to be documented so it covers a lot of ground, though.
SYDI has a Linux tool. I haven't used it, so I don't know it's limitations though.
