Avatar of jmoody
 asked on

Server Documentation

I am new to being a server admin and work for a fairly large organization. I was assigned a bunch of Windows servers that have absolutely no documentation on them. I used SYDI to get some useful info but I’m looking for more info that an automatic tool probably can’t give me. I am looking for support info such as what the server does, it’s role in the organization, critical services and any info that can help during the troubleshooting process. I would like to draft a document that I can send out to other teams that have databases or applications on these servers to help fill out. Maybe someone already has one that I can use or ideas of what other questions I can ask to get as much info as I need to support the server and applications on the server.
Microsoft Server OS

Avatar of undefined
Last Comment

8/22/2022 - Mon

This is a good idea, you already know that you're going to have to get this information from other people, rather than trying to extract it from the machines. But I'm not a fan of the "fill out and return questionnaire" approach.

Take your list of servers, and throw out the wide net on the question of "Who's responsible for what this server does, and what are the key functions it serves?" That's as long as you want your wide net questions to be.

Then set up meetings with those people, preferably in a room with a whiteboard, so that you can ask them questions directly, and have a conversation. Take notes, obviously.

This accomplishes a number of things. Technically speaking, each of these servers is likely to be different enough that the full set of answers on them wouldn't properly fit into a single detailed questionnaire. While you're talking about a particular server, you can ask questions for clarity, and follow down the paths that open up about it.

Moreover, as a new admin, this is an opportunity for you to get to personally know the people you'll be working with, and providing services to. You'll learn about the servers, sure, but you'll also get a better picture of who these people are, and what skills and resources they bring to the table - things you might need to call on in the future. And they'll get to know something about you, too, which will hopefully evolve into, "Hey, I bet jmoody could help with this" when they need something down the road.

I know that probably doesn't answer your question the way you expected, but it's something to consider, at least.

I didn't think about that approach but that's a great idea and I think I'll try it. I still would like to get a check list of things that I need documented so that I don't forget anything.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Thanks for the tips.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy