How to Get Started with a System Having No Documentation?

You know, a lot of sysadmins fall into the trap of not documenting anything. They set things up, and when issues crop up, they realize how badly it's needed. On the plus side, you’ll learn a ton about the systems in the process! Just take it step by step. It's challenging, but you’ll also have the chance to create documentation yourself once you get everything figured out. Good luck!

If you have full access and the necessary passwords, you should be in a good position to reverse engineer the systems. It might be a slow process, especially if they're production systems, but go methodically. Take your time to figure out how everything is set up and talk to users about how they use the systems. It took me about six months to fully understand a similar situation when I started, so be patient. Also, prioritize learning how to back up and restore the systems as that’s critical.

First things first, take the time to analyze the systems. Look at what each one does and how they interact. Don't hesitate to ask questions if you're unsure about something. Once you've got a grasp on it, start documenting as you go. Welcome to the IT world where documentation is often an afterthought!