Sysadmin

5612 readers

1 users here now

A community dedicated to the profession of IT Systems Administration

founded 5 years ago

MODERATORS

[email protected]

DarraignTheSane

Advice for building documentation for a small company? (self.sysadmin)

submitted 1 year ago by kurosawaa to c/[email protected]

11 comments fedilink hide all child comments

Hi guys, I recently started working at a company with about 50 people that has grown to large for their current IT setup. They have no documentation or any SOPs. Has anyone been in a similar situation and how did you go about creating documentation, especially when you are new and don't fully understand all of the services they have in place?

Thankfully it's mostly a Microsoft shop and pretty low tech but there are dozens of exchange rules in place that no one knows why they exist or what they do, dozens of SharePoint sites with critical information strewn about them and so on. It's hard to think where to even start and decide what the best way to organize this information will be, and keep in a place a system where we will update it regularly. Any advice would be greatly appreciated.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago

With things like Exchange rules, I wonder if people thought they were self-documenting? Like, our puppet manifests don't have separate documentation for them. For other things, we use a wiki for everything, and it is mixed success. People who know have to think it's something that someone else would need info about it to then write that info down. We often try and separate out "this is the high level goal" from the minutiae of doing it. And this could be a big problem if lots of people leave.