Überblick Deutschland in i-doit

IT administrators who are responsible for the cross-location administration of IT infrastructures often face special challenges. They are often unable to access devices and systems directly, but must be able to track all changes in order to identify the causes of malfunctions.

With i-doit you not only get a visual overview of your global, international and regional locations, but you can also track all changes to devices and systems. We will show you a concrete example of how i-doit makes it very easy for you to carry out your cross-location IT administration.

In our application case, the company has several locations in Europe and South America. The decisive question for the responsible IT administration and the IT helpdesk is: From which location do the reported malfunctions originate and which IT infrastructure is available there?

 

Global overview

 

First, we have added the individual locations of the company to the map. So we can quickly switch between different locations to get all the information we need. 

 

Location Europa in i-doit

 

We visualized our company locations on a map of Europe. This allows us to switch between locations quickly and easily.

 

 

International Overview

 

Überblick Deutschland in i-doit

 

National Overview

 

Überblick Deutschland in i-doit

 

Regional Overview

 

Overview Düsseldorf in i-doit

 

When rapid crisis management is required

 

Location management is efficient for all system failures – but especially in worst-case scenarios like this: An external site reports the failure of a business-critical system. In our application case, one of the employees at our Düsseldorf location informed us that the POS system no longer functions and that no goods can therefore be sold at present. No sales mean no sales either, so we have to find the cause quickly and rectify the problem as quickly as possible.

 

 

Tracking changes with the i-doit logbook

 

When a system malfunction is detected, it is useful to be able to trace when and by whom changes were made to the affected system. i-doit offers a logbook that documents all changes to an object or system. This enables us to make qualified enquiries to the respective employee if required. This saves us valuable time.

 

Logbook Register in i-doit
Logbook Entry in i-doit
Logbook Details in i-doit

In order to determine the cause of the malfunction, we navigate to the POS system and open the logbook. There we check the last changes made. 

When looking through the logbook, we notice that the IP address was changed the day before. In addition, we can see who made this change and when. We can see from the logbook that “Max Admin” changed the IP address on 21.08.2019 at 17:53 hrs.

The logbook lists all changes made by all users. With a click on the corresponding logbook entry (marked red) we receive further information.

The detailed view shows us that “Max Admin” has changed the IP address from 172.0.1.3 to 172.0.1.11. The IP address has been changed from 172.0.1.3 to 172.0.1.11. Since the infrastructure in our example works with static IP addresses, it is likely that the POS system is no longer accessible due to the change of address and is therefore limited in its function.

 

Cross-site administration

 

Locations can be optimally managed with i-doit, as you have a variety of visualization options in addition to the classic tree structure.

This supports you in your daily work as well as when training new employees or taking over new fields of activity. Every change to systems and devices is thus completely traceable. In this way you can quickly identify the causes of malfunctions and remedy them quickly.

 

Logbook in i-doit

War diese Seite hilfreich für Sie?