6 steps to IT documentation

The Video-Guide for your successful project start

How do I start with my IT documentation project?
Our six videos answer this question – packed with knowledge and numerous tips.

What are these videos about?

The six videos in the series are webinar videos designed to help newcomers to start with their IT documentation. Using a live system, our experts build a complete IT documentation step by step – from the first locations to the documentation of business services and licenses.

Are there any other videos?

In addition to our series “6 steps to IT documentation” we have published numerous other videos, webinars and tutorials for you, which you can find on our YouTube channel. If you are missing a topic or have questions, we are looking forward to your message. Please also subscribe to our YouTube channel and stay up to date.

The video series “6 steps to IT documentation”

In 6 Schritten zur IT-Dokumentation - Teil 6: Business-Services und Applikationen

Part 1

In 6 Schritten zur IT-Dokumentation - Teil 2: Netzwerke

Part 2

In 6 Schritten zur IT-Dokumentation - Teil 3: Server

Part 3

In 6 Schritten zur IT-Dokumentation - Teil 4: Clients

Part 4

In 6 Schritten zur IT-Dokumentation - Teil 5: Software und Lizenzen

Part 5
Software & Licenses

In 6 Schritten zur IT-Dokumentation - Teil 6: Business-Services und Applikationen

Part 6
Applications & Services

Information about the videos

Part 1: Documentation of the IT infrastructure with i-doit

You are probably at the beginning of your project to create an IT documentation. You may be wondering how to document IT in the right way. This project will be your main occupation during the next months.

With i-doit you can even go a little further. Because you are developing a central IT documentation. This small difference has a significant impact. It opens up many interesting possibilities, but also many necessities.

The biggest advantage of central IT documentation: several users can work on and with it. However, this invaluable advantage also leads to important requirements. Every employee must practice a certain discipline. An approximately equal level of knowledge is also required for all those involved in such a project.

In this first step on your way to IT documentation, you record the infrastructure of your IT landscape with i-doit. You will learn how to create locations and what best practices exist for IT documentation.

Part 2: Network documentation with i-doit

In this second part of our series, you will expand the IT documentation to include networks. In addition to recording Layer-2 and Layer-3 networks, our experts will use the i-doit live system to show you how to implement IP address management. Especially in larger networks this topic is of essential importance.

In the course of the video you will learn how to create routers and switches. And the topic of cabling will also be introduced to you.

The cabling of IT assets using copper cables or fiber optics is part of the IT documentation. Even though the topic is addressed in this video, it should be pointed out again here that this part of the IT documentation should ideally not be implemented at such an early stage. The documentation of the cabling is a complex process that should be done at a later point in time.

Wireless networks (WLAN) can also be documented with i-doit. Our experts will show you how to use the floorplan add-on to display heat maps that can be used to visualize the illumination of rooms.

A particular strength of i-doit are the reporting options. We will show you how you can generate comprehensive and meaningful reports with the help of i-doit.

Translated with www.DeepL.com/Translator (free version)

Part 3: IT documentation of physical and virtual servers with i-doit

Which servers do you operate in your company?
What services do these servers provide?

Without a comprehensive IT documentation, you can only answer these questions inaccurately in most cases. Of course, as an administrator you will always have basic information such as server names and IP addresses in your mind.

But what happens if you are unavailable or leave the company? The third part of our series shows you how to put your knowledge into your IT documentation.

But IT documentation goes even further. With the information available, you can plan for changes in advance. You can ensure the availability of resources and react quickly in the event of server failures.

In this third part of our series, we look at the documentation of physical and virtual servers and record hardware and hosts for virtual environments. Our experts will show you how to allocate resources for virtual systems and document the network connection of your servers.

An IT documentation also contains organizational information. You should always include important operational data such as contact persons, supervisors and responsibilities. This video shows you how to implement this in i-doit.

Part 4: Documenting client systems and lifecycle of IT assets in i-doit

What equipment does an employee have in use? What work equipment do we have to provide a new colleague with?

These are questions that you, as the person responsible for IT in a company, always ask yourself. An IT documentation can answer these questions. Assign devices to new employees quickly and generate the required documents such as handover protocols directly from the IT documentation. In the fourth part of our series we will deal with the IT documentation of client systems and workstations.

Another topic in this fourth part of the series is the documentation of the entire life cycle of IT assets. Our experts will demonstrate how you can use your i-doit IT documentation to map responsibilities and generate important documents directly from the documentation. On- and offboarding of employees is also addressed in this video. 

Mice, keyboards and memory components are often neglected as “low-value”. In fact, depending on the size of the company, these assets can quickly make up a larger part of IT assets. However, no IT administrator wants to see these “mass assets” listed individually in their CMDB, but these devices should also be part of the IT documentation. We’ll show you how to handle these assets from a documentation perspective.

In the third part of the series – “Documenting Servers” – we showed you how to document the software installed on servers and the corresponding licenses. Of course, this also applies to client systems: the installed and licensed software must be recorded in IT documentation. Here we are already anticipating the next part of our series, which will deal specifically with license management.

Part 5: License management and documentation of software

Which licenses are used in my company? On which devices is which software run? Which operating systems run on my servers?

Recording the software used in a company is a rather time-consuming task. In such a case, central IT documentation such as i-doit is worth its weight in gold. In this fifth part of our series we will show you how to record the software used in your company in your IT documentation and document the associated licenses.

In the fourth part of our series (“Documentation of Clients”), our experts have created a target configuration for a client system. In this fifth part we show you how to install this system. The finished configuration is then transferred to your i-doit IT documentation using a discovery solution.

Another topic is the different software variants, how they are installed on server and client systems. In the server area we will show you how to manage operating systems and the corresponding patch levels in i-doit.

The documentation of server services and daemons or cluster services is also important. When does it make sense to transfer these into the CMDB and when not? This question is answered in the video.

At the end of this video you will see how to store your “Definitive Software Library” in i-doit. This repository, defined in ITIL4, contains not only the authorized versions of all software configuration elements and master copies of the respective software products, but also the associated documentation and license information.

Part 6: Documentation of applications and IT services with i-doit

“I can’t send e-mail!”
“I can’t access the network drives!”

As an IT administrator, you are familiar with these statements. You will hear them almost every day in your organization. But do you know off the top of your head which devices, people and software are connected to the failed service?

You can find out how to map these services in your IT documentation in the sixth and final part of our series “6 steps to IT documentation”. The documentation of services is not only helpful when one of the services fails. It is also essential for precise planning. In case of maintenance, a device must be switched off. With the information from the IT documentation, you can plan which replacement systems will take over for the time of the outage in order to provide all users with the required services.

But service is not just service. While a user understands an IT service to be everything he needs to work, the service provider (including you as the IT administrator of your company) sees the technical part of what is available to the user.

This sixth and final part of the series deals with these IT services. Our experts show you how to document services in i-doit. We will show you how to distinguish between business IT services, application services and infrastructure services, how they are connected and how they can ultimately be assigned to specific assets.

Get even more knowledge

6 steps to IT documentation

Cover 6 steps to IT documentation

Your compact start into the
world of IT documentation

How to build a working CMDB

Cover CMDB E-Book english - How to build a really working CMDB

How to implement your CMDB project

8 pitfalls
of discovery

How you start with IT documentation

All questions about Discovery answered in a hands-on way!

solutions with i-doit

How you start with IT documentation

How to find the right solution for network monitoring.

Service Desk
solutions with i-doit

Whitepaper Cover Service Desk

How to effectively run a service desk