Since the whole database grew from a very simple approach to something bigger, Servers migrated to Servers and Equipment. The idea and thought behind it is rather simple – you can make a huge database application that divides everything in specific tables and input forms, likely resulting in multiple search forms or at least complicated data searches or you keep it simple.

What do most businesses have – a IT helpdesk, Sys-Admin level and Management level. While the helpdesk will deal with workstations, the sys-admins deal with all the server and network equipment while the management oversees those tasks. This might be simplified but is true for the most part.

So Sys-Admins would work in the Servers and Equipment module for the most part. This made it just logical to abuse this module for more then just servers.

Enough about on how this emerged, lets dive in.

You can chose a Type like virtual server, physical server from one of the many pre-configured entries, give the entry a hostname and define information like deployment status, department, location, etc.. basic information about software and hardware.

Further is there a relation to VMware vCenter servers, datacenters and clusters.

Information on if the system is backed up – what will expect a weekly review entry in the backup-module and information about the warranty that might cause it to show up in the main menu when the warranty is due soon.

You can add MAC addresses and see assigned IP addresses.

Any local harddrive / SSD / RAID / partition and volume information can be added in a simple flat table.

The system will show you related databases and what it might know about backup reviews – if you use those.

Software can be related to server and incidents be reviewed.

If you need additional field, you can simply adjust the tables and server-views and add them to the form.