Servers documentation template

A Dec 29, at pm. Good template to build around. Very valuable information. WhataGimik Dec 29, at pm. JCals Dec 29, at pm. Duffney Dec 29, at pm. Thai Pepper. Emerson Leal Dec 29, at pm. Radiohead Dec 29, at pm. Pure Capsaicin. Davison Jan 3, at pm. A Vigil Jan 14, at pm. Mitch Jan 16, at pm. If you are in this camp any server documentation template or checklist will do. In the other camp I see people who would use the network documentation as a tool. This could be to help them and their colleagues to better understand their network, maintain network continuity, help with project planning or a number of other reasons.

If a question was asked at least twice then the answer to it must be documented. Next you are asked about it again just refer to the documentation. Here should requirements come. Functional, technical, security, business, price. The very simple functional requirements to a document engine are:. Here are my choices:. Who are the users API description Links to users documentation if external Links to lows and regulations.

Include high level design drawing and low level design drawing. It is nice to have a table with component name, price, license key or where to find it , price, expiration date. Describe the concept. What tables are most important. How to search important data. Some useful SQL examples.

The author of this template bears following credentials:. Your Company is in Phase.. This eShop is operated by Services Concept Whitepapers. It is simple and you will achieve usable results within a few days of active asking and searching. It is indeed very important to have the list of all applications and servers, as those lists are needed for multiple purposes:.

In addition to nearly static system documentations you do need to produce "records" - evidence that required activities have been executed. Just copy the list without all attributes and fill in date, result and the link to document showing evidence and required follow-up actions for each server or application, and save it as static document.

This template was used to document a small IT department with 70 applications, 40 databases, 50 units of hardware and 35 different software licenses. This was achieved within 3 days by one consultant experienced in IT Operations. If not knowing out of mind what's running on that server, customers administrator logged in to that server and checked what's running.