0% found this document useful (0 votes)

2 views

GLPI_Documentation_Raw_English

Uploaded by

u8md8

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as TXT, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2 views

GLPI_Documentation_Raw_English

Uploaded by

u8md8

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as TXT, PDF, TXT or read online on Scribd

You are on page 1/ 321

GLPI User Document ation

Version 10.0
GLPI Project, Teclib'
21 février 2025

Table des matières

1 Préface
3
2 Inst allation
5
3 Sommaire
7
3.1 First Steps with GLPI
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
7
3.2 Modules
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
23
3.3 Advanced Con˝guration
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
313
3.4 GLPI command-line inter face
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
316
3.5 Glossar y
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
332
4 Licence de cette document ation
339
Index
341
i

GLPI User Document ation, Ver sion 10.0

.
Avertissement
La documentation est en cours de réécr iture. Il est for t probable que cer taines
par ties soient obsolètes, qu'il y ait
des liens mor ts, etc.
Table des matièr es
1

GLPI User Document ation, Ver sion 10.0

2
Table des matièr es

CHAPITRE
1
Préface
Cette documentation couvre l'utilisation de GLPI (Gestion Libre de Parc Infor
matique) !
Solution libre et open source pour la gestion des actifs infor matiques et le ser
vice d'assistance, et plus encore. GLPI
est une application web conçue pour gérer l'ensemble de vos problématiques de
gestion de parc infor matique depuis la
gestion des stocks de composants matér iels et logiciels jusqu'à la gestion de
l'assistance aux utilisateurs.
Ce guide est destiné à donner une vue d'ensemble de GLPI pour les administrateurs
et les utilisateurs.
Chaque par tie peut être consultée indépendamment même si pour des raisons de
logique nous vous recommandons de
lire entièrement cette documentation.
3

GLPI User Document ation, Ver sion 10.0

4
Chapitr e 1. Pr éface

CHAPITRE
2
Installation
La
documentation d'installation de GLPI
est disponible séparément.
5

GLPI User Document ation, Ver sion 10.0

6
Chapitr e 2. Inst allation

CHAPITRE
3
Sommaire
3.1
Fir st Steps with GLPI
Ever ything you need to know to get star ted with GLPI !
3.1.1
Gener al
Choose a web browser
GLPI requires the use of a web browser.
Optimal functioning of the application is obtained by using a moder n browser
compliant with web standards.
The following web browsers are suppor ted :

Edge

Firefox (including 2 latests ESR version)

Chrome
GLPI also works on mobile ; it is generally compatible with the mobile versions of
the suppor ted browsers.
How to connect
Open your browser and go to the GLPI homepage (
https://{glpi_address}/
).
Access to the full functionality of the application requires authentication. An
unauthenticated user can possibly access
cer tain functions if GLPI has been con˝gured to allow it :

View the
FAQ
(Frequently Asked Questions),
Open a ticket,

. . .
Depending on the pro˝le of the authenticated user, they may be shown the
standard inter face
, or
simpli˝ed inter face
.
7

GLPI User Document ation, Ver sion 10.0

End your session
To log out, click the Logout button in the top r ight of the screen. Once logged
out, you will be redirected to the login
page.
3.1.2
U nder st anding the inter face
Depending on the user's pro˝le, some menus and content may di˙er, but the logic of
the inter face remains the same.
The GLPI inter face is made up of di˙erent areas g rouping together the
application's functionalities according to their
nature.
1.
The user menu allows you to manage your preferences, access help, change the cur
rent language, change your
cur rent pro˝le and entity, and disconnect.
2.
The main menu allows you to navigate through the di˙erent modules.
3.
The breadcr umb trail allows you to locate the context of use of the main work
area.
4.
The main working area is the pr ivileged space for interaction with the
application.
5.
The search box allows you to per for m a global search at any time.
3.1.3
Manag e your password
The change password for m can be found in
user preferences
.
You must enter and con˝r m your password before validation. The administrator can
disable this feature, so the change
password area does not appear in this case.
In the event that the user has forgotten their password, the possibility of
resetting it is o˙ered to them from the login
page. The link is only present if noti˝cations are enabled.
Only users with an e-mail address de˝ned in GLPI and not authenticating via an
exter nal source (LDAP, mail ser ver,
etc.) can use this functionality. Once the renewal request has been made by enter
ing their e-mail address, the user
receives an e-mail providing them with a link allowing them to reset their
password.
Passwords must follow the de˝ned secur ity policy. A real-time check of the entered
password is then car r ied out.
8
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
3.1.4
Manag e your Pr efer ences
User preferences are accessible from the
Preferences
tab of the user for m by clicking on your name at the top r ight of
the inter face, from any page.
Each authenticated user has the possibility to modify his preferences if they have
the
Personalize
update r ight in their
pro˝le.
ò
Note
These options over r ide the default ones set in the general setup. For more infor
mation about the available options
refer to the
general setup documentation
.
Main Tab
Here the user can modify the usual personal infor mation :

Sur name

First name

Email address

Phone numbers

Location

Language

. . .
ò
Note
Some ˝elds cannot be modi˝ed if they come from an LDAP director y.
A user can add email addresses and select the default address, which will be used
for sending noti˝cations.
They can also specify some default behaviors of the application, such as the
selected pro˝le and entity. They can also
tur n o˙ noti˝cations for actions they take.
Depending on the pro˝les, the exper ienced user can also choose to exit the nor mal
application mode. In debug mode,
GLPI displays er rors, all var iable values, SQL quer ies, etc. It is useful to
activate this mode in the event of GLPI
3.1. Fir st Steps with GLPI
9

GLPI User Document ation, Ver sion 10.0

malfunction. A maximum amount of infor mation can therefore be communicated to the
developers. This mode also
allows you to have additional infor mation on di˙erent objects in a speci˝c tab
(noti˝cations, etc.).
Per sonalization Tab
This tab allows you to modify the general display preferences applied to a given
user. These parameters take pr ior ity
over those de˝ned in the general con˝guration.
ò
Note
The Number of results per page value shown here cannot exceed the maximum value set
in the general display
options.
Note that the Remote access key section allows you to regenerate the secur ity key
used to access the pr ivate ˛ows
o˙ered by GLPI. Cur rently the ICAL and WEBCAL ˛ows of the planning are protected
by this secur ity key which is
integ rated into the url.
Per sonal View Tab
Lists custom views de˝ned in objects by the user. In par ticular, it allows you to
delete the personal views de˝ned to
retur n to global views.
3.1.5
N avig ate GLPI modules
The var ious functions of GLPI have been g rouped into several modules, built
around similar contexts of use. The top
bar of the inter face allows you to navigate between these modules :

The
Assets module
provides access to the var ious inventor ied mater ials,

The
Assistance module
allows you to create and monitor tickets, problems and changes ; as well as see
statistics.

The
Management module
allows you to manage contacts, suppliers, budgets, contracts and documents.

The
Tools module
allows you to manage projects, notes, the knowledge base, reser vations, RSS feeds
and view
repor ts.
10
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The
Administration module
allows you to administer users, g roups, entities, pro˝les, r ules and dictionar
ies. It
also allows the management of the email queue.

The
Setup module
provides access to the general con˝guration options of GLPI : noti˝cations,
collectors, auto-
matic tasks, authentication, plugins, exter nal links, SLA, management of titles,
components as well as control
of the uniqueness of ˝elds.
The menus presented var y according to the author izations of the logged in user.
The navigation context is presented to
the user in the breadcr umb trail.
ò
Note
You will ˝nd at the bottom r ight a button allowing you to quickly retur n to the
top of the page if necessar y.
There are keyboard shor tcuts that allow you to navigate from one module /
submodule to a nother. Here is the list of
these shor tcuts :

1
=> Home

Assets

o
=> Computers

s
=> Software

Assistance

t
=> Tickets

a
=> Statistics

p
=> Planning

Management

d
=> Documents

Tools

b
=> Knowledge base

r
=> Reser vations

e
=> Repor ts

Administration

u
=> Users

g
=> Groups

Setup

n
=> Dropdowns
ò
Note
The combination of keys to associate with these shor tcuts var ies depending on the
operating systems and browsers
used. Here are some examples according to the browsers :

Mozilla Firefox / Chrome

Simultaneously press the keys
Alt
,
Shift
and
the desired shor tcut
.

Opera
Simultaneously press the keys
Esc
,
Shift
and
the desired shor tcut
.
In addition, since version 9.2, GLPI o˙ers navigation with approximate search
(fuzzy) accessible from the keyboard
shor tcut
Ctrl
+
Alt
+
G
. This will open a modal window allowing you to ˝lter, via a search ˝eld, all the
men us of
GLPI (all the levels are present, you have for example access to the 3rd level such
as the dropdowns or the components).
In this window, additional shor tcuts are available :

^
and
_
in order to navigate through the results

Enter
to change the active glpi page on the selected result

Esc
to close the window.
3.1. Fir st Steps with GLPI
11

GLPI User Document ation, Ver sion 10.0

3.1.6
User inter faces
ò
Note
The choice of the default inter face as well as the visiblity of di˙erent modules
can be con˝gured in the pro˝les or
from
the user's preferences
.
St andard Inter face
This is the main inter face of the application. All the modules are available, but
there are limits depending on the pro˝le
settings.
12
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The home page of the standard inter face provides a summar y view for quick access
to active elements (tickets, notes,
planning, contracts, etc.).
It is divided into 5 views :

Dashboard
A customizable dashboard

Personal view
Shows the tickets opened, rejected, to be processed, to be approved (for which the
logged-in user is the
requestor) or those on which this user has an interaction as a validator or
technician (awaiting validation,
in prog ress, to be closed, in waiting). This view also o˙ers him cur rent issues,
his schedule and available
notes.

Group view
O˙ers the same infor mation about tickets and issues as the personal view, but
using the g roups to which
it belongs as a reference. Depending on their pro˝le, they may or may not have
access to the tickets for
which their g roups are requesting.

Global view
O˙ers statistics on tickets and issues according to their status and on contracts
according to their expira-
tion date. It also o˙ers the view of the late st additions of objects in GLPI.
Depending on the con˝guration
used, new tickets can also be presented in this tab.

RSS feed
Proposes the content of de˝ned RSS feeds.
RSS feeds are managed from the # Tools > RSS Feeds #
menu
.
ò
Note
For Personal and Group views, only tables with infor mation are displayed.
ò
Note
3.1. Fir st Steps with GLPI
13

GLPI User Document ation, Ver sion 10.0

Two secur ity messages may be displayed when you log in for the ˝rst time after
completing the installation proce-
dure.
The ˝rst asks you to change the passwords of the accounts created by default in
GLPI, the second asks you to delete
the director y
glpi/install
. There may also be one or more other messages here related to secur ity or needed
database schema changes
As long as you have not per for med these operations, the messages will remain.
Sim pli˝ed Inter face
It is the most restr ictive inter face of the application and is built for an end-
user more than a technician. Therefore, the
number of available modules is reduced to a minimum.
It is intended for users with ver y limited per missions in the application such as
the built-in self-ser vice and helpdesk
pro˝les.
In the default con˝guration, a user can, from this inter face, only create tickets,
follow the processing of their tickets,
make reser vations, view the notes or public RSS feeds (or create pr ivate notes or
feeds) and consult the Frequently
Asked Questions.
The home page o˙ers the number of its tickets according to their status as well as
the most popular and recent FAQ
topics.
3.1.7
View and manag e r ecords
The display of all the lists of records and of all the details concer ning a record
always works in the same way in GLPI.
Whether it's a list of computers, phones or tickets, the presentation follows the
same pr inciple.
A list of elements can be obtained in 2 ways :

From the search engine

14
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

From the search engine, after deter mining the cr iter ia and validating the
search, a list of records is
displayed. By default, no search cr iter ia limit the list of recordings o˙ered and
the display is limited to
the ˝rst
x
records in the list, which is con˝gurable in the preferences.

From another list

Some tab s o˙er a list of related items. For example, from a list of computers,
click on the name of a
computer then navigate to the software tab. The list of software installed on this
computer is displayed.
Details conce r n ing a record are displayed in the for m of tabs g rouping
together similar infor mation. For a computer,
the ˝nancial infor mation and the software list are in two separate tabs.
Customize the display
The columns displayed from the complete list of the inventor y can be con˝gured.
Click on the button
. It is
possible to add, delete and order the displayed columns.

The global view applies to all pro˝les having access to a par t of the inventor
y : the modi˝cation of this par t will
therefore be visible by all users.

The personal view applies only to the logged-in user and over r ides the global
view settings. This view is only
available if you have the
User view
r ight regarding the
Search result display
.
This tab also allows you to reset the display customization of the di˙erent lists.
The user can, for each
type of object, retur n to the default display by deleting this personalization.
3.1.8
Search for information in GLPI
GLPI has a search engine allowing you to display a set of elements satisfying a cer
tain number of cr iter ia. The proposed
lists are paginated. A navigation bar at the top and bottom of the list is used to
de˝ne the number of items to display
per page and to navigate between pages.
A global search engine (that is, one that can use data from objects of di˙erent
type) is also available.
In addition to the list of elements cor responding to the stated cr iter ia ; these
lists o˙er some additional features :

Expor t in di˙erent for mats (CSV, PDF, . . .)

Massive (Bulk) actions

A
bookmarks
system to save searches
Per form a basic search
The basic search makes it possible to car r y out multiple searches con˝gured and
sor ted, on one of the types of the
inventor y. Depending on the data on which the search is car r ied out, the
following operators can be proposed :

contains
,

is
,

is not
,

before
,

after
.
Searching on dates allows you to specify a speci˝c date (
Specify a date
) or to de˝ne it in relation to the cur rent date
(
Now
,
+
or
- X hour(s)
,
day(s)
,
month
or
year(s)
). It is also possible to specify a search before or after a given date, as
de˝ned inter vals (
Monday
,
Last Saturday
,
Star t of month
,
Star t of year
,
Star t of year
, etc).
For labels, it is possible to search for a given value (
is
). If the dropdowns can be visible in the sub-entities, the choices
under and not under appear. The cr iter ia are added with the
+
on a g ray backg round.
For example, to ˝nd computers with more than 1024 MiB of memor y and more than 80%
free disk space :
-
Type
Field
Com parison
Value
-
simple
Memor y
contains
> 1024
AND
simple
Volumes - Percentage free
contains
> 80
3.1. Fir st Steps with GLPI
15

GLPI User Document ation, Ver sion 10.0

ò
Note
Once the cr iter ia have been de˝ned, the search is launched by pressing the Search
button.
Per form a multi-criteria search
The multi-cr iter ia search makes it possible to re˝ne the search by extending it
to other types of objects by adding global
search cr iter ia. This type of search is obtained by adding cr iter ia with the
+
on a white backg round.
For example, to ˝nd computers with more than 1024 MiB of memor y and more than 80%
free disk space, attached to
a 17-inch monitor and having LibreO˚ce software installed :
-
Type
Field
Com parison
Value
-
simple
Memor y (Mio)
contains
> 1024
AND
simple
Volumes > Percentage free
contains
> 80
AND
multi
Monitor > Size
contains
17
AND
multi
Sof tware > Name
contains
LibreOffice
Items in Tr ash
Some items in GLPI can be trashed. To view them in order to restore them or delete
them per manently, click on the
icon representing a recycle bin. To retur n to the display of active elements,
click again on this icon.
Per form an advanced search
Here are some examples of search operators :
NULL

Find the records with such empty ˝eld with a date ˝eld : <number_of_months or>
number_of_months

Search for mater ials with a deadline cor responding to the number of months

Search for computers that are 5 years old : Date of purchase contains <-60.
^123
Find the records containing 123 at the star t of the ˝eld.
.
Avertissement
On some systems, you have to type ^, the space bar then the ˝rst character.
^Windows
Find records containing Windows 2000, Windows XP but not with Windows.
123$
Find the records containing 123 at the end of the ˝eld.
^123$
Find records containing only the text 123.
Two search criteria linked by the operator
AND NOT
Find records that do not match a cr iter ion (other than).
Entity is # Root entity #
AND NOT
Type contains # Laptop #
Search for all computers in the # Root entity # which are not laptops.
16
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

[Year]-[Month]-[Day]
(YYYY-MM-DD)
Search by date.
\\
For secur ity reasons, the
\\
operator is not usable.
Expor t the r esult of a search
The expor t of the search result in SLK or CSV spreadsheet for mats, or in PDF for
mat can be done in two di˙erent
for ms :

Current page
expor ts only the data displayed on the screen (for example the ˝rst 10 results out
of 200)

All pages
expor ts all of the search results
There is also an option to copy the names of the results to the clipboard (Ex :
Computer names).
The SLK for mat can be used by a lot of spreadsheet software. Fields that are too
long will be tr uncated when using
software that does not fully comply with the standards. In this case, it is
preferable to use the expor ts in CSV for mat.
If the data expor ted in CSV for mat is impor ted into Microsoft Excel software,
accented characters may not be displayed
cor rectly. This software seems to have di˚culty with data encoded in UTF-8.
You can expor t search results by clicking on the
Expor t
button above the search results list.
Search views
The are two di˙erent views for search results in GLPI.

List/Table - The default view that shows results in a table with the ˝eld names
along the top as headers and each
result as a row

Map - Shows the location of the results on a map

The switch to the map view, click on the map toggle above the search results.
ò
Note
If an item type does not have the ability to have a location, then the map view
toggle will be hidden.
Using the t able view
In the table view, you have the option to sor t the results by any of the displayed
˝elds by clicking on the relevant
column headers. You may per for m a multi-sor t by holding the
Ctrl
or
Command (MacOS)
keys while left clicking on
the column header. Clicking on column headers multiple times will cycle between sor
t directions and removing the
sor t.
At the bottom of the results table is a dropdown that can be used to change the
number of results that will show on
each page. There are also pagination controls that let you navigate between the
search results pages, and an indicator
of where you are cur rently at within the results (Ex : Showing 1 to 20 of 30
rows).
3.1. Fir st Steps with GLPI
17

GLPI User Document ation, Ver sion 10.0

Per form massive actions
A massive action system is integ rated into the search engine. It allows you to
make bulk modi˝cations and per for m
actions to all the selected elements. Some examples of the available massive
actions (Will di˙er based on the type of
item) :

Put in trashbin

Delete per manently

Restore

Connect
/
Disconnect

Install

Update

Add a contract

Enable the ˝nancial and administrative infor mation

Add to transfer list

Synchronize
To use it, simply select the elements for which you want to per for m an action
then click on the Actions button available
at the top and bottom of the list. Then, once the type of action has been selected,
options are optio nally presented, as
well as a validation button.
The results of the actions as well as the infor mation messages are presented at
the end of the execution of all the actions.
ò
Note

You will ˝nd in the headers of the table (at the top and at the bottom) a checkbox
allowing you to select or
unselect all the elements of the list.

A similar system of actions is available in cer tain lists present within the
objects themselves. The operation
is identical to that explained here.
.
Avertissement
The number of elements that can be handled simultaneously is limited by the values
of
max_input_vars
or
suhosin.post.max_vars
in your PHP con˝guration. You may therefore get a message indicating that massive
edits are disabled. You just need to increase the values of your PHP con˝guration
or reduce the number of items
displayed.
Quic k search
This tool is located at the top r ight of the GLPI screen. It allows searching
within elements including but not limited
to :

Tickets

Problems

Changes

Projects

Computers

Monitors

Software

Network Equipment

Per ipherals
18
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Pr inters

Phones

Contacts

Suppliers

Documents

Budgets

Licenses

Users

Groups
ò
Note
The search is car r ied out only on the ˝elds displayed by default for each of the
elements mentioned above. In
essence, it is the same as an
items seen
search on each type of element.
3.1.9
Saved Searches
GLPI o˙ers a system for saving searches (bookmarks). Once the search is done, it is
possible to save it from a star-shaped
button accessible in the search for m.
There are two types of saved searches :

Private
searches : Usable by all users and they are only accessible by their author

Public
searches : Can only be created by author ized users and are accessible by all users
provided they belong
to the con˝gured entities
Saved searches can be accessed by clicking on the star shaped button in the user
menu.
3.1. Fir st Steps with GLPI
19

GLPI User Document ation, Ver sion 10.0

20
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

From this inter face, it is possible to :

Reorder pr ivate searches (drag & drop) - public searches use automatic sor ting

Select a default search (only one possible per type of object) by clicking on the
star icon

Access the search results (by simply clicking on it)

Access the saved searches management inter face, by clicking on the wrench icon at
the top r ight
.
Avertissement
Setting a par ticularly heavy search as the default display can have catastrophic
e˙ects on the overall per for mance
of the application !
Display of counter s
The GLPI settings are used to de˝ne whether the counters should be displayed or
not. In the case of research, it's a bit
more complicated.
This is because some searches can take a long time (and resources) to complete. In
order to limit the impact on per for-
mance, the heaviest requests are not counted by default. So that the execution time
of a saved quer y can be calculated ;
it must be executed at least once. A scheduled task is also o˙ered to calculate
execution times regularly (and thus avoid
requests that would have become heavy over time).
Administrators can over r ide the automatic count method, and have a search always
or never be counted. This possibility
should be used spar ingly.
Con˝guring aler ts
It is possible to con˝gure the sending of #aler ts# on a saved search using the
GLPI noti˝cation system . Sending a
noti˝cation is based on the number of results retur ned by the search, compared
with the chosen operator to the entered
value.
The noti˝cation(s) used are displayed for reference from the aler ts con˝guration
tab. For pr ivate research ; only the user
who created the search can be noti˝ed, using a template provided by default ; in
this case, a single noti˝cation will be
linked.
For public searches, a speci˝c event must be created, as well as a noti˝cation that
uses it. This is only possible from
the aler ts con˝guration tab.
Once the speci˝c noti˝cation is created, it has to be con˝gured by associating it
with a template and by selecting the
desired recipients. Note that it is possible to associate several noti˝cations with
the same search via the event that
cor responds to it.
ò
Note
As long as the noti˝cation speci˝c to a public search is not created ; it will not
be possible to add aler ts.
3.1. Fir st Steps with GLPI
21

GLPI User Document ation, Ver sion 10.0

3.1.10
Administering access controls
This section descr ibes how to administer the access control system that allows
each user to access a speci˝c context of
use.
In GLPI each user does not have access to the same inter face nor to the same same
functionalities. For each user,
a speci˝c context of use is deter mined, which g rants them access only to the
functionalities and infor mation that is
needed. Access to identity infor mation about the user allows us to deter mine his
or her author izations.
The ˝rst step is to con˝gure the desired authentication method(s). GLPI is able to
manage user authentication and
infor mation completely locally in its database, however it is recommended to
delegate the authentication to an exter nal
ser vice like LDAP. See
Con˝guring authentication methods
for more infor mation.
The impor t or creation of new users and management of users known to GLPI
including deletion, syncronization,
activation/deactivation and management of infor mation such as email, phone, etc is
covered in
the user administration
documentation
.
A user can associated with g roups, entities, and pro˝les which are the means of
deter mining usage contexts.
Groups allow users to be g rouped according to similar ities in skills or
organizational units. See
Administering groups
for more infor mation.
Entities allow you to segment your asset ˛eet, help desk, etc into depar tments
that are isolated from each other. See
Administering entities
for more infor mation.
Pro˝les are sets of per missions that can be g ranted to users. Multiple pro˝les
can be given to a user but only one can
be active at a time. See
Administering pro˝les
for more infor mation.
Finally, you can con˝gure Rules for assigning author izations to a user to
dynamically assign entities, g roups and pro˝les
to users.
3.1.11
Conclusion
To go fur ther, you are not alone !
GLPI is a community project. Its strength is its power ful community on which you
can rely to car r y out your project.
You will ˝nd a list of resources and discussion spaces that you can use to go fur
ther.
Plugin cat alog
The GLPI Project maintains a curated
catalog
of ˝rst-par ty and community-made plugins that can be used to expand
the functionality of GLPI. Plugins may be available outside of this catalog, but
they have not been ver i˝ed.
Plugin developers are encouraged to submit their plugin for approval and addition
into the catalog.
Discussion platforms
The
for um
is a community suppor t space. Ask your questions on this space, making sure to
respect the r ules of operation
which that are speci˝c to it. You can then bene˝t from the advice, opinions, help
from other users. Don't forget to do
the same after wards with new beginners to share your exper ience.
A full, up to date list of discussion platfor ms can be found on the main
GLPI Project website
.
22
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Par tner s of the GLPI Project
The g rowing demand for ser vices around the GLPI project has given bir th to a
network of par tners. These par tners are
able to br ing you the high value-added ser vices and the assistance to the GLPI
deployment that you need. As an end
user, you are assured of the close collaboration between the GLPI project and its
par tners and you br ing your suppor t
to the project since each par tner is committed to actively contr ibute to the GLPI
project.
3.2
Modules
3.2.1
Over view
Actions
The di˙erent actions that are available on an object depend on the per missions
assigned in user pro˝le.
Likewise, some actions in the tab depend on pro˝le per mission, such as mass
actions.
This page descr ibes only main actions that can apply to di˙erent types of objects.
If an action is speci˝c to an object,
it will be descr ibed in the documentation of this object.
Cr eation
The per mission to create an object depend on de˝ned per mission in user pro˝le.
For all inventor y objects, creation is realized in the same way :
1.
Connect to GLPI ;
2.
Go to the object page, for example
Assets > Computers
to add a computer ;
3.
Click on the # + # button located in hor izontal menu ;
4.
If the inventor y object has a template management, choose the template to be
applied ;
5.
Fill in the di˙erent ˝elds of the empty for m ;
6.
Validate.
An option located in user preferences,
Af ter creation, go to created element
, allows to choose, after creating an object,
if the newly created object is displayed or if a new empty for m is displayed in
order to create another object.
Modi˝cation
The per mission to modify an object depend on de˝ned per mission in user pro˝le.
For all inventor y objects, creation is realized in the same way :
1.
Connect to GLPI ;
2.
Go to the object page, for example, to modify a computer, go to
Assets > Computers
;
3.
Or alter natively : search the object in the search engine available on top of
objects list ;
4.
Two choices of modi˝cation are then possible :

Unitar y modi˝cation :
1.
Click on object name ;
2.
Modify ˝elds ;
3.
Click on button
Update
.

Mass modi˝cation :
1.
Select the checkbox located on the left of the object name ;
2.
Click on button
Actions
;
3.
Choose ˝eld to be modi˝ed ;
4.
Enter new ˝eld value ;
5.
Click on button
Post
.
3.2. Modules
23
GLPI User Document ation, Ver sion 10.0
Display
The per mission to display an object depend on
read
per mission in user pro˝le.
If the per mission to display an object is not g ranted, the name of this object
will not appear in GLPI di˙erent menus. For
example, if the per mission to read a
Computer
type object is not g ranted in the user's pro˝le, the sub-menu
Computer
will not appear in menu
Assets
, even if the per mission to modify a
Computer
is g ranted.
For all inventor y objects, displaying an object is realized in the same way :
1.
Connect to GLPI ;
2.
Go to the object page, for example, to display a computer, go to
Assets > Computers
;
3.
Or alter natively : search the object in the search engine available on top of
objects list ;
4.
Click on object name..
Att aching a document
When available for the item type, attaching a document is realized in the same
way :
1.
Connect to GLPI ;
2.
Go to the object menu, for example, to attach to a computer, go to
Assets > Computers
;
3.
Or alter natively : search the object in the search engine available on top of
objects list ;
Two possibilities are available :

Unitar y attachment :
1.
Click on the object name ;
2.
Select tab
Documents
;
3.
Select a document or click button
Choose
to add a new document ;
4.
Click on button
Add
.
Mass attachment :
1.
Select the checkbox located on the left of the object name ;
2.
Click on button
Actions
and choose
Add a Document
GLPI will then display the object for m with newly attached document.
Att aching a contr act
When available for the item type, attaching a contract is realized in the same
way :
1.
Connect to GLPI ;
2.
Go to the object menu, for example, to attach to a computer, go to
Assets > Computers
;
3.
Or alter natively : search the object in the search engine available on top of
objects list ;
Two possibilities are available :

Unitar y attachment :
1.
Click on the object name ;
2.
Select tab
Contracts
;
3.
Select a contract ;
4.
Click on button
Add
.

Mass attachment :
1.
Select the checkbox located on the left of the object name ;
2.
Click on button
Actions
and choose
Add a Contract
GLPI will then display the object for m with newly attached contract.
24
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Tr ansfer between entities
Entities open the possibility to de˝ne transfer pro˝les in order to move elements
between entities. This allows in par-
ticular to switch from a single entity GLPI to a GLPI with multiple entities.
To make a transfer, it is ˝rst necessar y to check that the used pro˝le has per
mission to make transfers (
Administration
> Pro˝les > Administration #> Transfer read per mission
).
In order to make a transfer :
1.
Con˝gure the actions per for med by the transfer
Administration Rules Transfer
;
2.
Check that pro˝le per for ming transfer has per mission on the or igin entity and
on the destination entity (simplest
solution is to use a recursive pro˝le from root entity) ;
3.
Go to root entity (
See all
) ;
4.
From objects list, select the element to be transfer red ;
5.
Choose
Add to transfer list
then
Validate
;
6.
In
Transfer mode
, select a transfer con˝guration pro˝le that has been created at step 2 ;
7.
Select destination entity, where object will be transfer red to ;
8.
Click on
Transfer
;
9.
Check in destination entity that object is e˙ectively there.
ò
Note
If a linked element does not exist in destination entity, it will be automatically
created if transfer pro˝le asks to keep
it.
Example : transfer of a
Computer
with a provider de˝ned in accounting infor mations : if this provider exists only
in or igin entity, it will be created in destination entity ; however, a provider
de˝ned in root entity with recursivity
enable will not be recreated.
.
Avertissement
Location and g roup must be updated for destination entity.
Deletion
The per mission to delete an object depend on
delete
per mission in user pro˝le.
For all inventor y objects, deleting an object is realized in the same way :
1.
Connect to GLPI ;
2.
Go to the object page, for example, to delete a computer, go to
Assets > Computers
;
3.
Or alter natively : search the object in the search engine available on top of
objects list ;
4.
Two choices of deletion are then possible :

Unitar y deletion :
1.
Click on object name ;
2.
Click on button
Delete
;

Mass deletion :
1.
Select the checkbox located on the left of the object name ;
2.
Click on button
Actions
;
In both cases, a choice will have to be made between :
3.2. Modules
25

GLPI User Document ation, Ver sion 10.0

Move to trash bin

if object has an associated trash bin. In this case, object may be restored later
on ;

Delete per ma nently

if object does not have an associated trash bin. In this case, GLPI will ask for
con˝r mation
before real deletion of the object in the database.
Tem plate manag ement in GLPI
Introduction
For some object types in GLPI, it is possible to create new objects (computers for
example) using prede˝ned templates.
A template de˝nes a creation model in which some ˝elds are either already ˝xed or
computed using a function, for
example in the case of a computer a function which would compute the inventor y
number.
Template management is accessible via the button
Templates
located in the menu bar.
Assets
For assets, the template de˝nes a default standard object in which some ˝elds are
pre-˝lled and can later be reused to
create new objects. This allows to simplify drastically adding a large number of
objects that are nearly identical.
As an example, in order to prepare inventor ying 20 identical pr inters in which
only ser ial number and inventor y number
di˙er :

˝rst, a template would be created cor responding to this pr inter model

in this template, all ˝elds that will not changed are ˝lled (vendor, model. . .)

the 20 pr inters will then be created from this template

When creating a new pr inter from this template, ser ial number and inventor y
number are the only ˝elds to be entered ;
other ˝elds are already set.
Incr ement
A automatic ˝ll and increment mechanism is provided for some ˝elds that can be
identi˝ed with to the
. These
˝elds (name, inventor y number. . .) are then automatically completed when creating
the object. To use this mechanism,
the cor responding ˝eld in the template must contain a str ing following a syntax
which is descr ibed below.
The ˝eld str ing :

must star t with character

<
and must end with character
>
.

can contain the following special characters which are replaced automatically :

\g
look up of number in all identical ˝elds based on the same for mat ;

#
: is replaced by a counter having as many digits as there are consecutive
#
characters ;

\Y
: is replaced by the year on 4 digits ;

\y
: is replaced by the year on 2 digits ;

\m
: is replaced by the month ;

\d
: is replaced by the day.
For example, when creating a pr inter, it is possible in the pr inter template to
use this mechanism to automatically
generate inventor y numbers.
Let suppose that we want an inventor y number under the for m :
YEAR+MONTH+DAY+˝xed code str ucture equals to
555 + ˝xed operation code equals to 1234 + 2_DIGITS_COUNTER
; the n the inventor y number ˝eld in the template
will be :
<\Y-\m-\d-555-1234-##\>
.
On each pr inter creation, the ˝rst pr inter will have its inventor y number be
1984-JAN-02-555-1234-01
, the second
pr inter
1984-JAN-02-555-1234-02
and so on.
26
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
Tic ket tem plates
As with inventor y objects, templates are available for tickets. A ticket template
allow to customize the ticket creation
inter face based on ticket type and categor y.
The behaviors that can be modi˝ed are :

list of ˝elds which are mandator y to create the ticket ;

list of ˝elds which value is prede˝ned ;

list of ˝elds which will be masked.

ò
Note
For mandator y ˝elds control, the only ˝elds that will be controlled are the ˝elds
available in the user's inter face.
Therefore, if a ˝eld is de˝ned as mandator y but is not visible in the inter face,
it will not tr igger an er ror. When
de˝ning mandator y ˝elds, the inter faces in which these ˝elds are used are
displayed.
A template is attached to the entity where it has been created and can be visible
in sub-entities.
Default templates can be de˝ned at entity level or at pro˝le level. For the
pro˝les, only the template of the root entity
that are visible from sub-entities can be attached.
Default templates can also be de˝ned by ticket categor y.
When creating a ticket, the used template is, with pr ior ity order :
1.
First, the template de˝ned in the selected categor y and type
2.
Then, the default template for the cur rent pro˝le of the user
3.
Last, the default template for the creation entity of the ticket
.
Avertissement
In last two cases, if the template de˝nes a new couple type/categor y, then the
˝rst case is then tested again with
these new values.
ò
Note

When updating a ticket, the same pr ior ity order is applied to deter mine
mandator y ˝elds.

If one of the parameter entity, pro˝le, type or categor y is modi˝ed when ˝lling
the ticket, the template to
use is then searched again according to these new values.

The template is used to create recur rent tickets.

St atus in GLPI, speci˝c view
Status infor mation is frequently used to sor t hardware that is disposed,
available, assigned. . . It is possible to create new
status values speci˝c to the infor mation system managed by GLPI.
De˝ning new status and the object types they will be used for is under GLPI
administrator's responsibility, see
dropdown
con˝guration
. These de˝ned status can be recursive, in order to ease management.
Modifying an element's status can be done either from the element's for m or using
mass actions.
A repor t can display a summar y of statuses sor ted by asset types. Global search
on inventor y allows to quer y inventor y
elements by status.
3.2. Modules
27

GLPI User Document ation, Ver sion 10.0

Kanban
The Kanban is a view to display Projects, Tickets, Changes or Problems on a task
board.
For Projects, you can view a global Kanban involving all cur rent Projects and
Project Tasks or view a Kanban for a
speci˝c Project and its child Projects and tasks.
For Tickets, Changes, and Problems, only a global Kanban is available and is
speci˝c to each type (you cannot view
tickets and changes on the same Kanban). For the sake of berevity, the Kanban for
Tickets, Changes and Problems is
refered to as the
ITIL Kanban
in the rest of this document.
Cur rently, the columns of the Kanban represent the status of the items. Each item
is represented by a card inside the
columns.
For Projects, you can add new statuses directly from the Kanban since those are
con˝gurable. The Project Kanban has
a special column for # No status # that is always shown and cannot be changed.
For the ITIL Kanban, you can only choose to show or hide the di˙erent statuses
since they are not con˝gurable. The
ITIL Kanban also has a limitatio n placed on the # Closed # status column due to
the number of items that would show
there. You can drag cards into this column to update their status, but they will
not be displayed here.
Cards
Each card on the Kanban shows some basic infor mation including : - The name of the
item which is shown as the
card's titles - The prog ress of sub-tasks (Project tasks and child projects for
Project Kanban and child tickets for Ticket
Kanban) - If the item is a milestone (Project Kanban) - The team for the item shown
Hover ing over the title of a Kanban card will show a preview of the item's
content/descr iption.
Each card also has a # . . . # menu which includes : - Goto : Navigates to the
item's full for m - Delete : Delete the item
(this actually deletes the item and doesn't just remove it from the Kanban)
Clicking on the card's title will display a ˛yout panel which displays some of the
same infor mation as the card itself
but also includes : - A read-only view of the item's content - A full list of the
item's team along with the ability to add
and remove team members directly without having to go to the item's full for m
Team manag ement
In GLPI, there are multiple notions of a # Team #.
For Tickets, Changes, and Problems you have requesters, obser vers, and assignees.
For Projects and Project tasks you
have a simple # team # (assigned in the team tab) along with managers (assigned on
the main for m).
ò
Note
The Kanban team management feature does not cur rently allow changing managers from
the Project Kanban
The Kanban presents these di˙erent notions as a simple # Team # where each member
has a speci˝c role and shows
them all in a centralized list.
Team members can be adde d or removed from a card's panel view which can be
accessed by clicking on the card's title.
When adding a team member, you will be asked to select a role and then the type of
member (user, g roup, etc), and
then a speci˝c member.
28
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Searching and Filtering
The Kanban has a search and ˝lter system that lets you ˝lter which items are shown
on the Kanban.
Regular searches can be done by simply typing one or more search ter ms into the
search box.
When you click in the search box, a suggestion tooltop will be displayed that shows
a list of the available ˝lter
tags
.
There are di˙erent tags depending on which Kanban you are using and new tags can be
added by plugins.
Some of these tags incluse : - title : The name or title of the item - type : The
type of the item (On the Project Kanban
you can use this to ˝lter Projects or Project tasks) - content : The content of the
item - team : The team of the item
(searches regardless of the member type)
Each suggested tag may have zero or more buttons with an icon or character in them
which represent di˙erent modi˝ers
for the ˝lter.
The common modi˝ers : - ! : Represents a negation or exclusion - # : Represents a
regular expression
As you type, the list of suggested tags will be adjusted to match what you have
typed. You can manually add a ˝lter
by typing it out such as :
title :this
or
!title :notthis
You can also select the tag or modi˝er from the list of suggestio ns
using your mouse (or touch) or using the keyboard ar row keys to navigate and the
enter key to select. If you select a tag
or modi˝er from the suggestion list, it will add it to the search box in
edit
mode which lets you add the ter m.
Each ˝lter is represented in the search box with a colored backg round based on its
type or modi˝er. For example,
exclusions are red, regular expressions are g reen, regular tags are blue and
untagged searches (regular search) are
black.
To initiate the search, you will need to press the enter key on your keyboard or
click/touch outside of the search box.
You can edit a search ter m by clicking on it or by navigating using the ar row
keys and then pressing backspace when
the cursor is placed to the r ight of the ter m.
You can remove a ter m by removing the entire content including the tag por tion or
by clicking the # x # button in the
ter m.
3.2.2
Assets
The GLPI Asset module is used to manage all the assets that are par t of your IT
infrastr ucture.
Asset manag ement in GLPI
In order to manage hardwares and software of an IT infrastr ucture, GLPI allows
natively to list all the assets that are
used inside the managed organization.
However, it is possible to automate infor mation pushing from the assets thanks to
the native inventor y and GLPI Agent
and third-par ty tools.
More infor mation on the GLPI Agent can be found in its dedicated
documentation
.
ò
Note
If you have used Fusion Inventor y in the past with GLPI, it is ver y easy to mig
rate over to the GLPI Agent due to
the native inventor y remaining compatible with the Fusion Inventor y agent.
GLPI also suppor ts automatic inventor y via multiple plugins including but not
limited to :

The
Fusion Inventor y
plugin transfor ms GLPI into an inventor y ser ver with the Fusion Inventor y
agents inter-
facing directly with the GLPI ser ver.

The
ocsinventor yng
plugin allow to synchronize the GLPI database with the
OCS Inventor y NG
inventor y tool :
the agents installed on the computers inter face directly the the OCS Inventor y NG
ser ver.
3.2. Modules
29

GLPI User Document ation, Ver sion 10.0

Available types
Com puter s
In a computer for m, the following infor mation is available :

Operating system :

Name

Version

Ser vice pack

Ser ial number

Product ID

. . .

General character istics :

Manufacturer
Model

Type

Ser ial number

. . .

Management infor mation :

Technical manager

Status

Location

. . .

Users :

Computer users, either known by GLPI or not

Other ˝elds are infor mative, such as
Network
(connexion type) and
Update source
(where are computer updates coming
from (Windows update, yum, apt. . .).
It is possible to use
templates with computers
.
ò
Note

when GLPI is used with an inventor y tool, var ious infor mation provided by the
tool itself are also available

a computer can be a ser ver, a desktop computer or a laptop ; to di˙erentiate

them, it is possible to use the
type
˝eld
The di˙er ent t abs
Oper ating systems
The infor mation on operating systems for a computer are visible in tabs
Operating system
for a Computer entr y.
An operating system is associated with the following elements :

Name
30
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Version

Architecture

Ser vice Pack

Ker nel

Edition

Product ID

Ser ial number

ò
Note
The creation and management of the titles for operating systems is located in the
menu
Setup > Drop-downs >
Operating systems
.
ò
Note
A deletion or addition of an operating system is recorded in the histor y of the
computer.
ò
Note
3.2. Modules
31

GLPI User Document ation, Ver sion 10.0

If using native inventor y or third-par ty inventor y tool, the operation system
infor mation can be automatically im-
por ted and updated.
Com ponents
This tab, named
Components
and visible in a
Computer
entr y, allows to manage the hardware components of a computer.
ò
Note
Adding or managing components is located in menu
Setup > Components
.
ò
Note
If several components of the same type are used, they will be g rouped in the view.
It is possible to add a component by ˝rst selecting its family in the drop-down
list at the top of the table and then its
name and the number of components to add.
32
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Star ting from a computer view, it is possible to modify a component by clicking on
the link under its name.
To act on several components (for example modify an element of the component,
activate accounting infor mation or
modify them, delete a component. . .), ˝rst select the components and then use the
Actions
button present at the top or
the bottom of the list.
If several types of di˙ere nt components, not having the same character istics, are
selected for modi˝cation, in the actions
it will be asked on which component modi˝cation must be applied.
Selection button in left column allows to select all the components at once.
3.2. Modules
33

GLPI User Document ation, Ver sion 10.0

Selection at r ight of type column (g rayed line ) allows to select all components
of the same type (processor, memor y,
network inter face. . .).
ò
Note
It is possible to modify the character istics of a component only for one computer
From tab
Elements
of the component, click on the link
Update
.
Several tabs are then displayed :

Tab # Element - Link name of component # : list the character istics of this
component

Tab # Management # : manage administrative and accounting infor mation

Tab # Documents # : attached documents

Tab # Histor y # : histor y of modi˝cations

Tab # Contract # : contracts management

Tab # Debug # : only if you are connected in Debug mode

Tab # All # : all the infor mation are displayed on a single page
34
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
Ever y deletion or addition of a component is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the components infor
mation can be automatically impor ted
and updated.
Volumes
This tab, named
Volumes
and visible in a
Computer
entr y, allows to manage the volumes attached to a computer.
A volume attached to a computer is character ized by :

name

physical par tition

mount point
˝le system

total size

available size

cipher ing algor ithm and type

It is possible from a
Computer
entr y to add a volume by clicking on button
Add a volume
.
It is possible from a
Computer
entr y to modify an existing volume by clicking on the link under its name.
3.2. Modules
35

GLPI User Document ation, Ver sion 10.0

ò
Note
Ever y deletion or addition of a volume is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the volumes infor
mation can be automatically impor ted and
updated.
Sof twar e
This tab, named
Sof twares
and visible in a
Computer
entr y, allows to manage the software installed on a computer.
Those software are sor ted by their categor y and are character ized by name,
version and version status.
To install a software, ˝rst select its name in the drop-down list, then its
version.
36
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

It is possible to associate a license to a software on a computer.
To associate a license, ˝rst select the software in the drop-down list, then the
wanted license.
If the license is associated with a software that is already installed on the
computer, it will be presented in the list of
software.
Other wise it will be displayed in a separate table.
ò
Note

the drop-down list enumerates the software that are available in the entity

licenses management can be found in

Assets > Sof twares
. See Manage software
ò
Note
It is possible via mass actions to install on a computer a software selected from
its license.
ò
Note
Ever y deletion or addition of a software or a license is recorded in the histor y
of the computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the software infor
mation can be automatically impor ted and
updated.
3.2. Modules
37

GLPI User Document ation, Ver sion 10.0

Connections
This tab allows to manage the direct connections between a computer and its
connected elements.
Direct connections represent the relation between di˙erent hardwares linked either
physically or vir tually.
From a com puter
The connection can be made toward one or several elements of type display, pr
inter, per ipheral or phone. For each type
of connected object, its name, ser ial number and inventor y number are displayed.
From an element other than a com puter
To add a connection, select the computer in the drop-down list presented at top of
the table.
If this case, the connection can only be made to a single computer. The table will
list the name of this computer as well
as its ser ial and inventor y numbers.
ò
Note
The deletion of a connection can be made from the entr y of each connected hardware
(tab
Connections
) via mass
actions.
ò
Note
Ever y deletion or addition of a connection is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the connections infor
mations can be automatically impor ted
and updated.
38
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

N etwork por ts
This tab, named
Network por ts
and visible in a
Computer
entr y, allows to manage the network por ts attached to a
computer.
A network por t represents the output of a network inter face on a given hardware.
A por t is character ized by a number
and a name.
It is possible on a network por t to add one or more VLAN, these VLANs being de˝ned
by a name, an optional comment
and a VLAN number.
One or more
network name
can be associated to each network por t. This can be done in tab
Network name
.
ò
Note
When a network por t has only one network name, this name is displayed in the
network por t for m itself and it is
possible to modify the name directly. It is also possible to modify the network
name via its own for m, accessible
by clicking on the link under the name.
When a network por t has several network names, the only way to modify the network
names is via the network
name for m.
3.2. Modules
39

GLPI User Document ation, Ver sion 10.0

Network por ts can be of di˙erent types :

physical por t : ether net, WiFi. . .

Vir tual network por t

: local loop-back, alias, agg regates. . .

point to point : switched network. . .

The
Network por t
tab g roups in a table the por ts that are available on the equipment. The table
header contains the total
number of por ts and a link that allows to choose display options. This allows to
selectively display or mask infor mation
such as network data (IP. . .), por t character istics depending on its type, MAC
address, VLANs. . .
ò
Note
GLPI allows to present complex network connection with for example WiFi or Ether
net por t aliases associated to
VLANs g rouped in agg regates. . .
Manag ement of Ethernet network por ts
The Ether net protocol is classically used on inter nal networks.
An Ether net por t is character ized by its type (twisted pair, mono-mode/multi-
mode optical ˝ber. . .), a transfer rate
((10Mb, 100Mb, 1Gb, 10Gb. . .) and a MAC address. It is possible to associate to
the por t a network card and a network
plug.
Ether net connections are realized by linking two Ether net por ts, which requires
that there is a free por t on each equip-
ment to be connected. In general, a connection links a por t attached to a
computer, a per ipheral or a pr inter and a por t
attached to a network equipment (hub, switch).
Manag ement of WiFi network por ts
The WiFi protocol is widely used on wireless networks.
A WiFi por t is character ized by the mode of the network card (ad-hoc, access
point, repeater. . .), the WiFi protocol
version (ab, g. . .) and its MAX address.
It is possible to associate a network card to the por t, similarly to Ether net por
ts.
A WiFi network can be associated to a given por t. Apar t from its name, a WiFi
network has an ESSID and is charac-
ter ized by its type :
Infrastr ucture :
WiFi network with on or several access points and connected clients
Ad-hoc :
WiFi network between
similar systems without access points
Manag ement of local loop-bac k por ts
The local loop-back is a vir tual por t used by most equipments for inter nal
communication. It is this por t that is used
when connecting to
localhost
or
127.0.0.1
.
Local loop-back has no speci˝c attr ibute.
Manag ement of network por t aliases
A network por t alias is a vir tual por t that can re˝ne a physical por t.
On Linux, to each VLAN, when transmitted
# tagged #
, is associated a por t alias, for example
eth2.50
to represent
VLAN 50 on por t
eth2
.
A por t alias contains its base por t and a MAC address.
Note that when the or igin por t is changed, the MAC address of the new por t is
a˙ected to the por t alias.
40
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Manag ement of network por t aggr eg ates
A network por t agg regate is a vir tual por t that allows to g roup several
physical por ts.
On Linux, agg regates are represented by br idges
bridges <http ://www.linuxfoundation.org/collaborate/workgroups/networking/bridge>
linking together di˙erent por ts. In the same way, an Ether net ˝rewall uses a br
idge that links inter faces to be ˝ltered.
A por t agg regate contains the or igin por ts and a MAC address.
ò
Note
Ever y deletion or addition of a network por t is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the network por ts
infor mation can be automatically impor ted
and updated.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
3.2. Modules
41

GLPI User Document ation, Ver sion 10.0

It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.
Type of depreciation : choice of the type of depreciation between linear and
declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
42
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

If a war ranty star t date and a war ranty per iod are set, the infor mation #
Expires on # will appear with a date
in red if it is earlier than the cur rent date
All the dates de˝ned can be managed automatically according to changes in the
status of the equipment. Some dates
can also be copied from another date. All this con˝guration is done by [entity]
(administration_entity_delegation.dita).
Tips
GLPI allows you to con˝gure a noti˝cation on the expir y of the hardware war ranty.
This is con˝gurable by entity in
noti˝cation management to de˝ne the models and recipients used and in
the administration of entities
to enable or
disable this feature, de˝ne the default values and anticipate the sending of the
noti˝cation if necessar y.
GLPI can per for m a simple net book value calculation based on straight-line or
declining balance depreciation. To do
so, a cer tain amount of infor mation (value, date, etc.) must be entered. The user
must also enter the date of the ˝nancial
year the general con˝guration.
The display of ˝nancial infor mation for each type of equipment depends on the
pro˝le of the user logged in.
Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
43

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Vir tualization
This tab displays the vir tualization systems (vir tual machines, containers,
jails. . ..) associated to a host.
The available infor mation var y from one system to anoth er : for a vir tual
machine for instance, it includes name,
vir tualization system, vir tualization model, state, allocated memor y, number of
logical processors. . . as well as the
name of the physical machine (the host).
GLPI establishes the link between a host and a vir tual machine based on the unique
identi˝er (UUID). In some case, it
is possible that the UUID is di˙erent inside the physical machine and the vir tual
machine ; it is therefore impossible to
make the link automatically.
The only way to link manually a vir tual machine to a physical machine is to attr
ibute the
same
UUID to the vir tual
machine declared on the host and to the vir tual machine inside GLPI.
ò
Note
If using native inventor y or third-par ty inventor y tool, the vir tualization
infor mation can be automatically impor ted
and updated.
Antivirus
This tab, named
Antivir us
and visible in a
Computer
entr y, allows to manage the antivir us r unning on a computer.
44
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

An antivir us is character ized by :

name

active/non active

vendor

update status

antivir us version

signature database version

expiration date
ò
Note
Ever y deletion or addition of an antivir us is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the antivir us infor
mation can be automatically impor ted and
updated.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
3.2. Modules
45

GLPI User Document ation, Ver sion 10.0

ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

ò
Note
A second table lists the problems attached to the related elements
ò
Note
Any deletion or addition of a problem is recorded in the histor y.
Chang es
The
Changes
tab is used to create a change associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes the following ˝elds for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements
46
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Categor y

Name

Number of scheduled tasks

ò
Note
A second table lists the changes attached to the related elements
ò
Note
Any deletion or addition of a change is recorded in the histor y.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

v
À faire
Fix this reference (include or link ? ? ?)
[Onglet # Réservations #](Les_di˙érents_onglets/Onglet_Réservations.rst)
Gestion des réser vations pour un objet d'inventaire
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

48
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Inst all a software with a license on a computer

From the tab
Sof twares
, add a license by choosing the name
of the software followed by the name of the license. From the
Mass actions
of summar y table, choose
Inst all
.
Avertissement
A software can only be installed if its license has a version in use or a purchase
version.
Displays
In a display for m, the following infor mation is available :

General character istics of the display :

Vendor

Model
Type

Ser ial number

. . .

Display management :

Technical person in charge

Status

Location

. . .

Display users :

Users known to GLPI or not

Groups of users

Speci˝cations :

Size

Resolution

Por t types (VGA, DVI, HDMI, DisplayPor t)

Integ rated sound

Connectivity

. . .
Management type :
It is possible to manage displays either unitar y or globally.
Unitar y management cor responds to one display per computer while global
management make the pr inter a vir tual
global element that will be connected to several computers.
Global management allows to limit the number of elements to manage when these
elements are not a strategic data in
the assets management.
It is possible to use
templates with displays
.
3.2. Modules
49

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Connections
This tab allows to manage the direct connections between a computer and its
connected elements.
Direct connections represent the relation between di˙erent hardwares linked either
physically or vir tually.
From a com puter
The connection can be made toward one or several elements of type display, pr
inter, per ipheral or phone. For each type
of connected object, its name, ser ial number and inventor y number are displayed.
From an element other than a com puter
To add a connection, select the computer in the drop-down list presented at top of
the table.
If this case, the connection can only be made to a single computer. The table will
list the name of this computer as well
as its ser ial and inventor y numbers.
ò
Note
The deletion of a connection can be made from the entr y of each connected hardware
(tab
Connections
) via mass
actions.
ò
Note
Ever y deletion or addition of a connection is recorded in the histor y of the
computer.
ò
Note
50
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

If using native inventor y or third-par ty inventor y tool, the connections infor
mations can be automatically impor ted
and updated.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
3.2. Modules
51

GLPI User Document ation, Ver sion 10.0

Lifecycle

Order date

Date of purchase
Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

so, a cer tain amount of infor mation (value, date, etc.) must be entered. The user
must also enter the date of the ˝nancial
year the general con˝guration.
The display of ˝nancial infor mation for each type of equipment depends on the
pro˝le of the user logged in.
Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
3.2. Modules
53

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

54
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the problems attached to the related elements
ò
Note
Any deletion or addition of a problem is recorded in the histor y.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
v
À faire
Fix this reference (include or link ? ? ?)
[Tab # Reservations #](Les_di˙érents_onglets/Onglet_Réservations.rst)
Management of reser vations for an inventor y object
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

3.2. Modules
55

GLPI User Document ation, Ver sion 10.0

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

connect a display to a monitor

Sof twar e
GLPI allows management of software and their versions as well as licenses,
associated or not to software versions.
A software is by default associated with an entity.
Financial management is done at the level of licenses ; the ˝nancial management at
software level is only a model for
the licenses associated with this software.
56
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Software can be impor ted automatically using a third-par ty inventor y tool ; in
this case a dictionar y can be used to
˝lter or clean the impor t data (see [Con˝gure data dictionar ies]
(07_Module_Administration/06_Dictionnaires.rst # The
dictionar ies are managed from menu entr y Administration > Dictionar ies #)).
Some ˝elds are speci˝c in the software for m :

Update
is an infor mation, with no processing associated and which tells whether the
software is an update of
another software

Category
allows to g roup software in the list of software of an asset
Can be associated with a ticket
de˝nes whether the software can be seen in the drop-down list # Hardware #
of a ticket
It is recommended to ˝rst create the software without a version number in the name,
then to create the versions and last
to create the licenses.
ò
Note
In multi-entity mode, the list of software can rapidly become long because of
double entr ies (one software per
entity). A better approach can consist in g rouping identical software in the same
entity (see tab
Grouping
below),
then to make recursive the elements that can be made recursive.
It is possible to use
templates with sof tware
.
The di˙er ent t abs
Ver sions
A version of a software is the element that can be installed on a asset ; see also
*Installations* tab
.
The main view lists the number of installations of the version.
Speci˝c ˝elds :

Name
: the version number

St atus
: in ITIL recommendations, it allows to follow the DSL (librar y stor ing author
ized versions)

Operating system
: the operating system on which this software version r uns

Inst allations
: the number of installations of the version

Comment
: some comments
Licenses
Inst allations
The installation of a software on a computer is visualized through a
version
and can be consu lted on a software for m
(list of computers having at least one version installed), on a version for m
(computers having this version installed) and
˝nally on a computer for m (list of versions of installed software, sor ted by
categor y).
ò
Note

Column
license
is ˝lled only when the license is a˙ected to the concer ned computer

The initial display of di˙erent categor ies depend upon user preferences (see
[manage preferences](01-
premiers-pas/03_Utiliser_GLPI/04_Gérer_ses_préférences.rst #).
Two options are available on the list of installations of software on a computer.
Above the list,
Inst all
allows to install
manually a version of a software on the computer, by selecting ˝rst the software
and its version ; if a license is associated
with this software, the use version of the license is automatically selected.
3.2. Modules
57

GLPI User Document ation, Ver sion 10.0

To
Uninst all
a version of a software, mass actions must be used : ˝rst select the versions to be
uninstalled, then select
Suppress de˝nitively
. If a license is a˙ected to the computer, it remains a˙ected but its use version
is erased.
Following the list of installed versions, the list of a˙ected but non installed
licenses is displayed. It is possible to add a
new license to the computer. Mass actions allow, via the action
Inst all
, to install a use version of selected licenses.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
58
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation
Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.
Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

3.2. Modules
61

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
v
À faire
Fix this reference (include or link ? ? ?)
[Onglet # Réservations #](Les_di˙érents_onglets/Onglet_Réservations.rst)
Gestion des réser vations pour un objet d'inventaire
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

62
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The descr iption of the change represents either the di˙erence between the old and
the new value (For example with
location ˝eld : Change HQ to Remote O˚ce A), or the explanation of the action which
was car r ied out (For example :
Uninstallation of a software : # Gimp 2.0 #).
ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
Grouping
This section descr ibes how to g roup software having same names in sub-entities,
allowing to g roup software of child
entities into mother entity.
ò
Note
This is only available for multi-entities platfor ms.
How to realize a g rouping :
1.
If the software does not exist in mother entity, create in this mother entity a
software whose name is str ictly
identical to the name of software in child entities
2.
Open the for m of the software of the mother entity
3.
Activate recursivity (sub-entities to Yes at top r ight) ; this will make a new
tab
Grouping
appear after tab
Histor y
4.
Open this tab ; a list displays software having same names in child entities
5.
Select appropr iate lines and validate g rouping
.
Avertissement
This operation cannot be undone
This g rouping have the following e˙ects :

Licenses are attached to the software in mother entity, but stay in or igin sub-
entities

Versions are merged, no more doubles in mother entity

Old software are moved to the trash

ò
Note
When using a third-par ty inventor y tool, some extra steps are mandator y :

Empty trash after g rouping, other wise synchronization will restore the old
software in case of new version

Associate the same vendor to the new software ; as the synchronization checks
vendor name, a new software
would then be created
Debugging information
If you have
Debug
mode enabled in your preferences, a
Debug
tab will appear before the
All
tab. This tab o˙ers
infor mation to help you resolve an issue.
For example, for a computer, you have one or more tables depending on the a˙ected
object (˝nancial infor mation,
reser vations. . .) listing the noti˝cations that will be tr iggered on this
computer with :

Tr igger ing event

3.2. Modules
63

GLPI User Document ation, Ver sion 10.0

Recipient(s)

Noti˝cation model used

Recipient(s) email address

Add a version to a sof tware

[Manage licenses](03_Module_Parc/04_Logiciels/Onglet_Licences.rst)
From menu
*Assets > Softwares*
click on license name in tab
Licenses
.
N etwork eq uipments
Network equipment represent the hardware that manages, transmits and route network
between several other equipments
(computers, pr inters. . .).
A network equipment can be a switch, an Ether net hub, a router, a ˝rewall or a
WiFi access point.
It is possible to use
templates with network equipments
.
The di˙er ent t abs
Com ponents
This tab, named
Components
and visible in a
Computer
entr y, allows to manage the hardware components of a computer.
64
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
Adding or managing components is located in menu
Setup > Components
.
ò
Note
If several components of the same type are used, they will be g rouped in the view.
It is possible to add a component by ˝rst selecting its family in the drop-down
list at the top of the table and then its
name and the number of components to add.
Star ting from a computer view, it is possible to modify a component by clicking on
the link under its name.
3.2. Modules
65

GLPI User Document ation, Ver sion 10.0

To act on several components (for example modify an element of the component,
activate accounting infor mation or
modify them, delete a component. . .), ˝rst select the components and then use the
Actions
button present at the top or
the bottom of the list.
If several types of di˙ere nt components, not having the same character istics, are
selected for modi˝cation, in the actions
it will be asked on which component modi˝cation must be applied.
Selection button in left column allows to select all the components at once.
Selection at r ight of type column (g rayed line ) allows to select all components
of the same type (processor, memor y,
66
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

network inter face. . .).
ò
Note
It is possible to modify the character istics of a component only for one computer
From tab
Elements
of the component, click on the link
Update
.
Several tabs are then displayed :

Tab # Element - Link name of component # : list the character istics of this
component

Tab # Management # : manage administrative and accounting infor mation

Tab # Documents # : attached documents

Tab # Histor y # : histor y of modi˝cations

Tab # Contract # : contracts management

Tab # Debug # : only if you are connected in Debug mode

GLPI User Document ation, Ver sion 10.0

A network por t represents the output of a network inter face on a given hardware.
A por t is character ized by a number
and a name.
It is possible on a network por t to add one or more VLAN, these VLANs being de˝ned
by a name, an optional comment
and a VLAN number.
One or more
network name
can be associated to each network por t. This can be done in tab
Network name
.
ò
Note
When a network por t has only one network name, this name is displayed in the
network por t for m itself and it is
possible to modify the name directly. It is also possible to modify the network
name via its own for m, accessible
by clicking on the link under the name.
When a network por t has several network names, the only way to modify the network
names is via the network
name for m.
Network por ts can be of di˙erent types :

physical por t : ether net, WiFi. . .

Vir tual network por t

: local loop-back, alias, agg regates. . .
68
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

point to point : switched network. . .

GLPI User Document ation, Ver sion 10.0

Tab # Network names #

Summar y of IP address and IP networks for each network name
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
70
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.
Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
3.2. Modules
71

GLPI User Document ation, Ver sion 10.0

Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity
3.2. Modules
73

GLPI User Document ation, Ver sion 10.0

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

v
À faire
Fix this reference (include or link ? ? ?)
[Tab # Reservations #](Les_di˙érents_onglets/Onglet_Réservations.rst)
Management of reser vations for an inventor y object
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)
Noti˝cation model used

Recipient(s) email address

3.2. Modules
75

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
The di˙er ent actions
Network equipments do not have speci˝c actions ; repor t to
common actions
.
Peripher als
In a per ipheral for m, the following infor mation is available :

General character istics of the per ipheral :

Vendor

Model

Type

Ser ial number

. . .

Per ipheral management :

Technical person in charge

Status

Location

. . .

Per ipheral users :

Users known to GLPI or not

Groups of users

. . .
Management type :
It is possible to manage per ipherals either unitar y or globally.
Unitar y management cor responds to one per ipheral per computer while global
management make the per ipheral a
vir tual global element that will be connected to several computers.
Global management allows to limit the number of elements to manage when these
elements are not a strategic data in
the assets management.
It is possible to use
templates with peripherals
.
76
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Com ponents
This tab, named
Components
and visible in a
Computer
entr y, allows to manage the hardware components of a computer.
ò
Note
Adding or managing components is located in menu
Setup > Components
.
ò
Note
If several components of the same type are used, they will be g rouped in the view.
It is possible to add a component by ˝rst selecting its family in the drop-down
list at the top of the table and then its
name and the number of components to add.
3.2. Modules
77

GLPI User Document ation, Ver sion 10.0

Tab # Element - Link name of component # : list the character istics of this
component
Tab # Management # : manage administrative and accounting infor mation

Tab # Documents # : attached documents

Tab # Histor y # : histor y of modi˝cations

Tab # Contract # : contracts management

Tab # Debug # : only if you are connected in Debug mode

Tab # All # : all the infor mation are displayed on a single page
3.2. Modules
79

GLPI User Document ation, Ver sion 10.0

ò
Note
Ever y deletion or addition of a component is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the components infor
mation can be automatically impor ted
and updated.
Connections
This tab allows to manage the direct connections between a computer and its
connected elements.
Direct connections represent the relation between di˙erent hardwares linked either
physically or vir tually.
From a com puter
The connection can be made toward one or several elements of type display, pr
inter, per ipheral or phone. For each type
of connected object, its name, ser ial number and inventor y number are displayed.
From an element other than a com puter
To add a connection, select the computer in the drop-down list presented at top of
the table.
If this case, the connection can only be made to a single computer. The table will
list the name of this computer as well
as its ser ial and inventor y numbers.
ò
Note
The deletion of a connection can be made from the entr y of each connected hardware
(tab
Connections
) via mass
actions.
80
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
Ever y deletion or addition of a connection is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the connections infor
mations can be automatically impor ted
and updated.
N etwork por ts
This tab, named
Network por ts
and visible in a
Computer
entr y, allows to manage the network por ts attached to a
computer.
A network por t represents the output of a network inter face on a given hardware.
A por t is character ized by a number
and a name.
It is possible on a network por t to add one or more VLAN, these VLANs being de˝ned
by a name, an optional comment
and a VLAN number.
One or more
network name
can be associated to each network por t. This can be done in tab
Network name
.
3.2. Modules
81

GLPI User Document ation, Ver sion 10.0

ò
Note
When a network por t has only one network name, this name is displayed in the
network por t for m itself and it is
possible to modify the name directly. It is also possible to modify the network
name via its own for m, accessible
by clicking on the link under the name.
When a network por t has several network names, the only way to modify the network
names is via the network
name for m.
Network por ts can be of di˙erent types :

physical por t : ether net, WiFi. . .

Vir tual network por t

: local loop-back, alias, agg regates. . .

point to point : switched network. . .

GLPI User Document ation, Ver sion 10.0

A WiFi network can be associated to a given por t. Apar t from its name, a WiFi
network has an ESSID and is charac-
ter ized by its type :
Infrastr ucture :
WiFi network with on or several access points and connected clients
Ad-hoc :
WiFi network between
similar systems without access points
Manag ement of local loop-bac k por ts
The local loop-back is a vir tual por t used by most equipments for inter nal
communication. It is this por t that is used
when connecting to
localhost
or
127.0.0.1
.
Local loop-back has no speci˝c attr ibute.
Manag ement of network por t aliases
A network por t alias is a vir tual por t that can re˝ne a physical por t.
On Linux, to each VLAN, when transmitted
# tagged #
, is associated a por t alias, for example
eth2.50
to represent
VLAN 50 on por t
eth2
.
A por t alias contains its base por t and a MAC address.
Note that when the or igin por t is changed, the MAC address of the new por t is
a˙ected to the por t alias.
Manag ement of network por t aggr eg ates
A network por t agg regate is a vir tual por t that allows to g roup several
physical por ts.
On Linux, agg regates are represented by br idges
bridges <http ://www.linuxfoundation.org/collaborate/workgroups/networking/bridge>
linking together di˙erent por ts. In the same way, an Ether net ˝rewall uses a br
idge that links inter faces to be ˝ltered.
A por t agg regate contains the or igin por ts and a MAC address.
ò
Note
Ever y deletion or addition of a network por t is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the network por ts
infor mation can be automatically impor ted
and updated.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
3.2. Modules
83

GLPI User Document ation, Ver sion 10.0

By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
84
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.
Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
86
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

ò
Note
A second table lists the problems attached to the related elements
3.2. Modules
87

GLPI User Document ation, Ver sion 10.0

ò
Note
Any deletion or addition of a problem is recorded in the histor y.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
Debugging information
If you have
Debug
mode enabled in your preferences, a
Debug
tab will appear before the
All
tab. This tab o˙ers
infor mation to help you resolve an issue.
For example, for a computer, you have one or more tables depending on the a˙ected
object (˝nancial infor mation,
reser vations. . .) listing the noti˝cations that will be tr iggered on this
computer with :

Tr igger ing event

Recipient(s)
Noti˝cation model used

Recipient(s) email address

General character istics of the pr inter :

Vendor

Model

Type

Ser ial number

. . .

Pr inter management :

Technical person in charge

Status

Location

. . .

Pr inter users :
3.2. Modules
89

GLPI User Document ation, Ver sion 10.0

Users known to GLPI or not

Groups of users

Speci˝cations :

Page counter

Por t types

. . .
Manag ement Type
It is possible to manage pr inters either unitar y or globally.
Unitar y management cor responds to one pr inter per computer while global
management make the pr inter a vir tual
global element that will be connected to several computers.
Global management allows to limit the number of elements to manage wh en these
elements are not a strategic data in
the assets management.
It is possible to use
templates with printers
.
The di˙er ent t abs
Com ponents
This tab, named
Components
and visible in a
Computer
entr y, allows to manage the hardware components of a computer.
ò
Note
Adding or managing components is located in menu
Setup > Components
.
90
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
If several components of the same type are used, they will be g rouped in the view.
It is possible to add a component by ˝rst selecting its family in the drop-down
list at the top of the table and then its
name and the number of components to add.
Star ting from a computer view, it is possible to modify a component by clicking on
the link under its name.
To act on several components (for example modify an element of the component,
activate accounting infor mation or
modify them, delete a component. . .), ˝rst select the components and then use the
Actions
button present at the top or
the bottom of the list.
If several types of di˙ere nt components, not having the same character istics, are
selected for modi˝cation, in the actions
it will be asked on which component modi˝cation must be applied.
Selection button in left column allows to select all the components at once.
3.2. Modules
91

GLPI User Document ation, Ver sion 10.0

Tab # Management # : manage administrative and accounting infor mation

Tab # Documents # : attached documents

Tab # Histor y # : histor y of modi˝cations

Tab # Contract # : contracts management

Tab # Debug # : only if you are connected in Debug mode

Tab # All # : all the infor mation are displayed on a single page
92
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

car tr idges in use, with add date and use date

used car tr idges, with car tr idge model, add date, use date, end of life date,
pr inting counter and number of pr inted
pages since last car tr idge change
ò
Note
For car tr idge adding or removing, repor t to
car tridges management
.
Connections
This tab allows to manage the direct connections between a computer and its
connected elements.
Direct connections represent the relation between di˙erent hardwares linked either
physically or vir tually.
From a com puter
The connection can be made toward one or several elements of type display, pr
inter, per ipheral or phone. For each type
of connected object, its name, ser ial number and inventor y number are displayed.
From an element other than a com puter
To add a connection, select the computer in the drop-down list presented at top of
the table.
3.2. Modules
93

GLPI User Document ation, Ver sion 10.0

If this case, the connection can only be made to a single computer. The table will
list the name of this computer as well
as its ser ial and inventor y numbers.
ò
Note
The deletion of a connection can be made from the entr y of each connected hardware
(tab
Connections
) via mass
actions.
ò
Note
Ever y deletion or addition of a connection is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the connections infor
mations can be automatically impor ted
and updated.
N etwork por ts
This tab, named
Network por ts
and visible in a
Computer
entr y, allows to manage the network por ts attached to a
computer.
A network por t represents the output of a network inter face on a given hardware.
A por t is character ized by a number
and a name.
It is possible on a network por t to add one or more VLAN, these VLANs being de˝ned
by a name, an optional comment
and a VLAN number.
94
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

One or more
network name
can be associated to each network por t. This can be done in tab
Network name
.
ò
Note
When a network por t has only one network name, this name is displayed in the
network por t for m itself and it is
possible to modify the name directly. It is also possible to modify the network
name via its own for m, accessible
by clicking on the link under the name.
When a network por t has several network names, the only way to modify the network
names is via the network
name for m.
Network por ts can be of di˙erent types :

physical por t : ether net, WiFi. . .

Vir tual network por t

: local loop-back, alias, agg regates. . .

point to point : switched network. . .

GLPI User Document ation, Ver sion 10.0

Ether net connections are realized by linking two Ether net por ts, which requires
that there is a free por t on each equip-
ment to be connected. In general, a connection links a por t attached to a
computer, a per ipheral or a pr inter and a por t
attached to a network equipment (hub, switch).
Manag ement of WiFi network por ts
The WiFi protocol is widely used on wireless networks.
A WiFi por t is character ized by the mode of the network card (ad-hoc, access
point, repeater. . .), the WiFi protocol
version (ab, g. . .) and its MAX address.
It is possible to associate a network card to the por t, similarly to Ether net por
ts.
A WiFi network can be associated to a given por t. Apar t from its name, a WiFi
network has an ESSID and is charac-
ter ized by its type :
Infrastr ucture :
WiFi network with on or several access points and connected clients
Ad-hoc :
WiFi network between
similar systems without access points
Manag ement of local loop-bac k por ts
The local loop-back is a vir tual por t used by most equipments for inter nal
communication. It is this por t that is used
when connecting to
localhost
or
127.0.0.1
.
Local loop-back has no speci˝c attr ibute.
Manag ement of network por t aliases
A network por t alias is a vir tual por t that can re˝ne a physical por t.
On Linux, to each VLAN, when transmitted
# tagged #
, is associated a por t alias, for example
eth2.50
to represent
VLAN 50 on por t
eth2
.
A por t alias contains its base por t and a MAC address.
Note that when the or igin por t is changed, the MAC address of the new por t is
a˙ected to the por t alias.
Manag ement of network por t aggr eg ates
A network por t agg regate is a vir tual por t that allows to g roup several
physical por ts.
On Linux, agg regates are represented by br idges
bridges <http ://www.linuxfoundation.org/collaborate/workgroups/networking/bridge>
linking together di˙erent por ts. In the same way, an Ether net ˝rewall uses a br
idge that links inter faces to be ˝ltered.
A por t agg regate contains the or igin por ts and a MAC address.
ò
Note
Ever y deletion or addition of a network por t is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the network por ts
infor mation can be automatically impor ted
and updated.
96
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
3.2. Modules
97

GLPI User Document ation, Ver sion 10.0

Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.
Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

ò
Note
A second table lists the problems attached to the related elements
100
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
v
À faire
Fix this reference (include or link ? ? ?)
[Onglet # Réservations #](Les_di˙érents_onglets/Onglet_Réservations.rst)
Gestion des réser vations pour un objet d'inventaire
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
The di˙er ent actions
Pr inters do not have speci˝c actions ; repor t to
common actions
.
Car tridg es
This functionality of
Asset
module allows to create car tr idges models and cor responding car tr idges.
In a car tr idge for m, the following infor mation is available :

General character istics of the car tr idge :

Vendor

Type

Reference

. . .

Pr inter management :

Technical person in charge

Storage site

. . .
The aler t threshold is the minimal value at which an aler t is tr iggered. A
restock threshold which represents the amount
you wish to have in stock after order ing.
102
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

For example, you want to have 10 of a c er tain car tr idge in stock but it isn't
wor th order ing them until you have 2 or less
in stock (due to bulk discounts, process overhead, etc). You can set your alar m
threshold to 2 and your restock value to
10. When you receive the alar m noti˝cation, it will let you know what the restock
value is and plainly say how many
need to be ordered to meet that value (con˝gurable in noti˝cation templates).
ò
Note
For aler ts to be e˙ective, noti˝cations must be activated ; see noti˝cation
management.
For a car tr idge to be installable on a pr inter, it must be declared as
compatible with this pr inter.
Management of shared stock is possible by de˝ning the element as recursive on an
entity. The elements will then be
available for all sub-entities.
The di˙er ent t abs

Tab # Cartridges #
This tab allows adding as many car tr idges as needed by the model. It is also
possible to
add several car tr idges at once.
A ˝rst table lists the new or unused car tr idges, the second table lists used car
tr idges.

Tab # Printer models #

This tab allows to declare the pr inter models that are compatible with the car tr
idge.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
3.2. Modules
103

GLPI User Document ation, Ver sion 10.0

Order date

Date of purchase
Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
104
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

3.2. Modules
107

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Consumables
In a consumable for m, the following infor mation is available :

General character istics of the consumable :

Vendor

Type

Reference

. . .

Consumable management :

Technical person in charge

Storage location

. . .
The aler t threshold cor responds to the minimal value at which an aler t is tr
iggere d. A restock threshold which represents
the amount you wish to have in stock after order ing.
For example, you want to have 100 HDMI cables in stock but it isn't wor th order
ing them until you have 10 or less in
stock (due to bulk discounts, process overhead, etc). You can set your alar m
threshold to 10 and your restock value to
100. When you receive the alar m noti˝cation, it will let you know what the restock
value is and plainly say how many
need to be ordered to meet that value (con˝gurable in noti˝cation templates).
ò
Note
For aler ts to be e˙ective, noti˝cations must be activated ; see noti˝cation
management.
Changing the state of a consumable from
new
to
used
requires to set involved user or g roup.
Management of shared stocks is possible by de˝ning the element as recursive on an
entity. The elements will then be
available for all sub-entities.
108
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Consumables
This tab allows to add as many consumables as needed. It is also possible to add
several consumable in one shot.
A ˝rst table lists unuse d consumables, a second table lists used consumables
together with the name of the g roup or
the person to which it has been allocated.
The mass actions of this tab allows to allocate consumables (action
Give*
).
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
3.2. Modules
109

GLPI User Document ation, Ver sion 10.0

Order date

Date of purchase

Deliver y date

Date of implementation
Date of last physical inventor y

Date of refor m
110
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.
Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

Debugging information
If you have
Debug
mode enabled in your preferences, a
Debug
tab will appear before the
All
tab. This tab o˙ers
infor mation to help you resolve an issue.
For example, for a computer, you have one or more tables depending on the a˙ected
object (˝nancial infor mation,
reser vations. . .) listing the noti˝cations that will be tr iggered on this
computer with :

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

Add new consumables to a model

;

List allocated consumables : The

Summar y
menu button allows you to see a summar y of allocated consumables
3.2. Modules
113

GLPI User Document ation, Ver sion 10.0

Phones
In a phone for m, the following infor mation is available :

General character istics of the phone :

Vendor

Model

Type

Ser ial number

. . .

Phone management :

Technical person in charge

Status

Location

. . .

Phone users :

Users known to GLPI or not

Groups of users

. . .

Speci˝cations :

Power supply

Fir mware

. . .
Management type :
It is possible to manage phones either unitar y or globally.
Unitar y management cor responds to one phone per computer while global management
make the phone a vir tual global
element that will be connected to several computers.
Global management allows to limit the number of elements to manage when these
elements are not a strategic data in
the assets management.
It is possible to use
templates with phones
.
The di˙er ent t abs
Com ponents
This tab, named
Components
and visible in a
Computer
entr y, allows to manage the hardware components of a computer.
114
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Tab # Element - Link name of component # : list the character istics of this
component
Tab # Management # : manage administrative and accounting infor mation

Tab # Documents # : attached documents

Tab # Histor y # : histor y of modi˝cations

Tab # Contract # : contracts management

Tab # Debug # : only if you are connected in Debug mode

Tab # All # : all the infor mation are displayed on a single page
ò
Note
Ever y deletion or addition of a component is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the components infor
mation can be automatically impor ted
and updated.
Connections
This tab allows to manage the direct connections between a computer and its
connected elements.
Direct connections represent the relation between di˙erent hardwares linked either
physically or vir tually.
From a com puter
The connection can be made toward one or several elements of type display, pr
inter, per ipheral or phone. For each type
of connected object, its name, ser ial number and inventor y number are displayed.
3.2. Modules
117

GLPI User Document ation, Ver sion 10.0

From an element other than a com puter
To add a connection, select the computer in the drop-down list presented at top of
the table.
If this case, the connection can only be made to a single computer. The table will
list the name of this computer as well
as its ser ial and inventor y numbers.
ò
Note
The deletion of a connection can be made from the entr y of each connected hardware
(tab
Connections
) via mass
actions.
ò
Note
Ever y deletion or addition of a connection is recorded in the histor y of the
computer.
ò
Note
If using native inventor y or third-par ty inventor y tool, the connections infor
mations can be automatically impor ted
and updated.
N etwork por ts
This tab, named
Network por ts
and visible in a
Computer
entr y, allows to manage the network por ts attached to a
computer.
118
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

physical por t : ether net, WiFi. . .

Vir tual network por t

: local loop-back, alias, agg regates. . .
3.2. Modules
119

GLPI User Document ation, Ver sion 10.0

point to point : switched network. . .

GLPI User Document ation, Ver sion 10.0

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
122
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity
124
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

126
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
The di˙er ent actions
Phones do not have speci˝c actions ; repor t to
common actions
.
Global search
Menu
Asset > Global
allows to per for m a global search on default view columns for allowed elements.
This search is
limited to following assets :

Computer,

Contact,

Contract,

Document,

Monitor,

NetworkEquipment,

Per ipheral,

Phone,

Pr inter,

Software,

SoftwareLicense,

Ticket,

Problem,

Change#,

User,

Group,

Project,

Supplier#,

Budget,

Cer ti˝cate,
Line,

Datacenter,

DCRoom,

Enclosure,

PDU,

Rack,
3.2. Modules
127

GLPI User Document ation, Ver sion 10.0

Cluster,

Domain
This search allows for instance to per for m a quer y by status, IP or MAC address.
v
À faire
Referenced in or iginal doc but not present :

[Gestion du protocole Internet (IP)](../glpi/inventory_ip.html)

Le protocole IP est matér ialisé sous plusieurs for mes : adresses IP, réseaux IP,
mais aussi des FQDN
3.2.3
Manag ement
The GLPI Management module is used to manage the following items :
Licenses
Licenses management in GLPI allows to manage software licenses :

Inventor ying licenses, with links to software inventor ied in GLPI ;

Following license installations on all assets ;

Linking licenses to ˝nancial management ;

Anticipating and following licenses renewal.

ò
Note
A license cannot exists in GLPI without a software associated to the license when
creating it.
License management is not automated, a human follow-up is needed for infor mation
update.
128
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to use
templates to generate this object
.
Description of speci˝c ˝elds

As child of
: allows to specify if the license is dependent upon another license ;

Version in use
: the version of the software associated with the license ;

Purchase version
: the purchase version, which can di˙er from
Version in use
; if di˙erent, this ˝eld indicates
it ;

Number
: the maximum number of uses of the license by assets ;

Allow Over-Quot a
: allow or not the over ˛ow of maximum number con˝gured in ˝eld
Number
;

Expiration date
: expiration date of the license, useful to con˝gure aler ts and anticipate
renewal.
3.2. Modules
129

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Licenses
This tab lists all licenses declared as child of this license.
ò
Note
Some licenses can be obtained by pack or by g roup, linking them by child/parent
relationship allows to declare it.
Summar y
This tab lists all types and entities of items linked to this license.
ò
Note
The number of installations must be carefully checked against the ˝eld
Number
of the license.
Creating a link between an asset and the license id done in tab
Sof twares
of the asset.
Items
This tab details each item linked to the license.
130
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Tips
GLPI allows you to con˝gure a noti˝cation on the expir y of the hardware war ranty.
This is con˝gurable by entity in
noti˝cation management to de˝ne the models and recipients used and in
the administration of entities
to enable or
disable this feature, de˝ne the default values and anticipate the sending of the
noti˝cation if necessar y.
GLPI can per for m a simple net book value calculation based on straight-line or
declining balance depreciation. To do
so, a cer tain amount of infor mation (value, date, etc.) must be entered. The user
must also enter the date of the ˝nancial
year the general con˝guration.
The display of ˝nancial infor mation for each type of equipment depends on the
pro˝le of the user logged in.
Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
133

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Knowledg e base
The
Knowledge base
tab is used to show or add linked knowledge base ar ticles.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :
Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)
134
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Number of scheduled tasks

3.2. Modules
135

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the changes attached to the related elements
ò
Note
Any deletion or addition of a change is recorded in the histor y.
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Cer ti˝cates
This tab allows to attach a cer ti˝cate present in GLPI to the license.
136
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

The descr iption of the change represents either the di˙erence between the old and
the new value (For example with
location ˝eld : Change HQ to Remote O˚ce A), or the explanation of the action which
was car r ied out (For example :
Uninstallation of a software : # Gimp 2.0 #).
ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Budg ets
A budget in GLPI is de˝ned by an amount and a time per iod. Other GLPI items can be
attached to this budget and will
then, by providing their value, modify the budget available amount.
Creating a budget in GLPI enables the administrative and ˝nancial management
functionality for all other GLPI items.
It is possible to follow the evolution of a budget by tracing the value of each
attached item.
ò
Note
Attaching a GLPI item to a budget is done via tab
Management
of the item !
ò
Note
When displaying a budget from a sub-entity, the budget remaining total amount is
not visible.
3.2. Modules
137

GLPI User Document ation, Ver sion 10.0

The budget remaining total amount can be negative if the sum of the values of
attached items is g reater than the
budget amount.
ò
Note
It is possible to use
templates to generate this object
.
The di˙er ent t abs
Main t ab
This tab provides a summar y table giving the expended amount of the budget, sor
ted by item type, as well as total
remaining amount.
Items
This tab displays GLPI items attached to this budget as well as their value.
ò
Note
Attaching a GLPI item to a budget is done via tab
Management
of the item !
138
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Knowledg e base
The
Knowledge base
tab is used to show or add linked knowledge base ar ticles.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;
3.2. Modules
139

GLPI User Document ation, Ver sion 10.0

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Create an inventor y of all organization cer ti˝cates ;

Follow installation of cer ti˝cates on assets ;

Include cer ti˝cates in GLPI ˝nancial management ;

Anticipate and follow cer ti˝cates renewal.

140
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to use
templates to generate this object
.
Description of speci˝c ˝elds

Manufacturer (Root CA)

: This drop-down list allows you to select the cer ti˝cate manufacturer ;

Self-signed
: Tells whether cer ti˝cate is self-signed ;

DNS name
: The pre˝x of the domain name associated with the cer ti˝cate (for example, if
domain name is
ser ver.mycompany.com
, DNS name is
ser ver
) ;

DNS su˚x
: The su˚x of the domain name associated with the cer ti˝cate (for example, if
domain name is
ser ver.mycompany.com
, DNS su˚x is
mycompany.com
) ;

Expiration date
: Expiration date of the cer ti˝cate, useful to con˝gure aler ts and anticipate
renewal ;

Command used
: Can store the system command that generated the cer ti˝cate ;

Certi˝cate Request (CSR)

: Can store the system command that generated the CSR ˝le ;

Certi˝cate
: Can store the data contained in the CRT ˝le (PEM).
The di˙er ent t abs
Associated elements
The
Items
tab is used to show or add linked assets.
3.2. Modules
141

GLPI User Document ation, Ver sion 10.0

It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)
3.2. Modules
145

GLPI User Document ation, Ver sion 10.0

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Number of scheduled tasks

146
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

reference all suppliers of organization assets

ease contact in case of incident

include suppliers in GLPI assistance

148
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

-The di˙er ent t abs
Associated Cont acts
The
Contacts
tab is used to show or add linked contacts.
ò
Note
There is a clear distinction between a supplier (which can be attached to assets)
and a contact (which are the persons
allowing to contact the supplier). Therefore, a supplier must be associated with
contacts.
Example : M. Doe is sale assistant in company Foo. Create a supplier named Foo.
Create a contact for M. Doe.
Assign to this contact the type # Sale # Attach the contact to supplier Foo
3.2. Modules
149

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity
3.2. Modules
151

GLPI User Document ation, Ver sion 10.0

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Number of scheduled tasks

152
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

GLPI User Document ation, Ver sion 10.0

Knowledg e base
The
Knowledge base
tab is used to show or add linked knowledge base ar ticles.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

ò
Note
The list of possible titles for a contact is the same as the list of possible
titles for users.
The di˙er ent t abs
Supplier s
The
Suppliers
tab is used to show or add linked suppliers.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
155

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).
156
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Field that was changed.

Descr iption of the change that was made.

make an inventor y of all contracts related to the organization assets

integ rate contracts in GLPI ˝nancial management

anticipate and follow contract renewal.

ò
Note
It is possible to use
templates to generate this object
.
3.2. Modules
157

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to receive noti˝cations in order to be infor med of events such as
contract end. When contract must
be renewed expressly, it is useful to be noti˝ed before end of contract. For per
iodic contracts, it is also possible to
be noti˝ed at the end of each per iod. Noti˝cations are con˝gured at entity level,
in menu
Setup > Noti˝cations
to
de˝ne models and destination and in menu
Administration > Entities
to enable noti˝cation, de˝ne default values
and a possible anticipation of noti˝cation.
Description of speci˝c ˝elds

Contract type
: by default, no contract type is de˝ned, contract types must be con˝gured in drop-
down con˝-
guration ;

Number
: contract number ;

St art date
: date at which contract star ts, all per iodicity based events are computed using
this date ;

Initial contract period

: if this ˝eld and star t date are given, contract end date will appear, colored in
red if
contract has expired ;

Notice
: used to tr igger aler t noti˝cations ;

Account number
: used to connect with company accounting software ;

Contract renewal period

: duration after which contract renewal is available ;

Invoice period
: duration between invoices ;

Renewal
:
Tacit
(the contract is automatically renewed if no par ty has ended it) or
Express
(needs ag reement
for renewal) ;

Max number of items

: attaching new items to this contract will be blocked when over ˛owing this number
;

Support hours
: suppor t hours as de˝ned in the contract, it is possible to distinguish week
days, Saturdays and
Sundays/holidays.
The di˙er ent t abs
Costs
This tab allows to de˝ne a cost related to the contract and linked to a GLPI budget
: the cost of the contract will be
imputed to this budget.
158
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Supplier s
This tab allows to associate one or several suppliers to the contract.
Associated elements
The
Items
tab is used to show or add linked assets.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
159

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).
160
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Documents
Documents management in GLPI allows to store digital documents or web links sor ted
under di˙erent headings.
A document is descr ibed by a
name
and an
comment
and can be associated to a
heading
.
The ˝le cor responding to the document can be added in several ways :

From local disk ;

Using a web link pointing to a document (image, HTML page, PDF. . .) ;

Using a ˝le previously transfer red with FTP to sub-folder

/˝les/_uploads/
of GLPI installation
A MIME type can also be given.
3.2. Modules
161

GLPI User Document ation, Ver sion 10.0

ò
Note

Document types author ized in GLPI according to their extension are de˝ned in
Setup
>
Dropdowns
>
Management
>
Document types

Document headings can be hierarchical

The option
Blacklisted for import
allows to exclude this document from impor t by collectors ; it is useful
for signature images, logos. . .
The di˙er ent t abs
Associated elements
The
Items
tab is used to show or add linked assets.
162
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Documents
It is possible in GLPI to attach other documents to a document, which explains why
a
Document
has a
Document
tab.
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Create an inventor y of all organization's phone lines ;

Follow infor mation on each phone line ;

Include phone lines in GLPI ˝nancial management.

3.2. Modules
163

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
164
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in
order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
3.2. Modules
165

GLPI User Document ation, Ver sion 10.0

Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.
The descr iption of the change represents either the di˙erence between the old and
the new value (For example with
location ˝eld : Change HQ to Remote O˚ce A), or the explanation of the action which
was car r ied out (For example :
Uninstallation of a software : # Gimp 2.0 #).
ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
3.2. Modules
167

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Dat a center s
Data centers management in GLPI, more precisely management of ser vers rooms and
racks, allows to :

Create an inventor y of data centers, rooms and racks of the organization ;

Include data centers in GLPI ˝nancial management ;

Use other modules for data centers management, in par ticular

Assets
module which provides a detailed g raphical
representation of racks.
Dat a center
Data center in itself is a ver y simple object, with a name and a location, and
allows only to g roup ser ver rooms.
The di˙er ent t abs
Ser ver rooms
This tab displays ser ver rooms attached to the data center and allows to add new
rooms.
168
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Ser ver room
A ser ver room is represented in GLPI by a schematic map. This map gives the space
available in the room to place
racks.
A ser ver room can be attached to a data center and to a location.
ò
Note
The map is a g r id de˝ned by a number of lines and columns. One rack consumes one
square.
The backg round image can enhance room visualization, in par ticular if this image
has been generated by a dedicated
tool.
The di˙er ent t abs
Rac ks
This tab allow to display and modify the map of a ser ver room by adding directly
on the map the racks composing the
room.
If the room contains many elements, it is possible to switch from a g r id view to
a list view.
3.2. Modules
169

GLPI User Document ation, Ver sion 10.0

Im pact analysis
This tab allow to display and build the impact schema for the data center.
170
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
3.2. Modules
171

GLPI User Document ation, Ver sion 10.0

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
172
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Associated External Links
The
Exter nal links
tab is used to show associated exter nal links.
For some items, exter nal links are managed from the menu
Setup > External links
.
These links can use object ˝elds such as IP, name, etc. See
Con˝gure protocol exter nal links
.
174
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Examples :

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y
Name

Column indicating the number of scheduled tasks

3.2. Modules
175

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Number of scheduled tasks

176
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the changes attached to the related elements
ò
Note
Any deletion or addition of a change is recorded in the histor y.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Description of speci˝c ˝elds

UUID
: Unique identi˝er of the cluster

Version
: In the case of a software cluster, the version number can be entered

Update Source
: How the cluster's data were updated
The di˙er ent t abs
Elements
This tab lists the cluster's elements and allow to add new assets to the cluster.
178
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

N etwork por ts
This tab list cluster's network inter faces and allows to create new ones.
Possible inter faces are :

Ether net por t

WiFi por t

FiberChannel por t
Por t agg regate

Por t alias

Dial up line connection

Local loop-back
Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
3.2. Modules
179

GLPI User Document ation, Ver sion 10.0

are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
180
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements
3.2. Modules
181

GLPI User Document ation, Ver sion 10.0

Categor y

Name

Number of scheduled tasks

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Domains
Domains management in GLPI allows to manage domains (i.e. Inter net domains) and
domain records :

Inventor ying domain names ;

Inventor ying domain records ;

Anticipating and following domain names renewal ;

Integ rating domains in GLPI ˝nancial management ;

Linking assets to domains ;

Modi˝é dans la version 9.5.0.

Include domains and records in GLPI assistance.

ò
Note
Access to list of domain
Records
is done via the list of
Domains
.
Domain object
A
Domain
object represents an Inter net domain, with its name, expire date. . . This object
can be attached to other
objects in GLPI assistance (tickets, problems, changes).
The di˙er ent t abs
Records
This tab allow to create or select a domain record to be associated with the
domain.
3.2. Modules
183

GLPI User Document ation, Ver sion 10.0

Associated elements
The
Items
tab is used to show or add linked assets.
Manag ement
Management of ˝nancial and administrative infor mation, this infor mation is
visible in the #Management# tab on the
computer's for m.
By default this management is disabled. It is possible to activate the ˝nancial
infor mation on any type of object in the
inventor y by using the link in the
Management
tab of the mater ial detail.
ò
Note
It is possible to activate the administrative and ˝nancial infor mation from the
massive actions on a set of elements
(computer, monitor, . . .)
184
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to activate the administrative and ˝nancial infor mation as soon as
an element is created. See # Enable
default administrative and ˝nancial infor mation # option in Setup > General >
Asset tab.
Financial infor mation consists of the following items :
Lifecycle

Order date

Date of purchase

Deliver y date

Date of implementation

Date of last physical inventor y

Date of refor m
Financial and administr ative information

Supplier : Third par ty who sold the equipment. See

Managing suppliers
. Suppliers are managed from the menu
Management > Suppliers
.

Order number : number of the order of the equipment.

Asset number.

Invoice number : equipment invoice number.

Deliver y note : deliver y note for the equipment.

Value : cost of the equipment.

War ranty extension value : cost of the war ranty extension, but preferably use
contracts.

Account net value : this is the automatic calculation of the g ross value of a
piece of equipment minus the amount
of depreciation.

Type of depreciation : choice of the type of depreciation between linear and

declining balance.

Depreciation per iod : depreciation per iod expressed in years.

Depreciation coe˚cient : coe˚cient applied to a straight-line depreciation type in

order to obtain the values of
the declining balance type. It is therefore only used if the type of depreciation
is declining balance.

TCO (value+amount of inter ventions) : the total cost of ownership which includes
all the constituent elements
of an invoiced product.

Budget : the budget on which this equipment was purchased See

Managing the budget
.

Order date : date on which the mater ial was ordered.

Purchase date : date on which the equipment was purchased.

Deliver y date : date on which the equipment was delivered.

Star tup date : date on which the equipment was put into ser vice.

Date of last physical inventor y : date of the last physical inventor y of the
equipment.

Comments.

Monthly TCO : TCO divided by the number of months between today's date and the
date of purchase of the
equipment.
Warr anty information

War ranty star t date : date on which the war ranty of the equipment star ts

War ranty infor mation : text qualifying the war ranty

Warranty period : duration of the warranty expressed in months

GLPI User Document ation, Ver sion 10.0

Tips
GLPI allows you to con˝gure a noti˝cation on the expir y of the hardware war ranty.
This is con˝gurable by entity in
noti˝cation management to de˝ne the models and recipients used and in
the administration of entities
to enable or
disable this feature, de˝ne the default values and anticipate the sending of the
noti˝cation if necessar y.
GLPI can per for m a simple net book value calculation based on straight-line or
declining balance depreciation. To do
so, a cer tain amount of infor mation (value, date, etc.) must be entered. The user
must also enter the date of the ˝nancial
year the general con˝guration.
The display of ˝nancial infor mation for each type of equipment depends on the
pro˝le of the user logged in.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity
Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

186
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the change)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Number of scheduled tasks

3.2. Modules
187

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the changes attached to the related elements
ò
Note
Any deletion or addition of a change is recorded in the histor y.
Associated Contr acts
The
Contracts
tab is used to show or add linked contracts.
For each associated contract, the name, number, contract type, supplier, star t
date and initial duration of the contract
are listed. In the last ˝eld, the end date of the contract is also shown with a red
display if the date is earlier than the
cur rent date.
Refer to
contract management
for more infor mation.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
188
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).
Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

ò
Note
Record types are not limited to the default ones and can be customized using drop-
down management.
The di˙er ent t abs
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Problems
The
Problems
tab is used to create a problem associated with the cur rent object. It also lists
the changes already linked
to the object.
This summar y table includes for each object :
190
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0

Status

Date (opening or expir y date, resolution or closing date depending on the status
of the problem)

Pr ior ity

Requestor(s) and assigned technician(s)

Associated elements

Categor y

Name

Column indicating the number of scheduled tasks

ò
Note
A second table lists the problems attached to the related elements
ò
Note
Any deletion or addition of a problem is recorded in the histor y.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
191

GLPI User Document ation, Ver sion 10.0

A web link :
http:// 192.168.0.1
(IP retr ieved from the network por t of the hardware) ;

A RDP link for remote access : glpi ://MSTSC.EXE,pc001 (name # pc001 # retr ieved
from the hardware).
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).
192
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Field that was changed.

Descr iption of the change that was made.

creating teams for a project and its tasks ;

tr igger ing sub-projects inside the project ;

building GANTT diag rams ;

using Kanban method ;

attaching costs ;

linking to GLPI ITIL items.

A project can be hierarchical, a project can therefore have sub-projects.
A project is character ized by name, code, state, type, provisional and real dates,
percent done.
Distinct management teams can by composed of users, g roups, suppliers and
contacts.
Several GANTT diag rams are available for each project (see tab
GANTT
).
Project management relies on two types of items : project and project task.
Project
The di˙er ent t abs
Project t asks
This tab allows to add new tasks to the project. It displays also already de˝ned
tasks with, for each task, its name, type,
status, planned star t and end dates, real star t and end dates, percent done and
parent task name.
3.2. Modules
193

GLPI User Document ation, Ver sion 10.0

Project team
This tab allows to add new members to the project team, this member being a
contact, a supplier or a g roup. It lists also
members of project team with for each member its type.
Project
This tab displays project's sub-projects. A sub-project is de˝ned the same way as a
project, the only di˙erence being
that the ˝eld
As child of
is de˝ned.
GANTT
A GANTT diag ram is available for each project. A global GANTT diag ram is also
available, including projects de˝ned
as visible in this global diag ram (˝eld
Show on global GANTT
of the project for m).
194
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Kanban
This tab provides an inter face to use Kanban method.
For more infor mation about the Kanban feature, please refer to the
full documentation
.
3.2. Modules
195

GLPI User Document ation, Ver sion 10.0

Costs
Costs can be attached to projects ; the costs of the tickets attached to project's
tasks will sum up to these costs.
ITIL objects
This tab allows to attach to the project GLPI ITIL objects : tickets, problems and
changes. It is also possible to create
these objects directly from this tab.
Associated elements
The
Items
tab is used to show or add linked assets.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
196
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Project t ask
Task item is quite similar to a project.
A project task can also be a project sub-task.
A task is character ized by name, state, type, provisional and real dates, percent
done.
Distinct management teams can by composed of users, g roups, suppliers and
contacts.
198
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
A project task is not an independent item, it can only be accessed through the
Project tasks
tab of the project owning
the task.
Tasks can be attached to tickets in order to plan inter ventions.
Planned and actual duration are also de˝ned for a task, repor ted at project level
together with attached tickets duration.
The di˙er ent t abs
Project t asks
This tab allows to display and add sub-tasks.
3.2. Modules
199

GLPI User Document ation, Ver sion 10.0

Task team
This tab de˝nes the team in charge of the task.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
200
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

a lifetime ;

a status ;

the possibility to appear in planning ;

its targets.
3.2. Modules
201

GLPI User Document ation, Ver sion 10.0

The created reminders will then appear in GLPI home page or in targeted users#
planning.
202
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to add a star t date and an end date for each reminder. If no star t
date is given, the reminder will be
visible immediately and until its end date. If no end date is given, the reminder
will be visible per manently star ting
from its star t date.
Adding a reminder to the planning makes it visible for targeted users of the
reminder : the owner for a personal
reminder, all users# plannings for a public note. A planned reminder is not deleted
after its end date.
The di˙er ent t abs
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
3.2. Modules
203

GLPI User Document ation, Ver sion 10.0

ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Targ et
A reminder is personal by default and therefore only visible for its wr iter.
For a reminder to be visible by other users (public reminder), it is necessar y to
add targets to the reminder. Possible
targets are entity, pro˝le, g roup or users.
A public reminder is visible by users associated with a pro˝le if this pro˝le has
read per mission for public reminders.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Gener ate r epor ts
GLPI allows to generate repor ts based on managed items :

Default report
This repor t summar izes present equipments sor ted by type. Computers are also sor
ted by operating systems.

By contract
This repor t shows the equipments that are under a maintenance contract with a
third-par ty and can be detailed
by equipment type and purchase date.
Multiple selection is available.
To add a type, it is possible to click in empty area and choose new type. Same
applies to add a date.
Generated table lists, sor ted by item type, name, if it is in trash bin, entity,
location, purchase and war ranty
expire date, contract type and contract begin and end dates.

By year
Same as repor t by contract, but lists also the equipments without contract.

Hardware ˝nancial and administrative information

This repor t shows the summar y of ˝nancial infor mation for computers, pr inters,
network equipments, displays,
per ipherals and phones.
It is possible to obtain a repor t for a given per iod.
The generated table lists, sor ted by item type, name, entity, value, net
accounting value, TCO, purchase date,
star ting date, war ranty expire date. A summar y displaying total value and net
accountin value is available, both
by item type and for all items.

Other ˝nancial and administrative information

Same as
Hardware ˝nancial and administrative infor mation
, but for car tr idges, licenses and consumables.

Network report
Three types of repor ts can be generated : by location, by hardware or by network
plug.

Loan
This repor t shows a summar y of cur rent, future and past reser vations for a
given user.

St atus
This repor t shows a summar y of di˙erent status, sor ted by equipment types.
ò
Note
The range of possible repor ts can be increased by adding to GLPI the following
plugin :
https:// plugins.glpi- project.
org/ #/ plugin/ repor ts
Manag e r eser vations
GLPI includes an equipment reser vation tool that allows to select assets in order
to reser ve them for a time slot. For
repetitive reser vations, it is possible to declare a reser vation as recur rent.
3.2. Modules
205

GLPI User Document ation, Ver sion 10.0

ò
Note
By default, an equipment is not reser vable !
Making an equipment reser vable is done from the
Reser vation
tab of the equipment's for m.
A reser ved equipment will be displayed in global reser vation planning.
206
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

It is also possible to consult the speci˝c planning of a reser vable equipment. A
reser vation can also be created from
this planning.
The di˙er ent t abs
Reser vations
This main tab of the tool allows to display and select available reser vable
equipments.
Administr ation
This tab display all reser vable items and not only the available ones. As for main
GLPI items, it o˙ers a search engine
with mass actions.
3.2. Modules
207

GLPI User Document ation, Ver sion 10.0

Manag e RSS feeds
GLPI allows to include RSS feeds in tool home page.
A RSS feed is by default personal and therefore only visible by its creator.
For a RSS feed to become public and visible by other users, targets must be added
to it, a target being either an entity,
a g roup, a pro˝le or a user.
ò
Note
A public RSS feed is visible by users associated with a pro˝le if this pro˝le has
read per mission for public RSS
feeds.
The di˙er ent t abs
Content
This tab allows to consult the number of displayed items ; this content is the one
displayed on home page.
Targ ets
This tab allows to display and modify the list of targets of the RSS feed.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Manag e knowledg e base
GLPI knowledge base has two main targets :

Gather inter nal knowledge for technicians ;

Provide infor mation as a public FAQ to enable users to solve simple problems on
their own.
ò
Note
Only public FAQ items are visible to users of simpli˝ed inter face. Other elements
are visible only to technicians
via standard inter face.
Each ar ticle of the knowledge base must have one or more targets, being entities,
g roups, pro˝les or users, to be readable.
As long as an ar ticle has no target, it is visible only by its wr iter, is ˛agged
as
unpublished
and appears in table
Unpublished ar ticles
on the home page of the knowledge base.
ò
Note
You can publish an ar ticle for ever yone by targeting the root entity.
By default, ar ticles are not translatable. However, this functionality can be
activated, see
general con˝guration
.
It is possible to attach documents to ar ticles of the knowledge base.
ò
Note
An ar ticle can be made visible dur ing a time slot by de˝ning a star t date and an
end date.
.
Avertissement
Elements which should not be inter preted when displayed can be de˝ned with prefor
mated style (
<pre>
in HTML).
Tags like
<VirtualHost>
can therefore be inser ted and will be displayed. Other HTML tags (
<TAG>...</TAG>
may disappear when editing ; to have complete visibility of the text, it is
possible to switch to HTML mode where
all elements will be visible. The browser may also modify dynamically content (case
change, tags adding) when
editing.
It is possible to create categor ies and sub-categor ies in order to organize
browsing (see
Con˝gure drop-downs
). User
can then use several tabs to search and browse knowledge base :

Search
This tab is the default tab, displaying recent ar ticles, popular ar ticles and
last changes. It allows also to
search inside knowledge base.
3.2. Modules
209

GLPI User Document ation, Ver sion 10.0

Browse
This tab allows to browse tree str ucture of categor ies.

Manage
This tab is only visible for knowledge base administrators. Depending on user's per
missions, it is
possible to access quickly user's ar ticles, user's unpublished ar ticles, all
unpublished ar ticles. . .
ò
Note
The knowledge base search engine provides operators for complex search :
+ - ~ < > * # # ()
.
210
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

+
: word must be there ;
-
: word must not be there ;

*
: tr uncate su˚x ;

" "
: contained sequence must be searched literally ;

< >
: de˝ne order on search elements ;

()
: g roup when using < and >.
Examples :
-
printer failure
-
>
Search lines containing at least one of these words
-
+
printer
+
failure
-
>
Search lines containing both words
-
+
mail thunderbird
-
>
Search lines containing word
*
mail
*
but rank higher lines containing also

,
!
word
*
thunderbird
*
-
+
mail
-
outlook
-
>
Search lines containing word
*
mail
*
but
not
word
*
outlook
*
-
*
+
mail
+
(
>
thunderbird
<
outlook)
-
>
Search lines containing word
*
mail
*
and
*
thunderbird
*
,
or
*
mail
*
and

,
!
*
outlook
*
,
in
any
order, but rank
*
mail thunderbird
*
higher than
*
mail

,
!
outlook
*
-
open
*
-
>
Search lines containing words such
as
*
openoffice
*
,
*
openwriter
*
,

,
!
*
openbar
*
,
*
openphp
*
.
.
.
-
"
openoffice suite
"
-
>
Search lines containing exactly sentence
*
openoffice suite
*
The di˙er ent t abs of an ar ticle
Knowledg e base
This tab displays a table with ar ticle categor y, subject, content, wr iter,
creation date, last modi˝cation date, number of
views and FAQ membership.
If an ar ticle is unpublished (i.e. has no target), this infor mation will appear
in red above number of views.
Targ et
This tab allows to manage ar ticle's targets.
An ar ticle is by default personal and therefore only visible by its creator.
For an ar ticle to become visible by other users, targets must be added to it, a
target being either an entity, a g roup, a
pro˝le or a user who will be able to consult the ar ticle.
3.2. Modules
211

GLPI User Document ation, Ver sion 10.0

Edit
This tab allows, if appropr iate per mission, to modify or delete an ar ticle.
Associated elements
The
Items
tab is used to show or add linked assets.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
212
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
3.2.5
Assist ance
Assistance module allows users to create, follow and process tickets. Plannings,
statistics and recur rent tickets are also
available.
Depending on pro˝le per missions, it is possible as well to create, follow and
process problems and changes.
GLPI assistance module is compliant with ITIL best practises guide and integ rates
therefore some ˝elds nor maliza-
tion. However, following ITIL best practises is recommanded but not mandator y and
it is per fectly feasible, thanks to
module's ˛exibility, to implement an assistance ser vice tailored to the
organization's needs.
De˝ning actor s and roles
An assistance ser vice usually de˝nes the following roles :

Requester
: user or g roup of users known to GLPI and a˙ected by the ticket ;

Technician
: ticket processing is done by a technician, by a g roup or by a supplier ;

Watcher
: user who can follow a ticket but without modifying it ; follow-up can be done
from GLPI inter face
or by receiving noti˝cations.
Visible infor mation and possible actions are de˝ned by GLPI based on the user's
role, which is de˝ned in user's pro˝le :

Technicians are the actors having the most complete infor mation on a ticket and
the widest possible actions

Requester and watcher will only view the infor mation needed to ful˝ll request.
For multiple users or g roups, only the ˝rst user or g roup is de˝ned when creating
the ticket, more actors are added later.
A user who cannot modify actors but able to see the ticket can become a watcher.
When associating a new actor to a ticket, the number of tickets assigned to this
actor is visible ; this eases for instance
task par titioning between technicians.
ò
Note

for users who are not known to GLPI, mail address can be associated to a ticket.
Default choice for re-
quester and watcher (no selected user) allows to add a mail address in these
˝elds ; for this to be available,
noti˝cations must be activated (see noti˝cation management)

Role attr ibution is done in user's author ization management (see Attr ibute
author izations to a user)
Matrix of calculus for priority
This matr ix is common to all help desk items (tickets, problems and changes) and
can be parameter ized in tab
Assistance
of menu
Setup > General
.
ITIL best prac tices separate urgency (as de˝ned by the user) from incident impact
(a user, a ser vice, a functionality. . .)
which is usually set by the technician. A matr ix is then used to compute the pr
ior ity associated to the item of the help
desk (ticket, problem or change) as a function of both urgency and impact. GLPI
provides a default prede˝ned matr ix
which cor responds to standard cases.
This prede˝ned matr ix can be modi˝ed in tab
Assistance
of menu
Setup > General
(see
Con˝gure general parameters
.
Knowing that the order of items processing by technicians is based on pr ior ity,
it is possible to select the di˙erent levels
of urgency, impact or pr ior ities that will be used in the help desk and to
disable some of them. This action allows to
ease declaration of an incident and its proc essing. To disable a level, this level
must be set to
No
. Medium level cannot
be disabled.
214
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

In example above, the urgency level
Low
will not be proposed to requester and the impact level
High
will not be proposed
to the technician.
ò
Note
The
Major
pr ior ity used by tickets is not par t of the matr ix. This level is higher than
any other and requires the
per mission to modify pr ior ity in order to be able to assign it. A
Major
incident is a ticket whose processing is of
such high impor tance that it over r ides any other ticket.
Tic kets
Opening a tic ket
A requester for mulating a need can use several tools :

˝lling an online for m, the requester being known to GLPI or not ;

asking a delegate in the g roup to open the ticket (see

Administer groups
. In simpli˝ed inter face, this is put into
evidence by an option allowing to indicate if the ticket concer ns the requesting
user or another user. In standard
inter face, this mechanism is active as long as author ization
See all tickets
is set to
No
in the pro˝le ; all users
for which delegation is active will be added as requester ;

contacting an operator directly or by phone, the operator will open the ticket ;
sending the demand by mail.
Opening a tic ket in GLPI
A ticket can be opened :

through the anonymous ticket opening inter face, this inter face being accessible
by all non-authenticated users
if GLPI general con˝guration allows it ;

through the g raphical inter face :

simpli˝ed inter face : lightweight for m for an authenticated end-user ;

standard inter face : full-˛edged for m.

Anonymous tic ket opening inter face for non-authenticated user s
This inter face can be accessed at URL
http:// /front/ helpdesk.html
; it allows users having no GLPI account to send an
incident signaling for m to the help desk. Once ˝lled and submitted, a mail will
con˝r m the ticket opening.
The for m can be customized by modifying directly ˝le
helpdesk .html
.
By default, ticket is created in root entity.
3.2. Modules
215

GLPI User Document ation, Ver sion 10.0

Opening a tic ket in gr aphical inter face
If templates are used (see
Using templates
), some ˝elds can be made mandator y, prede˝ned or masked when opening
the ticket (content, title and/or categor y). If a mandator y ˝eld is missing, the
ticket will not be opened.
The di˙erent ˝elds are descr ibed in
Manage tickets
.
It is possible to attach to the ticket one or more documents in one operation.
When activating option
Use rich text for assist ance
in general con˝guration, the
Description
˝eld of the ticket will
be able to be for matted as HTML. Moreover, an added zone will be available for
images drag and drop, for example
screenshots. A tag will then be added automatically to the descr iption in order to
for malize the content of the demand.
Sim pli˝ed inter face
This inter face allows an authenticated user to open quickly a ticket, for the user
or by delegation for another person.
Ticket opening for m can be accompanied by a message inviting user to check
personal infor mation (location, phone
number) in order to be easily contacted by technicians.
Speci˝c ˝elds :

Inform me about he actions t ake

: Appears if email followup are con˝gured, see noti˝cation management. If
set to
Yes
, the requester will be kept infor med by mail of the di˙erent processing of the
ticket. The ˝eld
Mail
contains the email address to which noti˝cations will be sent. If several email
addresses are de˝ned, GLPI will
select the default email de˝ned in user's preferences. It is possible to select
another email address or to enter an
address if user's pro˝le does not mention an email ;

Associated elements
: Allows to associate an item of the inventor y with the ticket. The content of the
list
depends upon parameters de˝ned in user's pro˝le (see
Administer user pro˝le
.

Watchers
: Allows to add a watcher and to de˝ne noti˝cation parameters.
#
Indication
Users can add new email addresses to the pro˝le, see
Manager preferences
.
.
Avertissement
If images or documents are added to the ticket, it is impor tant to add them
after
having ˝lled
all
mandator y ˝elds
marked with a red star, this because the reloading of the ticket opening for m tr
iggered by a missing mandator y ˝eld
suppress attached images or documents.
A message con˝r ms the creation of the ticket which is then accessible by clicking
on the ticket number highlighted in
g reen.
St andard inter face
To create a ticket, go to menu
Assist ance > Ticket
then click add button with the # + # icon.
When adding a new image from tab
Documents
of the ticket, the generated tag can also be used to inser t image in
ticket's descr iption.
A message con˝r ms the creation of the ticket which is then accessible by clicking
on the ticket number highlighted in
g reen.
A validation demand can also be done at ticket opening by indicating the desired
validating user.
216
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
When ˝lling assigned requester, technician or g roup, infor mation is displayed
about the number of tickets this
person or this g roup has opened or is in charge of. Similarly, when selecting an
item, a simpli˝ed view of cur rent
tickets for this item is displayed.
Open a tic ket by mail
Opening a ticket by mail is done by sending a mail to an email address de˝ned in
the collector (see
Con˝gure collectors
On reception of the mail, a ticket will be opened automatically :

message object will become ticket title

body will become ticket descr iption

Cc : will become obser vers if emails are known to GLPI

attachments will become attached documents of the ticket

When activating option
Use rich text for assist ance
in general con˝guration, the images present in the message body
will become visible in the descr iption of the ticket.
Open a tic ket automatically
This mechanism is activated through
Recurrent tickets
.
Tic ket life cycle
Ticket life cycle is de˝ned at
pro˝le
level in a
life cycle matrix
. To display a life cycle and modify it, it is therefore done
in pro˝le management for m (menu
Administration > Pro˝les
).
Tic ket types
GLPI tickets are either incidents or requests, this type being stored in ˝eld
Type
of the ticket. This type ˝eld allows to
per for m actions based on ticket type (see business r ules for tickets modi˝cation
and assignment,
ticket templates
and
problem management
) and to customize the list of available categor ies.
St atus
ITIL de˝nes a standard for ticket status life cycle. This status life cycle is
implemented in GLPI by de˝ning the following
status :

New

Processing (assigned)

Processing (planned)

Pending

Solved

Closed
These status can neither be parameter ized nor modi˝ed.
ò
Note
It is therefore possible to hide some status according to pro˝le (see
Life cycle matrix
).*
To go fur ther in status management, refer to
ticket templates
and business r ules for tickets modi˝cation and assignment.
3.2. Modules
217

GLPI User Document ation, Ver sion 10.0

Scheduling
Ticket scheduling is done according to data provided by the requester and the
technician :

Requester de˝nes urgency

Technician appreciates the impact

Pr ior ity results from these two values. It is computed automatically using a matr
ix and provides the tr ue impor tance of
the ticket.
ò
Note
To go fur ther on this matr ix con˝guration, see
De˝ne the matrix of calculus for priority
.
Manag ement rules
The ticket status follows the following process :

upon creation, the ticket has status

New

when a technician assigns ticket processing to a g roup, a technician or a

supplier, the ticket goes to status
Processing (assigned)

when a new task is added to the ticket and is planned, ticket status become then
Processing (planned)

when a solution is found for the ticket, its status become

Solved

at last, then requester or wr iter validates the proposed solution, the ticket
status is
Closed
ò
Note

Technician can change ticket status at ever y moment, in par ticular to p ut the
ticket to
Pending
. Following
ITIL recommendations, a ticket must be made
Pending
only by the requester, for example if request is not
complete or if requester is not available for an inter vention

Requester can delete the ticket as long as the ticket status is

New
and no action has been done on the ticket
Manag e tic kets
Manag e tic kets following ITIL r ecommendations
GLPI assistance module is compliant with ITIL best practices guide for incident and
request management : it integ rates
therefore notions such as impact, ticket urgency, pr ior ity calculus matr ix and
status standardization. Despite the fact
that GLPI is ITIL compliant, it is not mandator y to follow these best practices
and freedom is given to implement an
incident management best tailored for organization's need.
Statistics are available for tickets, see
Display statistics
.
Description of speci˝c ˝elds

Opening date
: ticket creation date ;

Time to Resolve
: date at which ticket must be solved ;
These two dates allow to limit in time incident or ser vice request. A
SLA
can also be associated with the ticket ;
in this case the SLA and the next escalade level are displayed (see Con˝gure SLA).

By
: references the GLPI user having opened the ticket ;

Type
: de˝nes whether it is a request or an incident ;

Category
: allows to sor t request or incident by their nature, a categor y being associated
to only one type ;

St atus
: status attr ibuted manualy by the technician or dynamically by per for med
actions, see
Management
r ules
and
life cycle matrix
;

Request Source
: indicates the channel used to create the ticket, see
Con˝gure drop down
;

Urgency
: impor tance given to the ticket by the requester ;
218
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Impact
: impor tance given by the technician ;

Priority
: impor tance of the ticket automaticaly computed from de˝ned impact and urgency
using a prede˝ned
calculus matr ix, see
life cycle matrix
;

Approval
: by default the ticket is
Not subject to approval
;

Items
: list items associated to this ticket ; ˝eld appear ing only in ticket creation
for m, later editions will display
items in a separate tab also used to associate new items to the ticket ;

Location
: indicates the inter vention location, has no link with the location of associated
items nor with the
requester location (for example roaming requester with a laptop) ;

Actor
: implied actors are referenced in the ticket, which allows them to b e noti˝ed dur
ing ticket life cycle, see
De˝ning actors and roles
.
If email followup have been con˝gured (see noti˝cation management), infor mation
about noti˝cations are dis-
played for a user or a supplier :
Email Followup
(yes or no) and
Email
. Email is pre-˝lled with user's email if
de˝ned in user or supplier for m. If no email is de˝ned in user or supplier for m,
an email can be entered in text
˝eld.
v
À faire
proof read following parag raph
When using GLPI with multiple entities and having technicians with author izations
for several entities, it is
not needed to switch cur rent entity to declare a new incident inside an entity.
Entity to which ticket will be
assigned is deter mined as so : technician selects requester and GLPI ˝nd entities
for which this requester has
author izations ; if only one entity, ticket creation for m is updated and ticket
will be declared in this entity, if
several entities, a drop-down list allows to select the entity to which ticket will
be assigned.

Title
: if no tile is de˝ned by the user when creating the ticket, the ˝rst 70 characters
of the descr iption will be
used to de˝ne ticket title ;

Description
: mandator y, for above reason ;

Linked Tickets
: de˝nes a link between tickets, this link being of two types :

Linked to
: a simple link only used as infor mation ;

Duplicates
: when solving one of the duplicated ticke ts, the same solution is applied for
other duplicated
tickets which are therefore automatically solved.
v
À faire
Missing descr iption of
Son of
and
Parent of
The di˙er ent t abs
Processing tic ket
This tab displays exchanges between requester and personal in charge of the
ticket ; it allows to add infor mation on the
ticket such as requester call, ticket waiting for requester disponibility. . .
This tab is the default tab when consulting a ticket except when the ticket is
waiting for approval.
To add a followup, click on
Followup
and enter a descr iption.
It is possible to choose the source of the followup, see
Con˝gure dropdown
.
A followup can be public or pr ivate. A pr ivate followup is only visible by GLPI
users having the author ization
See all
followup and tasks
. It allows for instance to have an exchange between technician which is not
visible by requester.
Adding, modifying and deleting a followup is submited to author izations de˝ned in
pro˝le, see
Administer user pro˝les
.
3.2. Modules
219

GLPI User Document ation, Ver sion 10.0

Approvals
See Validation
Project Tasks
A task is an action cor responding to a technical inter vention related to the
ticket.
See Tasks
Solution
This tab allows resolution of a ticket by a technican and approval of solution by
requester.
See Solutions
St atistics
See Statistics
Items
Allows to associate several items to the ticket.
See Items
Chang es
Allows to add and display changes associated with the ticket.
See Changes
Problems
Allows to display and add problems associated with the ticket, or to create a
problem from this ticket.
See Problems
Historical
Display the histor y of the ticket.
See Histor ical
220
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Reccur ent tic kets
Using templates, it is possible to prog ram recur rent ticket opening.
ò
Note

Open a ticket ever y Monday to check that weekend back up was cor rectly executed

Open a ticket ˝rst day of the month to per for m initialization operations
The di˙er ent ˝elds

Active
: allows to disable temporar ily ticket creation ;

Ticket template
: model that will be used for ticket creation ;

St art date
: star t date for ticket creation, mandator y ;

End date
: optional, de˝nes ticket creation end date ;
Periodicity
: ticket creation per iod ;

Preliminary creation
: time for anticipated ticket creation ;

Calendar
: allows to limit ticket creation days.
ò
Note
3.2. Modules
221

GLPI User Document ation, Ver sion 10.0

Tickets will only be created if
Active
is
Yes
and if cur rent date is between
Star t date
and
End date
.
Reccurent ticket opening is done through an automatic action named
recurrent ticket
, see
Con˝gure automatic actions
.
To go fur ther
Tic kets categories
See
Categories
Tic kets tem plates
Using ticket templates, it is possible to customize ticket creation for m by
masking, pre-de˝ning or making mandator y
some ˝elds.
See
Ticket templates
Collector s
Exter nal tools can interact with assistance module using mail collectors.
Email is used to create tickets and add follow-up to existing tickets. A GLPI inter
nal task will connect to a mailbox and
fetch messages.
ò
Note
The solution or closure of a ticket are not available via collectors.
A mail message will go through the following steps :

Mail box ;

Collector, con˝gured using

Con˝gure collectors
;

Rules, see
Assigned a ticked opened by mail to an entity

Business r ules, see Business r ules for tickets

Ticket is created
An answer to a mail coming from GLPI will go through the following steps :

Mail box ;

Collector ;

Creation of a follow-up for concer ned ticket.

Recurr ent tic kets
See
Recurrent tickets
Att ached costs
See
Attached costs
Links between tic kets
It is possible to de˝ne links between tickets or to mark tickets as duplicates.
See
Links between tickets
222
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Processing time
Incidents resolution delays or SLA can be con˝gured.
See Con˝gure SLAs.
Business rules
Business r ules can be de˝ned to modify and assign tickets.
See Business r ules for tickets.
Administr ative closur e
Administrative closure moves the status of a ticket from
Solved
to
Closed
.
ITIL best practices recommends a validation of the solution by the ticket
requester, who validates that the answer
provided by the technician cor responds to the demand. However, if the requester
does not ful˝ll this validation, it is
possible to parameter ize an administrative closure after a delay which can be
con˝gured at entity level (see
Assistance
tab
). If this delay is set to zero, the ticket is automatically closed.
Satisfaction
(I can't get no)
A satisfaction sur vey is tr iggered when the ticket status is set to
Closed
and the tr igger ing delay is elapsed. This tr ig-
ger ing delay is parameter ized at entity level (see
Delegate administration at entity level
).
ò
Note
The automatic task that tr iggers the sur vey must be activated.
When ticket is closed, a noti˝cation that includes a link to the satisfaction sur
vey can be sent to the requester. The
requester will also have access to the sur vey from the ticket for m in tab
Satisfaction
.
The requester can then select the satisfaction level (from 0 to 5, given as stars)
about the ticket solution. A comment
can also be added.
Statistics on sur veys are available in
statistics
.
ò
Note

the requester can change the answer to the satisfaction sur vey within a delay of
12 hours after ˝rst answer

a noti˝cation can be sent when satisfaction sur vey is generated, but also on each
answer to this sur vey
See also
See
Advanced con˝guration
.
Manag e problems
A problem is the cause of potential incidents and, once identi˝ed, can be managed
in GLPI.
Creating a problem object can be done either from the ticket for m, in tab
Problem
, or directly from menu
Assistance >
Problems
.
3.2. Modules
223

GLPI User Document ation, Ver sion 10.0

The problem creation for m is ver y similar to the ticket creation for m and shares
with it many concepts :
Requester
,
Watcher
,
Assigned to
,
Status
,
Urgency
,
Impact
,
Priority
,
Categor y
. For more infor mation, see
Manage tickets
.
v
À faire
Check what is means From tickets list, an alter native solution can be associated
to linked tickets without solving
the problem. Depuis la liste des tickets, une solution de contour nement peut être
associé massivement aux tickets
liés sans pour autant résoudre le problème.
Problems use their own noti˝cations, see con˝guration of email follow-ups.
Statistics similar to tickets are available for problems, see
Display statistics
.
The di˙er ent t abs
Chang es
This tab allows to display changes associated with the problem and add new changes.
See Solutions
Analysis
This tab contains problem analysis and descr ibes impacts, causes and symptoms.
Solutions
This tab allows to descr ibe the resolution of the problem. See Solutions
St atistics
Statistics similar to tickets are available for problems. See Statistics
Tasks
A task is an action linked with a problem, usually a technical inter vention. See
Tasks
Costs
This tab de˝nes the costs applicable to this problem. See Costs
Elements
This tab allows to attach an item to the problem by choosing the type and the
selected item. See Items
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
224
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
3.2. Modules
225

GLPI User Document ation, Ver sion 10.0

N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

The descr iption of the change represents either the di˙erence between the old and
the new value (For example with
location ˝eld : Change HQ to Remote O˚ce A), or the explanation of the action which
was car r ied out (For example :
Uninstallation of a software : # Gimp 2.0 #).
ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Manag e chang es
A change is a modi˝cation of the infor mation system's infrastr ucture.
A change can be created either from a ticket for m or a problem for m, in tab
Changes
, or from menu
Assist ance >
Changes
.
The for m to create a change is similar to the ticket creation for m and shares
with it many ter ms :
requester
,
watcher
,
as-
signed to
,
status
,
urgency
,
impact
,
priority
,
categor y
. For more infor mation see
Manage tickets
. The validation process
is also the same as tickets in order to allow preliminar y validation of the change
(tab
Validations
).
Once the change is created, it is possible to attach tickets but also impacted
items (tab
Items
). An analysis ph ase (tab
Analysis
) consists in descr ibing impacts and controls list in order to implement this
change through a deployment plan,
a back up plan and a checklist (tab
Plans
).
Same as tickets, task, costs and solution allow to follow and solve the change. For
complex changes management, a
change can be linked with one or several projects allowing a mode detailed
management (
Manage projects
).
226
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Changes use their own noti˝cations (see con˝guration of email follow-ups).
The di˙er ent t abs
Analysis
This tab contains impacts and check-lists in order to implement the change.
Plans
This plan contains deployment plans, back up plans and check-lists.
Projects
This tab allows to attach a project to the change and displays already attached
projects.
The summar y table contains for each project status, opening or closing dates, pr
ior ity and super visors.
Solutions
This tab allows to descr ibe the resolution of the change. See Solutions
St atistics
Statistics similar to tickets are available for changes. See Statistics
Approvals
See Approvals
Tasks
A task is an action linked with a change, usually a technical inter vention. See
Tasks
Costs
This tab de˝nes the costs applicable to this change. See Costs
Elements
This tab allows to attach an item to the change by choosing the type and the
selected item. See Items
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
3.2. Modules
227

GLPI User Document ation, Ver sion 10.0

Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Tic ket life cycle matrix
See
Ticket management r ules
.
In example above, a
New
ticket will never be put to
Waiting
, this status being not proposed in the ticket.
Fur ther more, a requester will not have access to solution validation for m,
because a solved ticket for which solution
has been approved becomes closed, which is not author ized by the example.
For the simpli˝ed inter face, ticket life cycle allows to de˝ne if user can close a
ticket (solution approved) and if user
can re-open it event if it is closed.
Problem life cycle matrix
See
Ticket management r ules
.
In example above, a
New
problem will never be put directly to status
Solved
, this status being not proposed in the
problem.
230
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Chang e life cycle matrix
See
Ticket management r ules
.
In example above, a
New
change will never be
Accepted
before having its status put to
Evaluation
or
Validation
, this
status being not proposed in the change.
Managing plannings
Planning view allows to display planned tasks attached to a ticket, a problem or a
change as well as planned notes or
plugins# planned elements.
This menu is only visible if pro˝le includes
View planning
author ization.
Date and time slot can be selected. A ˝lter ing on objects to include in planning
is also available.
Four views are available, depending upon user author izations :

Personal view : includes only the elements of the connected user ;

Group view : includes only the elements of the connected user's g roup, needs
See planning of group's persons
author ization ;

Users view : includes the planning of a par ticular user, needs

See all plannings
author ization ;

Groups : includes the planning of a par ticular g roup, needs

See all plannings
author ization ;
This infor mation can be expor ted in two for mats :

Ical, in order to integ rate planning in third-par ty tool calendar ;

Webcal, which allows to subscr ibe a third-par ty calendar to GLPI planning.

ò
Note

Access to Ical and Webcall feed is protected by a secur ity key integ rated into
the URL. It is possible to
regenerate this key in menu
Preferences
. See
Manage preferences
.

User's planning can be displayed on home page if pro˝le has author ization
See my personal planning
.
However, it is not possible to add an element to a planning from this inter face ;
it is mandator y to plan a task
or a note so that planning ˝lls up.
Display st atistics
Statistics g roup repor ts on tickets as well as repor ts coming from plugins.
Repor ts can be parameter ized on a given time slot.
3.2. Modules
231
GLPI User Document ation, Ver sion 10.0
Repor ts on tic kets

Global :
Display general statistics on tickets :

Number of opened , solved, late and closed tickets ;

Average time of processing, resolution, closure and real duration ;

Number of satisfaction sur veys, opened or answered ;

Average satisfaction.

By ticket :
Display statistics on tickets items, selected via a dropdown (requester, assigned
technician, impact. . .).
Table shows following items in four g roups :

Number of opened , solved, late and closed tickets ;

Number of opened satisfaction sur veys, number of answers and average satisfaction
;

Average
Take into account
time (duration between ticket openin g and ˝rst action on ticket, follow-up, task
or solution), resolution time or closure time ;

Real ticket duration, average and total (real duration of allocated technician
time for actions relevant for the
ticket).

By hardware characteristics :
Displays statistics on computer items de˝ned in associated items of a ticket (for
example, model, operating
system, motherboard. . .)
The table g roups the same numbers as de˝ned in statistics by tickets.
For these two types of repor ts, the button
located on each result line allows to display the statistics as a
g raphic.

By hardware :
Display number of tickets assigned to each hardware, sor ted by number of tickets.
The option
See graphics
, when available, allows to display result as a pie char t.
ò
Note
When statistics are done on a tree str uctured item (g roups or categor ies for
example), two presentations are avai-
lable :

Nor mal : all values are displayed

Tree : only values at same level are displayed, taking into account the tickets
attached to child elements. It
is possible to navigate into values tree.
Categories
A categor y can be made hierarchical :

by selecting a parent categor y using in ˝rst tab the ˝eld

As child of

by adding a new child categor y in tab

ITIL Categories
ITIL categories
ITIL categor ies can be managed in dropdown setup
Setup > Dropdowns > Ticket Categories
.
ITIL categor ies are used by Tickets, Changes and Problems.
232
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

A person in charge and/or a technical g roup can be added to this categor y and
will then be used for noti˝cations.
A knowledge base categor y can also be associated to this categor y ; this will
register the solution in this categor y of the
knowledge base.
In this example, if you have a ticket with the categor y # Hard disk failure #
which is linke d to the KB categor y # Failure
> Computer #, when you add a solution to the ticket with # Save to Knowledge base #
set to # Yes #, the default categor y
in the new Knowledge base Ar ticle for m that opens will be # Failure > Computer #.
A categor y can be invisible in simpli˝ed inter face, in order to reduce list of
categor ies for end-users. It can also be
made visible or not for incidents, demands, problems or changes.
A template can be associated with this categor y and will be loaded when this
categor y is selected in ticket. This template
can be di˙erent for demands and incidents.
#
Indication
When building a helpdesk, it is impor tant to choose carefully the list of
available categor ies : a too large number
visible by end-users will make ticket creation less easy, whereas a too small
number will not allow you to cor rectly
qualify the demand.
Ticket categor ies allow to do automatic processing when creating a ticket, for
instance modify ticket attr ibutes ; see
Business r ules for tickets.
Task categories
Task categor ies are used to sor t task in order to ease their processing or to
build meaningful statistics.
Tickets, Changes and Problems can be viewed globally in a Kanban view. For more
infor mation about the Kanban
feature, please refer to the
full documentation
.
3.2.6
Administr ation
Administration module allows to administrate users, g roups, entities, pro˝les, r
ules and dictionnar ies.
3.2. Modules
233

GLPI User Document ation, Ver sion 10.0

User s
User management allows to add, modify, delete, search users and to impor t and
expor t users list.
Im por t user s
From users list, three options are available for adding a user
:

Add user
: Opens a user creation for m, similar to the
Add
button ; requires pro˝le to be g ranted user creation
author ization

. . .From an external source

: Impor t users from exter nal source

LDAP directory link

: Impor t and synchronize users from LDAP director y
Im por t user s from external source
This button is available when pro˝le is g ranted user
Exter nal add
author ization. The identi˝er of a user being known,
GLPI allows to search user and to impor t user's authentication infor mation from
an exter nal source. Once user's connec-
tion identi˝er ˝lled, this identi˝er is search in available director ies (button
Impor t from directories
) or in other sources
(button
Impor t from other sources
).
.
Avertissement

if more that one user is identi˝ed by provided identi˝er, then adding is not per
for med

when using a mail director y for authentication, no impor t user list is available
User personal infor mation can be impor ted under some conditions from a LDAP
director y ; users impor ted from a mail
ser ver do not get personal infor mation.
Im por t and synchronize user s from LDAP dir ector y
This button is available when pro˝le is g ranted user
Exter nal add
author ization. GLPI allows users advanced search in a
LDAP director y. The inter face is restr icted to the list of entities for which
GLPI connected user is g ranted author ization
(see
Administer user pro˝les
). Once entity is selected (if GLPI is in multi-entities mode or if connected user
is g ranted
author ization for several entities), a list of cr iter ia is displayed, based on
personal infor mation collected from director y.
The search syntax for ˝elds is similar to the syntax of GLPI search engine (see
Search
). Search can be limited to users
added or modi˝ed in the director y dur ing given time slot by following link
Activate date ˝ltering
.
ò
Note

In order to be able to use simpli˝ed inter face, either LDAP parameters for the
entity must have been con˝-
gured ˝rst using
Administration > Entity
to assign a director y to the entity or a default director y must have
been de˝ned.

This option, coupled with search on cr iter ia, allows to bypass the limit of
records retur ned by director y for
a LDAP request (see
Authenticate users with LDAP directories
)

Simpli˝ed inter face does not require wr ite author ization for users. An asset
manager or a technician can
therefore impor t users from the director y without having access to these impor
ted users after impor t. This
option is for example useful for a call center or for a director y from which mass
users impor t is not desired.
An
Expert Mode
is also proposed by following link on the r ight of table header. This mode is
available for users
g ranted with update author ization either for general con˝guration or for e
ntities. Unlike simple inter face, results are
not ˝ltered by entity : the only available cr iter ia are director y, based and
users search ˝lter.
234
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

.
Avertissement
advanced inter face is reser ved for administrators having knowledge of both LDAP
director y and GLPI users mana-
gement.
Once impor ted from a director y, GLPI stores user's LDAP unique identi˝er (the
distinguedName
or
DN
) in addition to
connection identi˝er. This allows to manage updating connection identi˝er when DN
is left untouched. For example,
if connection identi˝er is email address, GLPI will be able to update it without
recreating a new user in the case of a
change.
If an exter nal authentication source is con˝gured, it becomes possible to impor t
and synchronize users using this
source. For regular maintenance of the users base, it is recommended to use the
GLPI CLI command
glpi :ldap :syn-
chronize_users
. For daily management, the manual impor t mechanism is available (see above).
It is possible to deactivate a user if needed. If deactivated, the user can no
longer be selected in drop-down menu for
tickets or inventor ies, but keeps associated items and tickets. Validity dates can
also de˝ne the activity time slot of
user : the user account will be considered as active only after the star t date
and/or before the end date. Both dates can
be de˝ned independently.
A photo can be added manually or impor ted automatically from a director y (see
Authenticate users with LDAP).
Im per sonate
For debugging or administrative pur poses, it's possible for a #super-admin#
account (or any pro˝le with the con˝gu-
ration r ights) to temporar ily take the ownership of another user's account
without knowing its password. An icon is
available at the top of the user
´
s for m to per for m this action.
To note :

A special banner will show per manently as long as the function is active and will
allow you to exit this mode.

After the exit, the admin will retr ieve its session as it was before using the
feature.

The histor y of actions taken by the administrator will appear with a special note
: #user (xxx) impersonated by
admin (yyy)#.
3.2. Modules
235

GLPI User Document ation, Ver sion 10.0

The di˙er ent t abs
Authorizations
This tab allows to manage user author izations. To add an author ization, select
entity for which author izations must be
given, then select the pro˝le to attr ibute. the option
Recursive
allows to associate the chosen pro˝le to all sub-entities
of selected entities.
A summar y tab displays already attr ibuted author izations for the user.
Groups
This tab lists the g roups associated to the user. Table includes g roup name,
whether the g roup is dynamic (i.e. linked
to a director y ser vice), whether the user is delegatee or manager for the g roup
(see
Manage groups
).
If modify user author ization is g ranted, it is also possible from this tab to
assign a g roup to the user.
Settings
This tab allows to edit user's settings (see
Manage settings
). In order to be able to modify data in this tab, general
con˝guration modi˝cation author ization must be g ranted.
Used items
This tab lists the items for which user is de˝ned in ˝eld
User
of the item or for which user is member of the g roup
de˝ned in ˝eld
Group
of the item.
See Tab # Used items #
Manag ed items
This tab lists the items for which user is de˝ned in ˝eld
Technician in Charge
of the item or for which user is member
of the g roup de˝ned in ˝eld
Group in Charge
of the item.
See Tab # Managed items #
Reser vations
This tab lists passed, cur rent and future reser vations of the user. In order to
see this tab, read author ization on reser vation
management must be g ranted.
See Tab # Reser vations #
Synchronization
This tab is displayed if
Update Authentication and Synchronization
r ight is g ranted. It allows to change authentication
method for the user and to force its synchronization.
External Links
This tab list exter nal links de˝ned for users.
See Tab # Links #
236
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
For users, this tab allows to list tickets created by the user but also to create
directly a ticket (the user will then be
de˝ned automatically as
Requester
).
Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
3.2. Modules
237
GLPI User Document ation, Ver sion 10.0
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

238
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Groups
Groups tab allows to add, modify, delete, search, expor t g roups.
Groups can be de˝ned in a hierarchical str ucture in order to ease navigation and
search.
Example : groups
: :
Management > Division > Ser vice or N3 Suppor t > Network > LAN
Groups can be used in several way to g roup users by : *
skills
: for the helpdesk, for example network technicians, or
database administrators, *
organizational groups
: for example all the computers of the management or the accounting
depar tment but also set of persons to be noti˝ed.
The options available to adjust these behaviors are : *
Visible in a ticket
: requesting g roup and/or assignment to this
g roup ; *
Can be noti˝ed
: recipient of noti˝cations ; *
Can be supervisor
: only for a
project
; *
May cont ain
: assets
and/or users.
In an item for m, 2 notions of g roups are available : *
technical group
which indicates which g roup of people is in
charge of the asset (equivalent for a g roup of the technical manager) *
group
which indicates to which g roup of items
it belongs.
ò
Note
the technical g roup can allow the automatic assignment of a ticket to a g roup of
technicians, see the ticket categor ies
in the chapter : doc :
Con˝gure dropdowns </modules/con˝guration/dropdowns/assistance.rst>
. Likewise, it can
be used in Business r ules for tickets.
#
Indication
if all options are set to
No
, the g roup will not appear in any selection list ; this can be useful for a g
roup that is
deleted and kept for histor y or for adding empty g roups in the hierarchical str
ucture.
A g roup can have one or more super visors, concept which can then be used for
noti˝cations, for example to send an
email to the super visor(s) of the g roup when a ticket is opened, see noti˝cation
management.
A
delegation
mechanism allows a user to declare incidents not for himself but for one of the
members of this g roup.
Example : delegation
an assistant declar ing incidents for all persons of the management
The concepts of delegation and super visor can be con˝gured in the # Users # tab
(see below).
Assigning a user o a g roup is either static and done using the GLPI inter face, or
dynamic when this is automatically
extracted from the LDAP director y.
3.2. Modules
239

GLPI User Document ation, Ver sion 10.0

A g roup is attached to the entity in which it is created and can then be visible
in sub-entities.
From the list of g roups, a g roup can be impor ted from a LDAP director y via the
LDAP director y link
button if exter nal
authentication is used and the # Auth and sync update # author ization is g ranted
in pro˝le. The assignment of users to
g roups will be automatic, see
Pro˝les
. If several director ies are con˝gured, the choice between director ies is
proposed,
other wise the search for m is directly accessible.
Depending on how you search for g roups (see : doc :
Authenticating users from LDAP directories </mo-
dules/con˝guration/authenti˝cation/ldap>
), a
Search ˝lter in groups
and/or a
User search ˝lter
appear : these allow
to re˝ne the list to be impor ted. If GLPI is used in multi-entities, it is
necessar y to select the destination entity of the
g roup as well as its visibility in the sub-entities.
ò
Note
impor ting g roups cannot be ˝ltered by entity. In addition, no g roup
synchronization function is available. The only
way to refresh from a director y the list of g roup members is to resynchronize
users, see
Impor t users from an
exter nal source
.
.
Avertissement
when mig rating from a version of GLPI lower 0.80, any manual connection previously
car r ied out on a g roup
coming from the LDAP director y will be lost.
The di˙er ent t abs
Sub-groups
This tab allows to add a subg roup to the selected g roup and lists the existing
subg roups.
Used items
This tab lists the elements for which the
Group
˝eld cor responds to the cur rent g roup. The search can be extended to
sub-g roups as well as to the members of the g roup (
User
˝eld of the item).
See Tab # Used Items #
Manag ed items
This tab lists the elements for which the
Technical Group
˝eld cor responds to the cur rent g roup. The search can be
extended to sub-g roups as well as to the members of the g roup (
Technical manager
˝eld of the item).
See Tab # Managed Items #
LDAP dir ector y link
This tab only appears if the # Auth and sync update # author ization is g ranted in
pro˝le ; it gathers the infor mation
allowing GLPI to ˝nd the g roup and its users in the LDAP director y.
User s
This tab allows to add a user to this g roup by de˝ning whether the added user is
delegatee
and/or
super visor
of the
g roup. It also lists the users of this g roup with possible search by cr iter ia
(delegatee or super visor) and also in the
subg roups of the cur rent g roup.
240
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

N oti˝cations
Fig. 1
# List of noti˝cations for which destination is g roup or g roup super visor
Tic kets
The
Tickets
tab is used to create a ticket associated with the cur rent object. It also lists
the tickets already linked to the
object.
ò
Note
A second table lists the tickets attached to the linked elements
ò
Note
Any deletion or addition of a ticket is recorded in the histor y.
For g roups, this tab allows to list as well sub-g roups tickets.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

GLPI User Document ation, Ver sion 10.0

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Entities
Entity concept is a key concept in GLPI. Having many similar ities with a hierarchy
or a division inside a compa ny, it
allows on a single instance of GLPI to isolate sets organized in a hierarchical
manner. The chosen ter m is voluntar ily
neutral in order to adapt to many infor mation systems.
A single instance (or installation) of GLPI, when composed of several entities,
allows to consolidate common data and
r ules. Using entities allows to create a rather tight isolation between
organizational units.
#
Indication
When this isolation is not desired, it is better to use the functionalities o˙ered
by GLPI
Groups
.
Segmenting in entities can have several targets :
isolate assets of each division in order to limit assets visibility for g roups or
users

isolate assets of clients

reproduce the existing hierarchy of the director y (LDAP, Active Director y. . .).
Using entities is ver y useful for a company where management is hierarchical and
where employees must have access
to the assets depending on the division they belong to.
One entities creating in GLPI, assets inventor y, users, pro˝les and assistance ser
vice become dependent upon entities :
a computer can be assigned to an entity, a ticket can be declared on an entity,
pro˝les and author izations can be speci˝c
to entities. . . Automatic entity assignment for users and assets are possible
thanks to r ules management.
242
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Example : entities inside a company
EM
|
-
-
-
-
-
-
|
-
-
-
-
-
-
|
EA EB
|
|
|
|
EA1 EA2 EB1 EB2
Mother entity (EM, or named
Root Entity
in GLPI) has two subsidiar ies (EA and EB) which in tur n have two
divisions each (EA1, EA2 for EA, EB1, EB2 for EB). Each entity has access to its
assets and subsidiar y entities :

EM has access to its assets as well as to all assets of all entities

EA has access to its assets as well as to EA1 and EA2 assets

EA1 has only access to its own assets

A user can be attached to several entities with di˙erent author izations in each
entity, these author izations being kept in
daughter entities or not. For example a user will be able to open a ticket only
inside user's division, the ticket applying
only to the items of the same division.
On the contrar y, a user being g ranted larger author izations will be able to view
all items, tickets and other objects, and
this on all entities in which user's author izations apply.
By default, GLPI has a single gener ic entity named
Root Entity
. This entity can be renamed at user's convenience.
Processes may var y depending upon entity ; for this reason entities can have a
delegate administration (author ization
Entities
in pro˝le). This delegation must be g ranted to a ver y limited number of users who
will be in charge of the
complete management of the entity.
When using GLPI in multi-entities mode, management of some con˝guration parameters
can apply in a di˙erent way
in each entity.
The di˙er ent t abs
Entities
This tab lists existing sub-entities and allows to add a sub-entity to cur rent
entity.
Addr ess
This tab g roups administrative infor mation of cur rent entity : address, phone
numbers, email. . .
Advanced information
This tab g roups technical identi˝cation data of the entity, those concer ning
gener ic entity assignment r ules and those
concer ning users search inter face. These data will be used by r ules for
automatic assignment to the entity (hardware
if coupled with an inventor y tool, user or g roup if connected to a LDAP director
y, ticket if enabled ticket creation via
mail collector) as well as for impor t and synchronization of users or iginating
from a LDAP director y.
In order to o˙er to an entity administrator the possibility to impor t users from a
LDAP director y, it is necessar y to
provide some parameters : director y associated with the entity and search ˝lter.
This search ˝lter is meaningful only if
entity de˝nition is done by adding a restr iction on LDAP ˝lter. It is also
possible to de˝ne the email domain speci˝c
to the entity which can be used to assign users to this entity.
Three options are available for gener ic entity assignment r ules : the
TAG
coming from inventor y tool, the LDAP infor-
mation representing the entity (for example the
DN
of the entity) and the email domain associated with the entity.
3.2. Modules
243

GLPI User Document ation, Ver sion 10.0

N oti˝cations
Noti˝cation setting is done at entity level. This tab g roups two tables :

global options for all GLPI noti˝cations : administrator email (will be the
From:
for all GLPI issued emails),
administrator name, pre˝x for noti˝cation email subject (
GLPI
by default), response email address (see con˝-
guration of email follow-ups) and email signature.
For each entity, the delay applied before sending noti˝cation can be de˝ned. This
delay allows for instance in
case of fast multiples modi˝cations of a ticket to send only one noti˝cation email.
The email followup of an
actor can also be de˝ned to Yes or No.

tr igger ing options of aler ts for car tr idges, consumables, contracts,

accounting infor mation, licenses, reser vations
and tickets.
.
Avertissement
Each aler t option is associated with an automatic action. If action is disable by
GLPI administrator, no
noti˝cation will be sent.
If re˝ning noti˝cation at entity level is not desired, these parameters can be
de˝ned once at root entity level ; each entity
will then by default get the values de˝ned at parent entity level.
Assist ance
This tab is visible if
Read or Modify Entity Parameters
author ization is g ranted in pro˝le. The tab g roups entity para-
meters applicable to tickets :

Ticket Template
: selected template will be used for each ticket creation ;

Calendar
: entity default calendar for computing tickets resolution time and target date
shift ; this calendar will
be pre-selected when creating a SLA ;

Ticket Default Type

: prede˝ned type for ticket creation ; useful for ticket creation via email
collector ;

Automatic Ticket Assignment

: allows to assign automatically a ticket ; *
based on item then on categor y
: if
ticket has an associated item and this item has a technical manager or g roup, it
will be assigned to this technician
and/or g roup ; other wise if ticket has a de˝ned categor y, it will be assigned to
the technical manager or g roup of
the categor y *
based on categor y then on item
: if ticket has a de˝ned categor y and this categor y has a te chnical
manager or g roup, it will be assigned to this technical manager or g roup ; other
wise if ticket has an associated
item, it will be assigned to this technician and/or g roup of the item

Automatic Closure of Solved Ticket After

: allows to per for m a so-called # administrative # closure ; if closure
is set to
immediately
, ticket will be closed as soon as it is solved, which will block solution approval
by requester.
This closure is per for med by an automatic action which must therefore be active

Satisfaction Survey Con˝guration

: this sur vey can be inter nal (GLPI satisfaction for m) or delegated to a third-
par ty tool. For each entity, the sur vey date can be de˝ned (delay after ticket
closure) as well as to be generated
sur vey rate. In order to avoid that old tickets are taken into account when
activating sur vey, a ˝eld
For Tickets
Closed Af ter
contains the activation date to know which tickets must be taken into account.
Indeed, if sur vey
are reactivated after a deactivation time, this ˝eld must be set to exclude old
tickets. For exter nal sur vey, the
URL of the sur vey can be generated automatically using tags de˝ned below.
List of available t ags for survey URL :

[TICKET_ID]
: ticket id

[TICKET_NAME]
: ticket name

[TICKET_CREATEDATE]
: ticket creation date

[TICKET_SOLVEDATE]
: ticket resolution date

[REQUESTTYPE_ID]
: request source id

[REQUESTTYPE_NAME]
: request source name (phone, help desk. . .)

[ITEMTYPE]
: type of item associated to the ticket (computer, pr inter. . .)
244
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

[ITEM_ID]
: id of item associated to the ticket

[ITEM_NAME]
: name of item associated to the ticket

[TICKET_PRIORITY]
: ticket pr ior ity

[TICKETCATEGORY_ID]
: ticket categor y id

[TICKETCATEGORY_NAME]
: ticket categor y name

[TICKETTYPE_ID]
: ticket type

[TICKETTYPE_NAME]
: ticket type name (incident management or ser vice request)

[SOLUTIONTYPE_ID]
: solution type id

[SOLUTIONTYPE_NAME]
: solution name

[SLA_ID]
: id of SLA associated to the ticket

[SLA_NAME]
: name of SLA associated to the ticket

[SLALEVEL_ID]
: id of SLA level

[SLALEVEL_NAME]
: name of SLA level
Assets
This tab allows to con˝gure the di˙erent dates present in adm inistrative and
˝nancial infor mation and some other
entity-level asset options. The possible automatic actions are :

˝lling when item gets a par ticular status ;

˝lling by copying another date ;

no automatic ˝lling
The option
Sof tware creation entity
allows to redirect software creation to another entity at a higher level in the
hierarchy.
This functionality applies on
all
software of the entity ; if redirection must be de˝ned only for some software, the
sof tware dictionar y
must be used.

Model for automatic entity transfer on inventories

GLPI also allows to transfer a computer in another entity
if one of the cr iter ia used for the assignment to an entity is modi˝ed. If the
option Model for the automatic
transfer of computers in another entity indicates an existing model, then each time
a computer is updated from
the inventor y tool, the entity assignment r ules engine will be replayed. If the
resulting entity is di˙erent from
the cur rent entity, the computer will be transfer red to the new entity.
ò
Note
This con˝guration option is not present if you have only one entity in your
instance.
User s
This tab allows to add a user to the cur rent entity and to assign to the user a
pro˝le, recursive or not. The tab lists also,
sor ted by pro˝le, the entity users.
Rules
This tab allows to create r ules :

for author izations g ranting to users ;

for assignment of tickets opened by email ; if the r ule must be based on cr iter
ia, the newly created r ule must be
opened to de˝ne these cr iter ia. Rules already applicable to the cur rent entity
are also displayed.
3.2. Modules
245

GLPI User Document ation, Ver sion 10.0

Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
N otes
The
Notes
tab provides a free text ˝eld for stor ing additional infor mation. Notes are
displayed in the order of their
creation.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

246
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

management r ules :

assigning an asset to an entity

g ranting per missions to a user

assigning categor y to a software

routing tickets to entities

automatic actions when opening ticket

data dictionaries
:

manufacturers

software

pr inters

types of assets

models of assets

operating system related ˝elds

The engine behaves di˙erently depending on the types of r ules :

stop after ˝rst matching r ule

apply all r ules

apply r ules and pass r ule result to next r ule

Rules can be disabled, for example when wr iting and testing new r ules.
#
Indication
3.2. Modules
247

GLPI User Document ation, Ver sion 10.0

in general, it is recommended to test the r ules well before using them and to make
a back up before setting up each
new r ule. On the main for m of a r ule, a
Test
button opens an additional window that allows to see all the cr iter ia
and results of the r ule.
The di˙er ent rules
Rules for assigning a tic ket opened via a mail collector
See
Rules for assigning a ticket opened via a mail collector
Rules for assigning authorizations to a user
See Rules for assigning author izations to a user
Rules for assigning a categor y to sof twar e
Classi˝cation by categor y makes it easier to display and ˝nd software. This can be
done automatically for any new
software, or retroactively. The available c r ite r ia are the publisher, the name
and the comment of the software. The only
possible action is to assign software to a categor y. It is possible to replay the
r ules from the software list, using massive
action
Recalculate categor y
.
Business rules for tic kets
When opening or modifying a ticket, a mechanism allows to modify ticket attr ibutes
automatically.
See Business r ules for tickets
Rules for inventor y ag ent
The two menus below are only visible if you use an inventor y agent for an
automatic inventor y of computers in GLPI.

r ules for assigning an item to an entity

r ules for impor ting and linking computers

See Rules for inventor y agent

Transfer
This menu allows you to de˝ne the inter-entity transfer pro˝les.
Several actions are possible :

Preserve
: the item will be transfer red with the object ;

Put in Trash Bin

: the item will be placed in the recycle bin of the ceding entity ;

Delete Permanently
: the item will be deleted from the database ;

Keep
: the item will remain in the ceding entity ;

Disconnect
: the connection between element and object will be deleted

Blacklists
Thanks to the GLPI blacklist mechanism, it is possible to exclude cer tain values
from processing by
the r ules engine. The types that can be taken into account are :

IP address ;

MAC address ;

ser ial number ;

UUID ;

email
This allows, for example, to exclude cer tain IP addresses from the inventor y
agent (for example an IP 127.0.0.1
or 0.0.0.0) or not to create a ticket from a par ticular email address (for example
daily back up of a ser ver).
248
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Cr eate a rule
A r ule is composed of a ser ies of cr iter ia. Depending on the option chosen (OR/
ND) one or all of the cr iter ia must be
ver i˝ed to tr igger an action list.
A preview mechanism allows you to test the r ules being wr itten before putting
them into production.
Several cr iter ia are available :

simple :

is not

contains

does not contain

star ts with

ends with

under (for tree dropdowns, indicates to be this dropdown or one of the child
dropdowns)

not under (for tree dropdowns, indicates not to be this dropdown or one of the
child dropdowns))

complex :

regular expression match

regular expression does not match

Regular expressions (other wise known as regex) retur n one or more results which
can then be used by actions using
the #x directive (where x is the number of the result of the regular expression).
Example
Cr iter ia : name matching regular expression
/DESKTOP\_(.\*)/
If object is named
DESKTOP_0001
, then it will
be possible to use
0001
in the actions of the r ules using parameter
#0
Dictionaries
Dictionar y's allow to modify data already existing in GLPI or new data in order to
g roup redundant data.
Dictionar ies are based on GLPI
r ules engine
and are available for some types of items (software, suppliers, drop-
downs). The r ules associated with a dictionar y will modify values that are either
manually inser ted or automatically
inser ted via an inventor y tool or via plugins (for instance CSV ˝le injector).
Im por t, expor t and duplication
Expor t, impor t and duplication are available for dictionar ys or r ules. These
operations can be realized globally from
dictionar y's main page or by batch using mass actions from dictionar y's search
results. These functionalities are useful
for instance when mig rating r ules from a pre-production environment to a
production one.
ò
Note
expor t or impor t use a XML ˝le for mat
Con˝gur e dat a dictionaries
A dictionar y works the following way :
1.
data to be added enters the dictionar y ;
2.
r ules engine plays all r ules applying to this type of data and stops on ˝rst
matching r ule ;
3.
modi˝ed data is retur ned by the dictionar y and inser ted into database.
3.2. Modules
249

GLPI User Document ation, Ver sion 10.0

The
Replay the dictionar y r ules
button (under the list of r ules of the dictionar y) allows to replay the r ules on
data
already existing in database.
.
Avertissement
if database is big, the parameter
memor y_limit
in PHP con˝guration ˝le must be carefully adjusted : processing by
a dictionar y can be heavy.
#
Indication

it is highly recommended to play r ules on a test database and to back up database

before production launch
of the dictionar y or before inser ting new r ules

a scr ipt is available in director y

scripts
of GLPI installation, named
compute_dictionnar y.php
, that allows
to launch dictionnar y processing in command line mode ; this allows to bypass
problems of execution limit
and provides a signi˝cant speedup
Global dictionaries
Sof twar e
The software dictionar y modi˝e s software data (name, version, manufacturer) in
order to complete or merge software's.
It is used to make more coherent equivalent software for which name is not
identical (for example Mozilla Firefox 3.0
and Mozilla Firefox 3.6) or to add a manufacturer if it is not present.
This dictionar y allows also to redirect the creation of a software or of a set of
software in a given entity, by choosing
action
Entity
and to select the entity in which to create the software. This functionality can
also be used with general
option
Entity for sof tware
available in entity con˝guration.
ò
Note
for an optimal management of software and licenses in a multi-entity environment,
it is possible to use the software
dictionnar y simultaneously with software visible in sub-entities and thus to use g
rouping functionality.
.
Avertissement
using action
Add regexp result
on a version must be used with maximum care ; indeed, this action is only taken
into
account when impor ting data coming from an inventor y tool and will be ignored
when re-applying dictionar y on
an existing database.
As an example, following image descr ibes g rouping Mozilla software. Cr iter ia
are accumulated with AND.
The following image descr ibes associated action for g rouping Mozilla software.
The following image presents result of g rouping Mozilla software : software are g
rouped by type (Mozilla Thunderbird,
Mozilla Firefox. . .) and versions are g rouped by type.
Example for Windows updates grouping, very unclear !
Autre exemple pour reg rouper les mises à jour Windows. Cette fois le cr itères
sont des OU et non des ET
Cri-
250
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Fig. 2
# Cr iter ia for g rouping Mozilla software
Fig. 3
# Action for g rouping Mozilla software
Fig. 4
# Result of g rouping Mozilla software
3.2. Modules
251
GLPI User Document ation, Ver sion 10.0
tères
Logiciel expression rationnelle vér i˝e /Cor rectif.*XP.*KB([0-9]*)/ Logicel
expression rationnelle vér i˝e
/Mise.*XP.*KB([0-9]*)/ Logiciel expression rationnelle vér i˝e /Update.*XP.*KB([0-
9]*)/
Actions
Logiciel assi-
gner Mise à jour Windows Version assigner valeur depuis regex #0
Manufactur er
This dictionar y allows to g roup under a unique name th e manufacturer names
coming from an inventor y tool under
di˙erent for ms.
Exemple for manufacturer grouping, unclear !
reg rouper les fabr icants . Sun_Microsystems . Sun Microsystems, Inc. for the
OpenO˚ce.org-Community . Sun
Microsystems, Inc. . Sun Microsystems, Inc sous le nom Sun Microsystems.
Printer s
This dictionar y allows to modify pr inter infor mation based on manufacturer
and/or name. It is possible to reject an
impor t (for example pr inter name star ting with
//
), to g roup pr inters under same name, to assign a manufacturer or to
force management type (global or unitar y).
Drop-downs
This dictionar y allows to modify drop-downs related to inventor y : types and
models of items, operating system, version
and ser vice pack.
Models
Possible cr iter ia are manufacturer and item model.
Example : transforming technical number into commercial model name
Often inventor y tools extract model technical number, which is ir relevant for
user. This example allows to extract
commercial model name while keeping technical number which can be required in case
of requesting a provider
inter vention.
Fig. 5
# Example of dictionar y for computer model : r ule
Fig. 6
# Example of dictionar y for computer model : action
The obtained result will be for instance : Netvista S42 (8319LGV)
252
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Types
Only possible cr iter ia is item type.
Example : harmonizing peripheral names
Fig. 7
# Example of dictionar y on per ipheral type : r ule
Fig. 8
# Example of dictionar y on per ipheral type : action
The obtained result will be for instance : Keyboard
Oper ating systems
Depending on chosen dictionar y, the cr iter ia will be based on operating system
itself, on operating system ser vice pack
or on operating system version.
User pro˝les
Pro˝le is central in GLPI con˝guration : pro˝le is the key for users per missions g
ranting and for secur ing and isolating
data.
A pro˝le is associated with :

a user

an entity, in a
recursive
or
dynamic
manner
In order to enable per missions to be passed to child entities, the pro˝le must be
associated recursively.
v
À faire
old version : Pour répercuter les droits liés à ce pro˝l, à toutes les entités
˝lles de l'entité enregistrée, il faut associer
le pro˝l de manière récursive. C'est là tout le pr incipe de la récursivité.
Di˙erent pro˝les can be associated with the same user, based on entities and
whatever the relation between these
entities : this can be achieved by adding the pro˝le to the user for each entity
where user pro˝le must be di˙erent.
By default, 7 pro˝les are pre-registered in GLPI :

Super-Admin
: This pro˝le is g ranted
all
per missions ! .. war ning : : if the super-admin pro˝le is deleted or if
the
simpli˝ed inter face
is associated with this pro˝le, access to the GLPI con˝guration may be per manently
lost.
3.2. Modules
253

GLPI User Document ation, Ver sion 10.0

Admin
: This pro˝le has administration r ights for all GLPI. Some restr ictions are
applied to it at the level of
the con˝guration of r ules, entities as well as other items which may alter the
behavior of GLPI.

Supervisor
: This pro˝le incor porates the elements of the
Technician
pro˝le by adding elements allowing
management of a team and its organization (allocation of tickets, etc.).

Technician
: This pro˝le cor responds to the one used for a maintenance technician, having
read access to the
inventor y and to the help desk in order to process tickets.

Hotliner
: This pro˝le cor responds to the one that could be given for a hotline ser vice ;
it allows to open tickets
and follow them but not to be in charge of them as a
Technician
can be.

Observer
: This pro˝le has read per mission to all inventor y and management data. In ter ms
of assistance, it
can open a ticket or be assigned one, but cannot administer this section (assign a
ticket, steal a ticket. . .).

Self-Service
: This pro˝le is the most limited. It is also the only one to have a di˙erent inter
face, the
simpli˝ed
inter face
, as opposed to the
st andard inter face
. However, it can declare a ticket, add a follow-up, consult the
FAQ or reser ve asset. This pro˝le is set as the default pro˝le.
Permissions description
Once the pro˝le has been created, it will be possible to establish the per missions
on the var ious functionalities of GLPI.
Seven tabs cor responding to the di˙erent menus of GLPI are then available to
manage this set of per missions and are
descr ibed below.
The di˙erent per missions of an object are listed on the line of its name. To
activate an per mission, the cor responding
box must be checked and vice versa to delete an per mission the box must be
unchecked.
.
Avertissement
no per mission deduction is done ; for example in order to be able to modify an
object, read per mission must also
be g ranted.
Per missions after mig ration : mig ration takes over old per missions in full,
regardless of the pur pose, and activates the
cor responding values in the new system. Previous
Write
per mission is transfor med into
Read
,
Update
,
Create
,
Delete
and
Purge
for most objects and must then be re˝ned if needed. For others, the per missions
are g rouped by object, for
example, FAQ per mission are per missions of the Knowledge Base object.
Some per missions are standards for all objects :

Read
: allows to display an object, it is also often this per mission which displays or
not the object in the di˙erent
menus

Update
: allows to display an object data
Create
: allows to create a new element of the type of the object

Delete
: allows you to place the object in the trash bin. If this per mission is not
present, it means that the object
does not have a trash bin.

Purge
: deletes the object from the trash bin and therefore per manently from the
database. The per missions can
therefore be re˝ned between temporar y deletion (placing in the trash bin) and per
manent deletion (purging the
trash bin)

Read notes
: allows to display the
Notes
tab, if object has one

Update notes
: allows to modify the content of a note or to delete it
The di˙er ent t abs
ò
Note
the display of pro˝le management depends on the pro˝le of connected user. It can
therefore var y depending on the
pro˝le.
254
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Assets
The 7 standard per missions descr ibed above apply to the elements of tab
Assets
.
Fig. 9
# Per missions on assets
The
Internet
per mission applies to :

IP ˝eld of a network por t

association or disassociation of a network name to a network por t

Inter net par t of dropdowns (IP networks, inter net domains, WiFi networks,
network names)
Assist ance
This tab manages per missions on tickets, follow-ups, tasks, validations, asso
ciations, problems and changes. It also
manages the visibility of statistics and schedules as well as the assignment of a
template to the pro˝le.
See Tab # Assistance #
Life cycle
This tab manages the per missions on the status life cyle of tickets, problems and
changes.
See
Tab # Life cycle #
Manag ement
The 7 standard per missions descr ibed above apply to the elements of tab
Management
.
.
Avertissement
The per missions on
Financial and administrative information
applies also to objects containing ˝nancial infor-
mation ; for instance it is not allowed to purge a computer containing ˝nancial
infor mation if pro˝le is not g ranted
with
Purge
per mission on ˝nancial infor mation.
3.2. Modules
255

GLPI User Document ation, Ver sion 10.0

Fig. 10
# Per missions on management
Tools
This tab manages per missions on notes, RSS feeds, public bookmarks, repor ts,
reser vations, knowledge base as well
as projects and tasks of a project.
See Tab # Tools #
Administr ation
This tab manages per missions on users, entities and business r ules on tickets.
See Tab # Administration #
Con˝gur ation
See Tab # Con˝guration #
User s
This tab lists the entities in which this pro˝le is assigned. To see the cor
responding users, click on the concer ned entity.
# D #
means the per missions have been assigned dynamically,
# R #
means the per missions are recursive from the
assignment entity.
Historical
See Tab # Histor ical #
All
See Tab # All #
256
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Mailing q ueue
All noti˝cation emails go through a queue before actual deliver y. This allows
keeping a histor y and a list of the var ious
emails sent.
An automatic action (
queuedmail
) allows the sending of pending emails (see
Con˝gure automatic actions
). Another
automatic action (
queuemailclean
) cleans the queue by keeping only recent emails.
The delay applied for sending noti˝cations can be de˝ned at entity level, see
administration by entity
). This allows for
example in the case of rapid multiple modi˝cations of an object to send only one
noti˝cation.
.
Avertissement
using the queue does not work for a change, problem or ticket itself, only for a
sub-object. For example, when
changing the impact of a ticket, the email will be sent immediately ; on the other
hand, in the event of addition or
modi˝cation of a follow-up, a task, a validation request. . . the email will be
placed in the queue.
Fig. 11
# Example of queue
In the example above, the deadline for sending email noti˝cations has been set to
20 minutes in the con˝guration of
the entity ; as a consequence the sending date is set at 20 minutes after the
creation date.
Once the noti˝cation has been sent, the queue is placed in the recycle bin with the
date sent.
ò
Note
there will be as many queues in the recycle bin as there are recipients, each with
its own sending date.
3.2. Modules
257

GLPI User Document ation, Ver sion 10.0

Logs
This menu allows to display and sor t logs.
The logs page displays type of modi˝ed infor mation (computer, reser vation,
ticket. . .), the modi˝cation date, GLPI
ser vice (inventor y, con˝guration, tickets. . .) and a message detailing the
event.
ò
Note

Log level can be parameter ized in ˝eld

Log Level
of tab
System
of general con˝guration.

Log retention per iod can be parameter ized in automatic actions.

3.2.7
Con˝gur ation
Con˝guration module gives access to all GLPI con˝guration options such as : -
Global con˝guration - Noti˝cations -
Receivers - Automatic actions - Authentication - Plugins - Unicity cr iter ia -
Exter nal links
Authentication
This is where GLPI manages the authentication and infor mation of users.
GLPI uses its own inter nal database of users. These are either created in GLPI
itself or impor ted from one or more
exter nal sources. Depending on the type of source, the impor t can be done in bulk
or at the time of login if the user is
not yet known to GLPI but exists in an exter nal authentication ser ver with
matching credentials.
The general authentication con˝guration and the management of exter nal
authentication ser vers can be done in the
Setup > Authentication menu
.
The attr ibution of author izations is descr ibed in the Rules for assigning author
izations to a user documentation.
ò
Note
The authentication process is as follows :
1.
A user enters their login and password in GLPI
2.
GLPI checks if the user is already registered in its database and if not :
258
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

1.
GLPI tr ies the con˝gured methods of authentication one after another (Inter nal >
LDAP > IMAP >
Other)
2.
When the authentication is successful, the user is created in the GLPI database
and the method of au-
thentication is stored with it
3.
If no method of au thentication is able to authenticate the user, they are shown
an er ror indicating that
their user name or password is incor rect
3.
If the user already existed in the GLPI database or was impor ted in the previous
step :
1.
GLPI tr ies authenticating the user only with the last source that was able to
successfully authenticate
them
2.
If the authentication fails, they are shown an er ror indicating that their user
name or password is incor rect
4.
The author ization engine is launched with the user's infor mation :
1.
If the engine has g ranted one or more author izations to the user, then that user
has access to GLPI
2.
If the user is not g ranted any author izations, then the user will be known to
GLPI but will not be able to
login
In ord er to use an exter nal source of authentication you may need to enable the
relevant PHP extension(s). For example,
LDAP sources will require the
php-ldap
extension.
There is no limit to the number of authentication sources that can be con˝gured.
To allow GLPI to create users automatically from exter nal authentication sources
as they tr y to log in, it must be enabled
in the
Setup > Authentication > Setup
for m. When using LDAP director ies, it is possible to con˝gure the action that
GLPI takes when a user is no longer present in the LDAP director y from this same
for m.
Con˝gur e external authentication
This menu allows you to con˝gure the general settings for integ ration with exter
nal authentication sources.
In order to be able to use these exter nal authentication sources, the cor
responding extensions must ˝rst be activated in
the PHP con˝guration. There is no limit to the number of exter nal sources
con˝gured in the application.
To use the capacity of GLPI to create on the ˛y users present in the exter nal
sources of authentication, it is necessar y
to activate it in the menu Con˝guration > Authentication > Con˝guration.
The LDAP director ies also allow you to refuse the creation of users who do not
have author izations. Deleting a user
from the director y can also lead to an action such as trashing the user, deleting
his per missions or deactivating him.
You also have the option to specify how to handle users that were previously
deleted from the director y but are now
restored. You can set the restore action to do nothing, restore the user from the
trashbin, or re-enable the user.
It is also at this level that the time zone of GLPI is set.
Exter nal authentication sources that can be used inside GLPI are :

LDAP directories
3.2. Modules
259

GLPI User Document ation, Ver sion 10.0

Email ser vers

CAS ser ver

x509 cer ti˝cate

Delegate authentication to web ser ver

LDAP dir ectories
GLPI can inter face with one or more
LDAP directories
in order to authenticate users, control their access, retr ieve their
personal infor mation and impor t g roups.
All the director ies compatible LDAP v3 are suppor ted by GLPI. It is thus also the
case for the #
Active Director y
of
Microsoft. There is no limit as to the number of director ies infor med. However,
the higher the number, the longer the
search for a new user to authenticate can be.
It is possible to impor t and synchronize users in 2 ways :

At the ˝rst login, the user is created in GLPI. At each login, his personal infor
mation is synchronized with the
director y. In the case where the receivers are used and there is an email not
associated with an existing user, the
unknown email address will be searched in the director y to create the associated
user.

In mass either via the web inter face or the CLI

glpi :ldap :synchronize_users
command.
.
Avertissement
If no LDAP con˝guration is visible (see an er ror message on this par t) it means
that the LDAP module for PHP is
not installed.
Under Linux, install the ldap package for PHP (for example
php7.4-ldap
on Debian), then restar t the web ser ver.
Under Windows it is necessar y to uncomment in the ˝le
php.ini
(˝le present in the director y
apache/bin
) the line
extension=php_ldap.dll
then restar t the Web ser ver.
The process of authentication of the users is divided into 3 par ts :
authentication, access control and ˝nally the recover y
of the personal data.
LDAP Authentication
At the time of the ˝rst login of the user, GLPI will search all of the con˝gured
director ies until ˝nding one that contains
the user. If the option allowing to impor t users from an exter nal source is
active, then the user is created and the identi˝er
of the method of connection and the LDAP ser ver are stored in database.
Then, at each login the user is authenticated on the director y whose identi˝er is
stored in GLPI. The other director ies
are not used ; If a user is deactivated in the director y which it used until then
to connect, it cannot connect with another
source of authentication.
Access Control
Access control is the assignment of per missions to a user. Even if a user is
authenticated on a director y it is not neces-
sar ily entitled to connect to GLPI.
This mechanism is based on the use of Author ization Assignment Rules.
The di˙er ent t abs
260
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

LDAP dir ector y
ò
Note
There is an Active Director y pre-con˝guration template, which pre-˝lls a cer tain
number of ˝elds.
To load it, click on the
Active Directory
link when adding a director y. The
Default value(s)
link will reset the
values to the default.

Default server
: If you have multiple LDAP ser vers set up, you can only de˝ne one default ser
ver. Choosing
this setting will remove it from the ser ver it was previously set to.

Server and Port : Represent the address and port of the LDAP directory.
GLPI can connect to an LDAP director y through an LDAPS connection. To enable this,
pre˝x your ser ver
˝eld with
ldaps ://
and change the por t to the LDAPS one of your LDAP director y (default 636).

Connection ˝lter
: Allows you to restr ict the search for users in the director y. For example, if
only a restr icted
set of users have the r ight to connect to GLPI, you can create a condition to
restr ict the search to that set of
users.
Some example ˝lters :

A classic LDAP ˝lter :

(objectclass=inetOrgPerson)

An Active Director y ˝lter to retur n only enabled users :

(&(objectClass=user)(objectCategory=person)(!(userAccountControl:1.2.840.
113556.1.4.803:=2)))
The example Active Director y ˝lter is automatically populated when the Active
Director y pre-
con˝guration template is selected.

BaseDN
: The location in the director y from which the searches will be made.

RootDN
: The distinguished name of the user ac count to authenticate to LDAP with when not
using anonymouse
binds.
ò
Note
RootDN and BaseDN are case sensitive and must not contain spaces betwen the par ts.
Examples :

cn=Admin, ou=users, dc=mycompany

: incor rect
3.2. Modules
261

GLPI User Document ation, Ver sion 10.0

cn=Admin,ou=users,dc=mycompany
: cor rect

Password
: The password for the account speci˝ed (if any) in the RootDN ˝eld.

Login ˝eld
: The name of the ˝eld in the LDAP director y cor responding to the user's login
(Ex :
uid
in LDAP
or
samaccountname
in Active Director y).

Synchronization ˝eld
: The name of the ˝eld in the LDAP director y used for Synchronization. This ˝eld
must
be unique for ever y user (Ex :
employeeuid
in LDAP or
objectguid
in Active Director y).
The parameters to enter are simple. For example :

Ser ver :
ldap.mycompany.fr

BaseDN :
dc=mycompany,dc=fr
This should be enough if anonymous binds are allowed. If not, and if all users are
not located within the same DN, you
have to specify the DN of an author ized user and his password through the
RootDN/Password parameters. For Active
Director y, it is required to specify an account that has the r ight to
authenticate on the domain.
ò
Note
If some of the users have connection restr ictions to cer tain machines con˝gured
in their Active Director y pro˝le,
a user not found er ror may be seen. The solution is to add the Active Director y
ser ver to the list of computers the
user is allowed to connect to.
.
Avertissement
Do not forget to activate your director y and set it as the default (if wanted) if
you have multiple director ies.
Test
Allows the testing of the con˝guration de˝ned in the LDAP director y tab.
The message
Connection test successful
indicates that GLPI was able to connect to the LDAP director y with the
infor mation provided (host, por t, user account).
It remains now to impor t the users. For that, it is necessar y to check the other
parameters (connection ˝lter, login ˝eld,
etc).
User s
Allows you to con˝gure how the link between the ˝elds of the director y and those
of GLPI will be made. Most of the
˝elds are automatically mapped for you but can still be changed.
262
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Groups
Allows you to con˝gure the method for retreiving g roups from the LDAP director y.
Advanced Information
In case the ser ver hosting the LDAP director y is in a di˙erent timezone as GLPI,
it is necessar y to modify the
Timezone
var iable to account for the di˙erence.
Limit of the number of records returned
There are often two limits on the number of records retured per request.

The client limit (de˝ned for example on Debian/Ubuntu in

/etc/ldap/ldap.conf
)

The ser ver limit : If the ser ver limit is lower than the client limit, then that
is the e˙ective limit
.
Avertissement
If the limit is reached, the optional GLPI behavior for LDAP user deletion can not
work. Moreover, GLPI will
display a war ning message dur ing the impor t or synchronization.
It is possible to bypass the limitation by enabling
Pagination of results
in the
Advanced Information
tab of the LDAP
director y in GLPI. This will split requests into smaller requests that are under
the con˝gured limit.
3.2. Modules
263

GLPI User Document ation, Ver sion 10.0

The
Page size
option adjusts the number of results retreived per # page # with pagination
enabled. The
Maximum
number of results
option is the limit for the total number of records. This option may be useful to
avoid high memor y
usage.
ò
Note
On an OpenLDAP director y, the default limit is 500 and in Active Director y, it is
1000.
In Active Director y it is possible to modify the value of
MaxPageSize
with the following commands (This modi˝-
cation is global for the whole director y) :
C:> ntdsutil
ntdsutil: ldap policies
ldap policy: connections
server connections: connect to server 192.168.1.1 ( here a few messages regarding

,
!
connectivity are displayed)
server connections : q
ldap policy : show values ( here we will see all the values including MaxPageSize

,
!
which is 1000 currently)
ldap policy : set maxpagesize to 5000
ldap policy : commit changes
ldap policy : q
ntdsutil : q
Replicates
If an LDAP director y is not accessible, the users provided by it will not be able
to connect to GLPI.
To help avoid this situation, replicates can be declared in GLPI. These are LDAP
ser vers that have the same data as the
main ser ver, but are available at a di˙erent address.
Replicates are only used when the connection to the main ser ver is lost. The
additio n of replicates in GLPI is done
by enter ing a
Name
which is displayed in GLPI, as well as a
Server
,
Port
, and
Timeout
in the
Replicates
tab in the
LDAP director y. To enable LDAPS, pre˝x your ser ver entr y with
ldaps ://
and change the por t to the LDAPS one of
your LDAP director y (default 636). There is no limit to the number of replicates
per LDAP director y.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
The di˙er ent actions
See the
common actions
.
Authenticate from IMAP
The inter facing of GLPI with mail ser vers as a source of authentication.
This authentication source is con˝gured from the menu
Setup > Authentication > Mail ser vers
.
This ability can compensate for the absence of director y or of CAS ser ver.
However, contrar y to what is possible with
other sources of other authentication sources, no mass impor t is available. A user
is authenticated by GLPI if the ser ver
of mail ser ver has authenticated him beforehand.
The connection to the mail ser ver uses the IMAP or POP protocols. The options of
SSL and TLS encr yption are
available. The distinction is made between the mail domain which is the par t of
the of the mail address that follows the
aster isk character, and the fully quali˝ed name of the mail ser ver, which can ser
ve several mail domains.
Other external authentication methods
The integ ration of GLPI and authentication sources beyond inter nal, LDAP, and
IMAP is con˝gured from the
Setup >
Authentication > Other authentication methods
menu.
Centr al Authentication Ser vice (CAS)
The con˝guration of a CAS ser ver is compr ised on the address of the ser ver and
its por t (default 443). A base director y
can be speci˝ed if needed. The retur n web address parameter allows you to redirect
the user to a speci˝c page after
they log out from GLPI.
.
Avertissement
Once the CAS authentication is activated, each authentication is automatically
redirected to the CAS ser ver. In order
to log into an inter nal account or one authenticated through a di˙erent method,
you have to add # ?noAUTO=1 # to
the login URL.
ò
Note
The
php-curl
or
php-dom
extensions are required to be enabled for CAS authentication to function.
x509 cer ti˝cate
The
Email attribute for x509 authentication
tells GLPI to look at the value of this attr ibute in the
SSL_CLIENT_S_DN HTTP request var iable passed by the authentication system.
It is possible to restr ict the accepted values for the O, OR, and CN ˝elds of the
client cer ti˝cate. In order to specify
multiple values for each ˝eld, you may separate each value with the
$
symbol.
3.2. Modules
265

GLPI User Document ation, Ver sion 10.0

Other automatic authentications
GLPI can rely on other exter nal systems to authenticate users such as :
Basic Apache authentication

Windows domain authentication

Authentication coming from an authentication ser ver like LemonLDAP : :NG,

Shibboleth, etc
When the user wishes to reach GLPI, this one checks the presence of a var iable in
the HTTP headers stor ing the
login/user name. If the var iable is present, the authentication is allowed to be
done. We can map the
data transmitted
by the authentication system
with the
˝elds of the user account of GLPI
(name, ˝rst name, email, language. . .). To
˝nish, the controls of author izations are car r ied out. An option allows to
remove the domain of the user's login (Ex :
[email protected]
> testuser).
ò
Note
The list of possible names for the headers is con˝gurable, although the most common
ones are already provided by
GLPI. See
Con˝gur ing headings
.
Dropdowns
Some dropdown lists can be con˝gured in GLPI including but not limited to :

Locations

Status of items

Ticket categor ies

Software names

Manufacturers
Some of the dropdowns have some default values added dur ing the installation of
GLPI when they may bene˝t many
users. For example, GLPI de˝nes multiple ˝les system for mats by default.
The list of dropdown types may var y depending on the user's cur rent pro˝le.
The dropdown options can be translated into multiple languages, however this
feature is disabled by default. It can be
enabled in
Setup > General > General setup
. This will add a new tab in the dropdown for m to manage the translations.
Some of the dropdowns are simple, ˛at lists while others can be organized into a
tree str ucture by de˝ning their parent
option.
All dropdown options can be given a comment that will show in other GLPI for ms by
hover ing over the
Help
icon next
to the dropdown.
The types of dropdowns that can be associated with speci˝c entities will show a #
stack # icon (Same as the Entity
menu item).
Common
Locations
The list of locations is organized into a tree str ucture. Each location can have
sub-locations (Location 1 > Sub-location
1 > Sub-sub-location 1). It can be delegated by entity.
In the record of a location, there is some infor mation about it including :

The parent location

Building number

Room number

GPS coordinates (longitude, latitude, altitude)

Street address
If you allow GLPI to use your location, the map displayed when creating a new
location will automatically show your
approximate location to help make assigning GPS coordinates easier.
266
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Locations
Displays a list of locations that are children of the cur rent location and gives
an option to add new child locations.
Items
Displays a list of items that have this location assigned to them. You are able to
˝lter this list by a speci˝c item type
(Computers, Monitors, etc).
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Soc kets
Lists the network sockets assigned to this locatio n and allows to add a new one.
In this case, when selecting a socket on a
network por t of a device, only the available network sockets of the device
location (and child locations) are shown. The
addition can be single via the top par t or multiple via the bottom par t. For
adding multiple sockets, you can pre˝x the
socket number as shown in the screenshot. Another example : consider ing the pre˝x
br u
,
9
and
11
the socket numbers
and
sr v
the su˚x ; the network sockets created will be named :
br u09sr v
,
br u10sr v
and
br u11sr v
.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
St atus of items
The list of statuses is organized into a tree str ucture. Each status can have sub-
locations (Status 1 > Sub-status 1 >
Sub-sub-status 1). It can be delegated by entity.
St atuses of items
Displays a list of statuses that are children of the cur rent status and gives an
option to add new child statuses.
Tr anslation
This tab is reser ved for names and only appears if the translation of dropdown
names has been enabled in the general
con˝guration.
This tab lists all cur rent translations of the dropdown name and allows you to add
new ones.
268
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Manufactur er s
This list is a ˛at list of values valid for all entities.
This dropdown type cannot be translated.
Blac klists
This list is a ˛at list of values valid for all entities.
It includes the value you want to blacklist as well as what type to blacklist (IP,
MAC, ser ial number, UUID or email).
Blacklists are used for automatic impor ts via an inventor y agent or by the
receiver.
This dropdown type cannot be translated.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

Assist ance
Tic ket categories
The list of ticket categor ies is tree-like : each element can have sub-elements.
It can be delegated by entity.
In the for m of a ticket categor y, you can ˝nd some infor mation about this
categor y including but not limited to :
Responsible and technical g roup for the automatic assignment of tickets

Default categor y of the knowledgebase when you want to add a solution of a ticket

Visibility of the categor y depending on the inter face (simpli˝ed/standard) or

object

Ticket template to use for this categor y

Parent categor y
If a template is chosen, it will be assigned to the choice of the categor y and
will therefore over r ide the one that would
have been de˝ned in the entity or via a business r ule.
A link with the categor ies of the knowledge base is possible. If a categor y is
chosen, clicking on the ticket categor y
help in a ticket leads directly to all the ar ticles in the knowledge base for this
categor y.
Tic ket categories
Displays a list of child ticket categor ies and allows adding new ones.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Name

Parent categor y
Task categories
Displays a list of child task categor ies and allows adding new ones.
270
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
Project st ates
This list is a ˛at value list valid for all entities.
It allows to de˝ne the statuses applied to a project as well as its state.
Project types
This list is a list of ˛at values valid for all entities.
It is used to de˝ne the types applied to a project.
Project t ask types
This list is a ˛at value list valid for all entities.
It is used to de˝ne the types of tasks applied to a project.
The common t abs
Tr anslation
This tab is reser ved for names and only appears if the translation of dropdown
names has been enabled in the general
con˝guration.
This tab lists all cur rent translations of the dropdown name and allows you to add
new ones.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Calendar
The calendars used within GLPI are con˝gurable by entity. They are character ized
by per iods of opening as well as
per iods of closing.
These calendars are used in the
SL A
(see Con˝gure SLAs) and the
con˝guration of entities
.
272
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Calendar
Time r ang es
Cor responds to the opening time slots of the entity. You can add as many as
necessar y per day as long as these slots do
not overlap.
Close times
Lists the closing per iods a ssigned to this calendar and allows you to add a new
one ; see
lca con˝guration of closing
periods
.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Close times
The list of closure per iods is a ˛at list of valid values. It can be delegated by
entity.
A closure per iod consists of a name, a per iod and whether this closure is recur r
ing or not.
Concer ning the ˝eld Recur r ing, if it is in Yes it means that the per iod
indicated is valid all the time. In this case GLPI
would not care about the year indicated.
Ver y useful to indicate the holidays recur r ing each year (Chr istmas, Victor y
of 1945, May 1 . . .) or the per iod of closure
of the company (closed ever y year from 1 to 31 August) and especially it avoids
re-enter ing the same dates each year.
Internet Dropdowns
The IP protocol is represented in several for ms :

IP addresses

IP networks

FQDN
A device connects to a network through network por ts.
To a network por t, one or more Network Names are associated (see below).
A Network Name can belong to an Inter net Domain. It can contain one or more IP
addresses (see below) and it can
have several aliases.
An IP address belongs to an IP network (see below).
At the IP protocol level, networks are either in IPv4 or IPv6.
ò
Note
GLPI manages IPv4 and IPv6 di˙erently. The only di˙erences are the for mat of the
addresses and masks.
212.85.137.66
is an IPv4 address, while
2a00 :1450 :4007 :803 : :1012
is an IPv6 address.
GLPI considers IPv4 as a subset of IPv6 through IPv4-mapped IPv6 addresses and
treats them the same.
GLPI uses two representations for the IP addresses (IPv6 ad IPv4) :

The binar y representation allows GLPI to make the analysis of the relations
between networks, addresses and
masks. It is inaccessible to the user.

The textual representation is used for displaying and enter ing data.
3.2. Modules
273

GLPI User Document ation, Ver sion 10.0

IPv4 addresses and masks are represented in their classic for m (e.g.,
212.85.137.66
,
255.255.255.0
). The
repre-
sentation of IPv6 addresses is the canonical notation
(ie :
2001 :db8 :0 :85a3 :0 :0 :ac1f :8001
rather than
2001 :0db8 :0000 :85a3 :0000 :0000 :ac1f :8001
). In this for m, you may omit 1 - 3 leading zeros in each g roup.
IPv6 masks are represented in the for m of the subnetwork pre˝x (ie : number of
bits to 1 in the mask).
IP networks
IP networks allows you to de˝ne the network topology. They g roup together a set of
IP addresses g rouped according to
the topology de˝ned by the network administrators# addressing plan.
They can be nested, and the hierarchy of IP networks depends on the addresses and
masks of these networks as as well
as their associated identities. For example,
192.168.1.0/255.255.255.0
is a sub-network of
192.168.0.0/255.255.254.0
.
.
Avertissement
The hierarchy is managed implicitly and cannot be modi˝ed manually.
A network is composed of at least an address and a mask. A gateway can optionally
be included.
A network is said to be addressable if it is used for inter nal routing of
computers. In other words, its subnet mask and
its gateway are used by all the equipment on the network (if one or more computers
do not have the same infor ma-
tion, this can cause routing problems. . .). Generally a network with a gateway is
addressable because the gateway is
known by all the equipment and it can only belong to one subnet. But an addressable
network does not necessar ily
have a gateway. This is for example the case of pr ivate networks (
192.168.48.0/255.255.255.0
. . .) or the local loop
(
127.0.0.0/255.255.255.0
or
: :1/128
).
VL AN
Displays a list of
VL AN
associated with this IP network and allows adding new ones.
IP addr esses
Lists the IP addresses of this network.
You can sor t this list by IP number by clicking on the IP Addresses link or by
type of equipment by clicking on the Sor t
by Item Type link. In this case, you will have a table by type of element.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Internet domains
N etwork names
Displays a list of network names for the domain.
Wi-Fi networks
TO BE DONE
N etwork names
A network name is the unique identi˝cation of a machine from the Inter net point of
view.
Generally, a device is identi˝ed by one or more par ticular names on the network.
The DNS ser ver will resolve this
name to an IP address. In case both IPv4 and IPv6 are used, this name will retur n
two IP addresses : one in IPv4 and
the other in IPv6. This is why a network name can have several IP addresses.
A network name is composed of a name that cor responds to the
FQDN
label and one or more IP addresses.
The IP network ˝eld appears in order to retr ieve infor mation about the di˙erent
IP networks available . This infor mation
is not kept in the network name because it can have several IP addresses and each
can belong to several IP networks.
ò
Note
When enter ing a network name, the validity of the name as well as that of each IP
address is checked. If one of
these elements is not valid then it is rejected.
To add an IP address to a network name, click on the
plus button
in front of the IP address entr y ˝elds. To remove an
IP address, simply delete the contents of the IP ˝eld you wish to remove.
N etwork alias
Displays a list of aliases for this network and allows adding new ones.
Traditionally, the network name is the one used by DNS for reverse resolution of an
IP address, while the aliases
cor respond to the
CNAME
of the
FQDN
name.
Similarly, the alias name must have a valid
FQDN
label
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

3.2. Modules
275

GLPI User Document ation, Ver sion 10.0

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

The descr iption of the change represents either the di˙erence between the old and
the new value (For example with
location ˝eld : Change HQ to Remote O˚ce A), or the explanation of the action which
was car r ied out (For example :
Uninstallation of a software : # Gimp 2.0 #).
ò
Note
For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Other s
ò
Note
Some plugins can provide additional headings, which are con˝gurable in the same
menu.
Types
Whatever the type, the list is a ˛at list of values valid for all entities.
It allows to de˝ne the name of the tab type and can be translated.
Models
Whatever the model, the list is a list of ˛at values valid for all entities.
It allows to de˝ne the name of the model of the tab and can be translated.
Vir tual machines
Whatever the sub-title (models or vir tualization system, state of vir tual
machines), the list is a ˛at value list valid for
all entities.
It allows you to de˝ne the name of the vir tualization model or system or the name
of the state of the vir tual machines.
Only the state of the vir tual machines can be translated.
Document headings
This list is tree-like : each element can have sub-elements. It is valid for all
entities.
The
Document headings
tab lists the subheadings already created and allows you to add a new one.
276
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Document types
This list is a ˛at list of values valid for all entities.
The application o˙ers a number of types by default, but it is possible to add more
by provid ing the following infor ma-
tion :

the name of the document type

the extension, for example :

.txt
or
.pdf
; the detection of the documents that can be added is based on this
infor mation

the ˝le name for the desired document icon (Place the icon ˝les in the pics/icones
directo r y under the GLPI
installation ˝le tree)

the MIME type if necessar y

the author ization to download this type of ˝le (yes or no)

ò
Note
The type of document can be a regular expression. This allows for example to author
ize to de˝ne a set of documents
FILENAME.XXXXYYY where XXXX is a number and YYYY the date of the cur rent ˝scal
year. In this case the
regular expression could be /[0-9]+/ to indicate any extension composed exclusively
of numbers.
Knowledg e base categories
This list is tree-like : each element can have sub-elements, which facilitates
navigation and search. It can be delegated
by entity.
In the record of a categor y in the knowledge base, in addition to the name of the
categor y, there is infor mation about
the parent categor y (as a child of) and whether the categor y can be visible to
sub entities.
The
Knowledge Base Categories
tab lists the sub-categor ies already created and allows you to add a new one.
Oper ating systems
Whatever the sub-title, the list is a ˛at list of values valid for all entities.
Only the update sources can be translated.
N etworks
All lists in this par t are ˛at value lists.
Network inter faces, ˝r mware and networks are valid for all entities.
Network sockets, domains and VLANs can be delegated per entity with or without sub-
entity visibility.
Sof twar e categories
This list is tree-like : each element can have sub-elements. The values are de˝ned
for all entities
The
Sof tware categories
tab lists the subcategor ies and allows you to add a new one.
User titles
The lists in this par t are ˛at lists of values valid for all entities.
3.2. Modules
277

GLPI User Document ation, Ver sion 10.0

LDAP criteria
This list is a list of ˛at values valid for all entities.
It is also possible to add a par ticular LDAP cr iter ion.
Ignor ed values for the unicity
This list is a list of ˛at values which can be delegated by entity and applicable
or not to the sub-entity.
It is possible to indicate, for each type of object, values that must not be taken
into account when checking the uniqueness
of an object in the database.
For example not to use the gener ic ser ial number # To Be Filled By OEM # to check
if a computer already exists in
GLPI.
Fields stor ag e of the login in the HTTP r eq uest
The list is a list of ˛at values valid for all entities.
Com ponents
The hardware components that can be added to computers are con˝gurable.
A hardware component is de˝ned by a type, a name, a manufacturer, a comment, and
several ˝elds speci˝c to the type
of component. For example, for a system board, you can enter the chipset.
278
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
It is possible to ˝ll in other component types inside the
Other Components
type. However, it is not possible to add
3.2. Modules
279

GLPI User Document ation, Ver sion 10.0

other types than those listed here.
Once a component type has been selected (
Motherboard
,
Processor
. . .), you are redirected to the list of components
already created.
The di˙er ent t abs
Main
Infor mation that de˝nes a hardware component (di˙erent infor mation depending on
the type of component).
Example for a Processor :
Items
The elements tab allows to visualize the computers linked to the component.
ò
Note

It is possible to modify the characteristics of a component only for the linked

item
From the
Elements
tab of the component, click on the
Update
link.
Several tabs are then proposed :
280
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Element - Component name link tab

: lists the character istics of this component

Management tab : manage ˝nancial and administrative infor mation

Documents tab

Histor ical tab

Debug tab : only shown if you have debug mode enabled

All tab : for an item, all infor mation is displayed on a page

Documents
Additional infor mation is stored in the for m of exter nal documents which are
˝les uploaded into GLPI. In the
Documents
tab, documents can be associated and unlinked with the selected item. The
management of the documents themselves
is dealt with in another chapter.
It is also possible to quickly create a document via this tab by specifying the
desired ˝le and optionally the ˝eld in
which the new document is to be placed. The name of the created document will be
based on the name of the added
˝le.
ò
Note
When you delete a document from this tab via mass actions, you only remove the link
between the object and the
document ; the document itself is still present.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

GLPI User Document ation, Ver sion 10.0

For dropdowns or objects with a parent/child relationship, the modi˝cation of a
child will appear in the histor y of
the parent element.
All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Receiver s
Receivers con˝guration can be reached from
`
Con˝guration -> Receivers
`
menu.
A receiver allow to impor t emails from a mailbox ans tur n them into GLPI tickets.
A
routing mechanism
will br ing
them to the destination entity.
A receiver is associated with an email address. It is possible to add as many
receivers as you want. Of course, the more
receivers you con˝gure, the more impor t will take time.
To declare a new collector, you will have to provide a ser ver name, as well as
connection options (IMAP or POP, SSL,
TLS, cer ti˝cate validation). It is possible to limit the maximum size for
attachments (no impor t, or from 1 to 100 Mio).
This con˝guration value is inher ited from the main con˝guration (
Setup -> General -> Assistance
) A con˝guration
option per mit to switch tickets creation date between impor t date or email date.
Optionally, you can set an archive director y in the mailbox where impor ted and
refused emails will be stored.
Receivers that have er rors will be indicated above the list. In that case, number
of successive er rors will be displayed
in collector con˝guration for m.
Once the for m validated, you can test connection and messages retr ieving by using
the dedicated button.
An automatic action will do the impor t on con˝gured receivers ; time between two
executions can be con˝gured in
automated task for m.
Another automatic action will send noti˝cations when any collector repetitively
fails to impor t emails. See
noti˝cations
con˝guration <modules/con˝guration/noti˝cations>
.
.
Avertissement
Answers to emails generated from GLPI for tickets are cleaned when impor ting from
a collector : all content between
up and bottom tags will be removed. Answers must be done before or after or iginal
message.
Blac klists
Receivers can use a blacklist mechanism in order to remove recur rent but useless
contents, like email signatures.
Blacklist can also prevent emails to be impor ted from speci˝c email addresses ;
this can be useful to prevent spam, or
to handle emails aliases.
Rules for assigning a tic ket opened via a r eceiver
GLPI implements a mechanism for routing tickets opened by email, in order to create
them in the r ight entity. This is
based on the r ules engine.
282
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
if noti˝cations are not enabled in the con˝guration, the menu does not appear in
Rules
.
Available cr iter ia are :

name of receiver

requester

email domain, whether it is known or not

email headers :
auto_submitted
,
from
,
in_reply_to
,
received
,
subject
,
to
,
X-Auto-Response-Suppress
,
X-priority
,
X-UCE-Status

email body.
Finally, there is a third type of cr iter ia which operates on data speci˝c to the
user or to the con˝guration of the entities :

known email domain

: checks that the email dom ain of the email sent cor responds to a domain entered
in
an entity. This cr iter ion makes it possible to eliminate, for example, all spam,
i.e. messages not coming from
author ized domains

user : group
: checks that the GLPI user associated with the sender's e-mail address belongs to
a given g roup ;

user with pro˝le

: the user has a given pro˝le ;

user with single pro˝le

: the user has one and only one pro˝le in GLPI. If the pro˝le is associated with
several
di˙erent entities, then the one that is de˝ned as the default entity in the user's
personalization options will be
the entity of the ticket. If none is de˝ned in the preferences, the r ule does not
match

user with the pro˝le only once

: the user has a given pro˝le only once : it does not have the pro˝le assigned
on several separate entities.
The actions are either the refusal of the ticket (with or without noti˝cation of
the refusal to the issuer), or the impor t
into an entity (manual, from TAG, from mail domain, from user pro˝le).
.
Avertissement
The engine stops at the ˝rst matching r ule.
v
À faire
example
An example of using the engine is as follows :
1.
r ule refusing emails whose email domain is unknown (not taking spam into account)
;
2.
r ule refusing messages from mailing lists ;
3.
r ules a˙ecting emails if the user has only one pro˝le (case of users of the
simpli˝ed inter face) ;
4.
r ule a˙ecting emails to an entity if the user has a par ticular pro˝le (e.g. for
super administrators, who have
access to all entities, but are physically in a par ticular entity).
N oti˝cations
GLPI has a noti˝cation feature that allows it to send messages following an event
in the application, to users via email,
browser noti˝cations, and other methods (expandable by plugins).
GLPI comes with noti˝cation de˝nitions pre-de˝ned and they can be used out of the
box r ight away after enabling
noti˝cations.
To do this, you must activate the
Enable followup
option then
Enable followup via email
or
Browser followups from
browser
to display the settings menu :
3.2. Modules
283

GLPI User Document ation, Ver sion 10.0

N oti˝cation tem plates
A template is a global object of GLPI that de˝nes the infor mation included in a
noti˝cation and the for matting of the
infor mation.
The creation of a template is a complex operation, which impacts the users.
Therefore, templates can only be modi˝ed
by Administrators with the
Update
per mission for the
Con˝g
r ight. Moreover, a template is not linked to an entity,
which means that it is not possible to delegate its management to an administrator
of a sub-entity.
A template re˛ects a communication to a user and can be available in several
languages thanks to a translation me-
chanism. The use of tags (i.e. markers that are independent of the language used)
makes it possible to create a gener ic
translation, available for all the languages of GLPI.
GLPI comes with a set of pre-de˝ned templates for all noti˝cations (tickets, reser
vations, ˝nancial infor mation, car-
tr idges, consumables, licenses, MySQL synchronization. . .).
Par ameter s
N oti˝cation tem plate
First tab.

Name
: Template name

Type
: Type of GLPI object to which the template relates

Comments
: (optional) Additional infor mation

CSS
: (optional) Style sheet used for the template in HTML
ò
Note
Templates are global, they are not de˝ned at the entity level, as noti˝cations.
Tem plate tr anslation
Tab that lists the di˙erent noti˝cations de˝ned by language and allows adding a new
language.

Language
: Indicates the language to which this translation refers. If no language is
selected in the drop-down
list, this translation will be the default for this template.

Subject
: Subject of the mail.

Email text body

: Plain text without layout, used in cases where HTML is not allowed. If the ˝eld
is empty,
then it is generated from the HTML body text.

Email HTML body

: Text with HTML layout.
ò
Note
A default translation is applicable to all GLPI languages that do not have their
own translation.
Tags
The tags allow to display data of the noti˝cation tr igger object.
e.g.
: in a ticket you can retr ieve its title, descr iption,
actors. . .
A tag is identi˝ed by
##
at the beginning and at the end.
There are several types of tags :

Simple
:
##<object>.<field>##
for the ˝eld value of a GLPI object

Label
:
##lang.<object>.<field>##
for the translated label of the object's ˝eld

Condition
: to test if a ˝eld has :

a value :
##IF<object>.<field>##
. . .
##ENDIF<object>.<field>##
284
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

a value = <V> :
##IF<object>.<field>=<V>##
. . .
##ENDIF<object>.<field>##

Loop
: to display sub-objects :

all <objects> :
##FOREACH<objects>##
. . .
##ENDFOREACH<objects>##

˝rst <N> <objects> :

##FOREACH FIRST <N> <objects>##
. . .
##ENDFOREACH<objects>##
last <N> <objects> :
##FOREACH LAST <N> <objects>##
. . .
##ENDFOREACH<objects>##
Tem plate exam ple
In this example, we will create a template for ticket mail noti˝cations.
In the end, this template can be used for several ticket events :

New ticket

Add followup

Add task

Resolve ticket

. . .
3.2. Modules
285

GLPI User Document ation, Ver sion 10.0

Cr eate tem plate
1.
Go to
Setup > Noti˝cations > Noti˝cation templates
2.
Click on
Add
button
3.
Fill in ˝elds

Name
:
Generic tickets with timeline
for example

Type
:
Ticket

Comments
:
Generic template for tickets, using timeline
for example

CSS
:
leave empty for now
4.
Save to be redirected to the template translation
Basic dat a
We are now in the editing mode of a template translation.

Language
:
Default translation
The minimum required. We will see later how to add other languages.
Subject
:
##ticket.action##: ##ticket.title##
# [GLPI <ticket_number>] # will be automatically
added to the email subject
ò
Note

##ticket.action##
: action that tr iggered the noti˝cation

##ticket.title##
: ticket title

Email text body

:
leave empty to be ˝lled automatically

Email HTML body

:
this is the ˝eld that we will mainly modify in the next chapters
Case : N ew tic ket
Let's star t by adding some basic data. You can add more by using the #
Show list of available t ags
# button to display
the available tags.

Email HTML body

:
##ticket.action##: ##ticket.title##
##lang.ticket.status##: ##ticket.status##
##lang.ticket.url##: ##ticket.url##
##lang.ticket.description##:
##ticket.authors## - ##ticket.creationdate##
##ticket.description##
ò
Note

##lang.ticket.status##
: text # Status #
automatically translated into the recipient's language

##ticket.status##
: ticket status

##lang.ticket.url##
: text # URL #
automatically translated

##ticket.url##
: ticket url

##lang.ticket.description##
: text # Ticket Descr iption #
automatically translated

##ticket.authors##
: ticket requesters
separated by #,# if there is more than one
##ticket.creationdate##
: ticket creation date

##ticket.description##
: ticket descr iption text
286
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Case : Add followup, Add t ask , Resolve tic ket
Follow-ups, task s and solutions are elements of a ticket's timeline, so we'll loop
through # timelineitems # using
FOREACHtimelineitems
.

Email HTML body

:
##ticket.action##: ##ticket.title##
##lang.ticket.status##: ##ticket.status##
##lang.ticket.url##: ##ticket.url##
##FOREACHtimelineitems##
##timelineitems.author## - ##timelineitems.date##
##timelineitems.description##
##ENDFOREACHtimelineitems##
##lang.ticket.description##:
##ticket.authors## - ##ticket.creationdate##
##ticket.description##
ò
Note

##FOREACHtimelineitems##
: loop over all timeline items

##timelineitems.author##
: author of the timeline item

##timelineitems.date##
: date of the timeline item

##timelineitems.description##
: descr iption text of the timeline item

##ENDFOREACHtimelineitems##
: end of the loop
Layout
For now, we have only retr ieved tags but there is no for matting yet.
Put in bold
1.
Select text :
e.g.
##ticket.authors##
2.
Click on
Bold
button
Clic kable link
1.
Select URL text :
e.g.
##ticket.url##
2.
On r ight-click menu, click on
Link. . .
3.
Fill in the ˝eld
URL
=
##ticket.title##
4.
You can leave the other ˝elds unchanged and
Save
Add headings
1.
Select text :
e.g.
##ticket.action##: ##ticket.title##
2.
Click on the
format
drop-down list and select
Headings > Headings 1
3.2. Modules
287

GLPI User Document ation, Ver sion 10.0

Add a logo
1.
Without selecting any text, click on the place where you want to put your image
2.
Click on
Insert image
button
3.
Browse to add your image
4.
If necessar y, you can resize via
right-click
menu >
Image. . .
Add a t able
This table will allow us to display the logo at the same row as the ticket title
and its URL.
1.
Without selecting any text, click on the place where you want to put your table
2.
Click on
Insert t able
button
3.
The generated table has 2 columns and 2 rows, we only want one row, so delete
one :
1.
Right-click on the generated table
2.
Clic on
Row
>
Delete row
4.
Select the previously added image, to drag and drop it into the left cell
5.
Select the text of the tags below, to drag and drop it into the r ight cell
##ticket.action##: ##ticket.title##
##lang.ticket.status##: ##ticket.status##
##lang.ticket.url##: ##ticket.url##
6.
Right-click
on table >
Table properties
7.
In
Advanced
, click on
Background color
˝eld to select
Dark Blue
8.
Click on
Save
button
Chang e color s
As the backg round of the table is dark, we will wr ite in white to be more
readable.
1. Select the text in the table 3. Click on the
Text color
drop-down list and select the color
White
Add conditional emoticon
If the ticket is in pending status, we want to display an emoji.
1.
Add 2 test tags :
##IFticket.storestatus=4## ##ENDIFticket.storestatus##
2.
Right-click
between the 2 tags >
Emoticon
3.
Add emoticon named
Pause button
Tr anslations
So far, we have only used
##lang....##
tags which are automatically translated. So we could be satis˝ed with a single
translation in the
Default translation
language.
Let's take the case where we have users who only understand one language (English,
French or Spanish). And we want
to add a text under the URL that ever yone can understand :

If you wish to add fur ther infor mation, click on the previous links, or reply
directly to this e-mail.
English

Si vous souhaitez ajouter des infor mations supplémentaires, cliquez sur les liens
précédents, ou répondez di-
rectement à cet e-mail.
French

Si desea añadir más infor mación, haga clic en los enlaces anter iores, o responda
directamente a este cor reo
electrónico.
Spanish
288
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

1.
In the
Default translation
we add the English text
2.
Remember to
Save
3.
Right-click
in # Email HTML body # ˝eld >
Source code
4.
Select all the code to
copy
it
5.
Go back to the template header by clicking on the
Noti˝cation templates
value at the top
6.
In
Template translations
tab click on
Add a new translation
button
7.
Select Language =
Français
8.
Right-click
in # Email HTML body # ˝eld >
Source code
9.
Paste
the previously copied code
10.
Save
to exit code view
11.
Updates the ˝elds :

Subject
=
##ticket.action##: ##ticket.title##

In
Email HTML body
replace English text with the French text
12.
Save
Repeat steps 3 to 12 for all useful languages.
Going fur ther with HTML and CSS
.
Avertissement
Par t for people already familiar with HTML and CSS.
Ever ything we have done in the # Email HTML body # ˝eld is conver ted into HTML
code which you can edit via
right-click
>
Source code
. So if you are familiar with HTML, you can edit the code directly. Depending on
the case
and your skills, this is sometimes easier.
The following code repeats what we did earlier by separating the CSS layout fro m
the HTML and adding colors to the
timeline items. It is not explained, it is just an example.
Code in # Email HTML body # ˝eld
<
table
class
=
"header"
border
=
"0"
>
<
tbody
>
<
tr
>
<
td
class
=
"logo"
>
<
img
src
=
"data:image/png;base64,
,
!
iVBORw0KGgoAAAANSUhEUgAAAGQAAAA3CAYAAAD6+O8NAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJ
lYWR5ccllPAAABWVJREFUeNrsWz9PG1kQX5Ot0tyeUkf4GlqckjQ4ob0I8wliX3cVcHWkEIk2IXwC4BNAlL
R3mCaULGXSxCeflCZWNk1OusaZQbOJsd+/
,
!
eW92jU5vpKeFxX7vzfzmz2/eLkkSJUqUKFGiRIkSJcr/
,
!
XhpVLzAej9tTt8rfBzRQ8kajUTDnbcElm7jFnkMzbxMuTcZXBrDuQMg2uZTRmzA6MHZgHMM4HfPkA3O9rmK
OYwE9WmM/
,
!
+YB7Yq61pdIhDfAiRHedrlmgLZrMz68r7mUCvtUJ2P8B2GUTrhuOEaPSIUm5ngmXxxNpR0oKAQALgX0sB34
f0+gF2OkXh/
,
!
Sp0uEydQABPW8LxqaHFxaUF88mfr66DxvOAxWfUUYAkExoDkyfDzwAGdjA6FB+5ObTPSq6VZCEpmbdrsDcn
8dy0vWoVW1tVMA4YG7gVDuhMGtjKcOb29mwZKOuAcQLDx0y3UIXzIioHAgLO1ErUwPQ5O06UJocHfBvC4p6
carJ0So5gXEP6kG/
,
!
xt5JaXiJHkQzb9/
,
!
yd6yFh0z2qNKhPwMIFSNXMA5hMxtVGcIgqzplAqUdwNxeMebU6VBcAwSbOgad7QMQvRt04iDhFD8p7uUSUe
QYIZffAaFUtclQfp5gtCuivC02Db3eKIusVUbIFoOD7/
,
!
ue3QgUdN0eJfajMurfAQZWplIDeNcAeczY+OEco6NVMyCuzeu65n7OKPRXOqTUwLmGXO4THbDGElzuwrhD1
0kZwXgH854HnHnlgZHX8q1N5PFdja0KVx1Ku6bMc6m+o4J3yZuXaNhkBb6zBtcXsLGvXEAEmF4WALTulPnI
JxIRkEXGxr8YQEDvv4/
,
!
GpUjgCoL4O4znzMM/
,
!
Ccrb4gJN9UzXJhSG1L5sisSU0XdolYfNrRAYZQoaEShcYJY8PFmC8mYavY7J04spD8c+omOIrJ4BTNV3ziY
BkehmMf+fGyKnTGErLukO5hvWTHlXNfc7Cf8ZCTbMJ74N6IJAD2ADa4THCzAwhHcdPj+cA+WVOHYvweh50P
Z8EpCzujgrGXtk+Mj7OVFeiUcFzxxOL6w6pEyFVgPppa2uvPXw4kHgnpqhUUFguOzDSHlLQDgsBY+oswCae
d/
,
!
wt6GlF2nZlBFsCCdze65JMVi7Tpi2sDafKSoERs4ZYYvHLDueypuK+pHlu4vSDaEljfSo7knKso0llkV9nz
Hpps/
(suite sur la page suivante)
3.2. Modules
289

GLPI User Document ation, Ver sion 10.0

(suite de la page précédente)
,
!
DIGr87hiK4dDDu6qivIMKwLBS3u+A0OIDxqTHTDAQiF8NYJx7erIEIVmtiCh4sdRJ2rvNrCUHjmDcpg78dg
AYdTeF4szTkFX6SkComXnJWKNLLzZkFjD+SGYPFFlgGJ5rV1lDpMXpAHNhirFsJ7zjdTSU8jVKSlMqMPDwc
JcRGfOgvP0KANFR3lwLCH2gxwQFjXVAb59s0VsrWMCfKMAYEhhDCe+qkPIWNQEys/
,
!
9Uo2gPjIp5dI9xrNCkz+/RQh+pK/8E4z8Yb2De157KLGo8/
,
!
IJhvJwygAvQeQWALHsDUjIvUBhD92mifgBjA2faI5Zgvt+S2cPAgupJ4eHJnPzfVhCXrEaGlYnVQHp9c0/
,
!
4VUvn10Cl1lXMq/q3idMq0NBsacdEexNDtGCjtA3jZ/h1g2pMVZ7EKeoccS3UderVd05ZBnCQHp/
,
!
QY9qnyY9n5Wi0Wwn/fz1cQjdPwunpkWPxflWR8Yspxxqo9G54hB4a/9HUuRRS2Nf47GOKUrqAk8/
,
!
h7ccbK40AILCf+AvGn5YXE6JIAkLdNp5DrdEtjAKkr5cRiBoBISAQhId0DoVp6S2A8D6arUZApoD4F1MS5f
lRNFfNgNAbfJie/
,
!
onRcAOkqv8LjBIlSpQoUaJEiRJlvvJNgAEAqG9GVu+GoEcAAAAASUVORK5CYII="
alt
=
"GLPI"
width
=
"100"
height
=
"55"
/></
td
>
<
td
class
=
"title"
>
<
h2
><
strong
>##ticket.action##</
strong
>: ##ticket.title##</
h2
>
<
h4
>##lang.ticket.status##: ##ticket.status## ##IFticket.storestatus=4###
,
!
#ENDIFticket.storestatus##</
h4
>
<
strong
>##lang.ticket.url##</
strong
>: <
a
href
=
"##ticket.url##"
>##ticket.url##</
a
>
</
td
>
</
tr
>
</
tbody
>
</
table
>
<
p
>If you wish to add further information, click on the previous links, or reply

,
!
directly to this e-mail.</
p
>
<
p
>##FOREACH LAST 5 timelineitems##</
p
>
<
div
class
=
"timeline ##timelineitems.type##"
>
<
p
class
=
"attributes"
><
strong
>##timelineitems.author##</
strong
> - ##timelineitems.date##
,
!
</
p
>
<
p
>##timelineitems.description##</
p
>
</
div
>
<
p
>##ENDFOREACHtimelineitems##</
p
>
<
h4
>##lang.ticket.description##:</
h4
>
<
div
class
=
"request"
>
<
p
class
=
"attributes"
><
strong
>##ticket.authors##</
strong
> - ##ticket.creationdate##</
p
>
<
p
>##ticket.description##</
p
>
</
div
>
Code in # CSS # ˝eld
.
header
{
width
:
100
%
;
background-color
:
#2f3f64
;
color
:
#eeeeee
;
border
:
none
;
}
.
title
{
padding
:
10
px
;
}
.
title
a
{
color
:
#dddddd
;
}
.
attributes
{
background-color
:
#1111
;
border-radius
:
4
px
;
padding
:
0
5
px
;
}
(suite sur la page suivante)
290
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

(suite de la page précédente)
.
timeline
,
.
request
{
padding
:
5
px
;
border
:
thin
solid
;
border-radius
:
4
px
;
}
.
timeline
{
margin
:
5
px
15
px
;
display
:
inline-block
;
}
.
ITILFollowup
{
background-color
:
#ececec
;
border-color
:
#cccccc
;
}
.
TicketTask
{
background-color
:
#ffe8b9
;
border-color
:
#e5c88c
;
}
.
ITILSolution
{
background-color
:
#9fd6ed
;
border-color
:
#90c2d8
;
}
.
request
{
background-color
:
#e2f2e3
;
border-color
:
#87aa8a
;
}
N oti˝cation De˝nitions
A noti˝cation de˝nition in GLPI is composed of :

One or more noti˝cation templates

Templates are added for speci˝c noti˝cations modes. This allows you to use one
template for email noti˝-
cations and another for browser noti˝cations.

A set of recipients
The list of recipients could include speci˝c users, g roups, etc or can include
dynamic recipients such as
# Requester # which would be replaced by all user's listed as requester on a Ticket
for example.

An item type (Ex : Ticket).

An event from the speci˝ed item type (Ex : Add).

The di˙er ent t abs

Noti˝cation
A noti˝cation is composed of a cert ain number of speci˝c ˝elds to ˝ll in :

Name
: Name of the noti˝cation.

Active
: Allows you to temporar ily deactivate a noti˝cation.

Type
: Type of GLPI object to which the noti˝cation refers.

Noti˝cation mode
The noti˝cation method (Email and Browser available by default).

Event
: Indicates what will be the tr igger ing event following the type of the object.

Noti˝cation templates
: Indicates the noti˝cation that will be sent for the object type and the event
de˝ned
previously.

Recipients
This is where you de˝ne who will receive the noti˝cation.
3.2. Modules
291

GLPI User Document ation, Ver sion 10.0

A cer tain number of actors of the application are proposed and the list The list
var ies according to the type
of object de˝ned.
This list includes, but is not limited to :

Administrator
: person whose email address has been de˝n ed in the global
con˝guration of email
follow-ups
.

Entity Administrator
: person, for each entity, whose email address is de˝ned in the entity
con˝guration
of email follow-ups
.

Requester
: The person who is listed as the requester in the ticket.

Technician in charge of the ticket

: Users assigned to the ticket.

Group XXX
: All the people who have access in the entity and who are par t of the g roup.

Group XXX without supervisor

: All members of the g roup except the person declared Manager of
the g roup.

Group in charge of the ticket

: All the members of the g roup to which the ticket is assigned.

Group in charge of the ticket without supervisor

: All members of the g roup assigned to the ticket,
except for the person declared Manager of the g roup.

Requesting group
: All members of the g roup indicated as the requesting g roup of the ticket.

Observer group
: All members of the g roup indicated as the obser ver g roup of the ticket.

Observer
: The person who is the obser ver of the ticket.

Pro˝le XXX
: All the people who have access in the entity and who have this pro˝le.

Writer
: person who enters the infor mation.

Technical manager
: The person designated as the user responsible for the asset(s) related to the
ticket.
Email follow -ups con˝gur ation
For GLPI to be able to send noti˝cation via email, an email ser ver connection will
need con˝gured.
The email ser ver con˝guration can be con˝gured globally, and then some options can
be over r idden at the entity level.
Global settings can be accessed from the # Email followups con˝guration # option on
the
Setup > Noti˝cations
page.
Global Con˝gur ation
The global con˝guration allows you to set the following options :
292
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Option
Meaning
Administrator email
GLPI Administrator email.
This can be used as a special recipient in noti˝cations
Administrator name
The display name to use for the Administrator email ad-
dress.
From email
The email address to use in the From ˝eld for emails sent
by GLPI.
From name
The display name to use for the From email address.
This name will be seen by end users.
Reply-to address
The email address to use when user's reply to the email
noti˝cations.
Reply-to name
The display name to use for the Reply-to email address.
No-Reply address
The email address to use for emails that shouldn't be re-
sponded to.
No-Reply name
The display name to use for the No-Reply email address.
Add documents into
ticket noti˝cations
If enabled, documents attached to a ticket will be added
to related noti˝cations as links.
The links will use the GLPI URL speci˝ed in the
general con˝guration.
Email signature
Text added at the end of ever y noti˝cation.
Way of sending emails
Method to send emails (PHP, SMTP, SMTP+SSL,
SMTP+TLS).
Max deliver y retries
Number times GLPI will tr y to send a noti˝cation.
Tr y to deliver again in (minutes)
Time between noti˝cation deliver y attempts.
You can test the sending of noti˝cations from the global noti˝cation con˝guration
for m by tr ying to send an email to
the speci˝ed Administrator email address.
Email Method - PHP
This option cannot be con˝gured within GLPI and must be done in your PHP
con˝guration. This option uses the
mail()
function of PHP.
ò
Note
The PHP email method is blocked by most hosting providers.
Email Method - SMTP
The following con˝guration options are available for the
SMTP
email method(s) :

Check cer ti˝cate - Ver ify the email ser ver has a valid cer ti˝cate.

SMTP host - The SMTP ser ver address.

Port - The port to communicate with the SMTP host over.

3.2. Modules
293
GLPI User Document ation, Ver sion 10.0
Typically, this is por t 25. Check your provider's documentation for more info.
Also, additional con˝guration may be needed if your provider needs
IMAP OAuth
.

SMTP login (optional) - User name to authenticate with the email ser ver.

SMTP password (optional) - Password to authenticate with the email ser ver.

Email sender - This may be needed for some email providers.

If this is not speci˝ed, the Administrator email will be used.
Email Method - SMTP+SSL
The con˝guration options are the same as the
SMTP
option but GLPI will use
SSL
secur ity for the connection.
Email Method - SMTP+TLS
The con˝guration options are the same as the
SMTP
option but GLPI will use
TL S
secur ity for the connection.
Entity Con˝gur ation
The following options can be over r idden at an entity level (see global
con˝guration for more infor mation about each
option) : - Administrator email - Administrator name - Reply-to address - Reply-to
name - Email signature
The entity level options can be accessed for the
Noti˝cations
tab in the entity's for m.
The following options can only be con˝gured at the entity level :

Pre˝x for noti˝cations

- Text to pre˝x to the subject of email noti˝cations.

Delay to send email noti˝cations

- Optional delay to the initial sending of noti˝cations.

Enable noti˝cations by default

- If enabled, a user is automatically set to receive noti˝cations in some cases
such as when they are assigned to a ticket.
Fields that are no set, will be inher ited from their parent entity by default.
Alarm options
At the entity level, you can con˝gure the alar m options (car tr idge/consumable
stock alar ms, expiration alar ms, etc). By
default, these options will inher it the value from their parent entity.
As of GLPI 10.0, the following alar m options are available : - Car tr idges >
Reminders frequency for alar ms on car tr idges
- Car tr idges > Default threshold for car tr idges count - Consumables > Reminders
frequency for alar ms on consumables
- Consumables > Default threshold for consumables count - Contract > Alar ms on
contracts - Contract > Default
value - Contract > Send contract alar ms before - Financial and administrative
infor mation > Alar ms on ˝nancial and
administrative infor mation - Financial and administrative infor mation > Default
value - Financial and administrative
infor mation > Send ˝nancial and administrative infor mation alar ms before -
Licenses > Alar ms on expired licenses -
Licenses > Send license alar ms before - Cer ti˝cates > Alar ms on expired cer
ti˝cates - Cer ti˝cates > Send cer ti˝cates
alar ms before - Reser vations > Aler ts on reser vations - Tickets > Aler ts on
tickets which are not solved since - Domains
> Alar ms on domains expir ies - Domains > Domains closes expir ies - Domains >
Domains expired
ò
Note
Noti˝cations work as follows (
e.g. : ticket creation noti˝ed by email
) :
1.
The ticket is created in GLPI.
2.
GLPI looks for noti˝cations of the #
ticket creation
# event in the ticket entity (other wise in the parent
entities).
3.
GLPI builds the list of recipients according to the settings.
4.
For each recipient, GLPI generates the mail in the language of the user if the
translation exists, other wise it
is the #
Default translation
#.
294
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

5.
The emails are placed in
Administration > Noti˝cation queue
waiting to be sent by the automatic task
queuednotification
.
.
Avertissement
When new noti˝cations are added to GLPI through an update, they are enabled by
default.
Con˝gur e automatic actions
GLPI has multiple automatic actions (also refer red to as crontasks) that are per
iodically scheduled jobs. These actions
can be con˝gured to r un at a speci˝c frequency and r un in either GLPI or CLI
mode.
In GLPI mode, the actions are star ted occasionally when users navigate GLPI. In
CLI mode, the actions are star ted in
their own session via cron, Scheduled Tasks, or some other exter nal task
scheduler. You may con˝gure some actions
to r un in GLPI mode and others to be CLI. Some actions may suppor t only one of
the modes.
Con˝gur e CLI mode
To r un CLI mode tasks, you will need to con˝gure your exter nal task scheduler to
call GLPI's
front/cron.php
˝le
per iodically. It is recommended to have it r un ever y minute to ensure that
actions that are ready to r un, get ran as soon
as possible.
For Linux/MacOS, you should add the following to the web ser ver's user's (www-
data, apache, etc) crontab :
*
*
*
*
*
php GLPI
/
front
/
cron
.
php
You will need to replace
GLPI
with the path to your GLPI folder. You may also need to replace
php
with the full path
to your php binar y if it is not in the PATH.
Force execution of action from CLI
To execute a speci˝c action from the command-line, you can r un (for mailgate
action) :
php GLPI
/
front
/
cron
.
php
-
-
force mailgate
You will need to replace
GLPI
with the path to your GLPI folder.
Forcing the action to r un will ensure it is r un even if it is not scheduled to r
un again yet.
Default actions
aler tnotclosed (Tic ket)
Send noti˝cation aler ts for tickets that have been open a cer tain number of days
without being closed. Noti˝cations
must be enabled for this action to work. The number of days can be con˝gured for
each Entity.
car tridg e (Car tridg eItem)
Send noti˝cation aler ts for car tr idge stock under the aler t threshold.
Noti˝cations must be enabled for this action to
work. The aler t threshold can be changed for each Car tr idge.
3.2. Modules
295

GLPI User Document ation, Ver sion 10.0

cer ti˝cate (Cer ti˝cate)
Send noti˝cation aler ts for cer ti˝cates that are about to expire. Noti˝cations
must be enabled for this action to work.
The expiration war ning delay can be changed for each Entity.
chec kAllU pdates (GlpiMarketplaceController)
Checks all installed plugins to see if there is an update available. The plugins
must be available via the
marketplace
even if they weren't installed that way in order for the update detection to work.
If you have noti˝cations enabled, you
can receive a noti˝cation regarding the available updates. Other wise, the
available updates are listed in the action's log.
chec kdbr eplicate (DBconnection)
Checks the statu s of all database replicates including that it is reachable from
GLPI and that it is in sync with the
main database. If you have noti˝cations enabled, you can receive a noti˝cation
regarding any issues with the replicates.
Other wise, the issues are listed in the action's log.
chec kupdate (CronTask)
Checks for a new GLPI version.
circularlogs (CronTask)
Removes entr ies in logs in the
˝les/_log
folder that are older than a cer tain number of days which is con˝gurable within
the action for m itself.
cleanorphans (Document)
Deletes all documents that aren't associated with other GLPI items like Tickets.
ò
Note
This doesn't account for direct links to documents added for example in Ticket
tasks, comments, etc.
cleanorphans (GlpiInventor yInventor y)
Deletes all inventor y submission ˝les that are not related to an existing asset in
GLPI.
cleansof twar e (CleanSof twar eCron)
Deletes all software versions without an installation and deletes all software
without a version.
cleantem p (GlpiInventor yInventor y)
Deletes all temporar y inventor y ˝les older than 12 hours.
closetic ket (Tic ket)
Closes all tickets that were solved for a cer tain amount of working time. The
amount of time can be con˝gured for each
Entity.
296
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

ò
Note
The working hours on the Entity's calendar are considered when deter mining how
much working time had passed.
consumable (ConsumableItem)
Send noti˝cation aler ts for consumable stock under the aler t threshold.
Noti˝cations must be enabled for this action to
work. The aler t threshold can be changed for each consumable.
contr act (Contr act)
Send noti˝cation aler ts for contracts that are about to expire. If you don't have
noti˝cations enabled, the expiration
war nings are still listed in the action's log. The expiration war ning delay can
be changed for each Entity.
countAll (SavedSearch)
Updates the estimated execution time for saved searches.
cr eateinq uest (Tic ket)
Creates ticket satisfaction sur veys after a cer tain amount of time and closes sur
veys after a cer tain amount of time. Both
durations can be changed for each Entity.
DomainsAler t (Domain)
Send noti˝cation aler ts for domains that are about to expire. If you don't have
noti˝cations enabled, the expiration
war nings are still listed in the action's log. The expiration war ning delay can
be changed for each Entity.
gr aph (CronTask)
Cleans generated g raphs older than an hour.
These g raphs were only created in GLPI before version 9.2 for statistics and
possibly some plugins from those versions
or newer.
infocom (Infocom)
Send noti˝cation aler ts for war ranties (Set in the Management tab on an asset for
m) that are about to expire. If you
don't have noti˝cations enabled, the expiration war nings are still listed in the
action's lo g. The expiration war ning delay
can be changed for each Entity.
logs (CronTask)
Cleans old automatic action log entr ies. The amount of time to keep log entr ies
can be changed for each automatic
action.
mailg ate (MailCollector)
Retr ieves emails from
con˝gured mailboxes
and creates tickets from the mail.
3.2. Modules
297

GLPI User Document ation, Ver sion 10.0

mailg ateerror (MailCollector)
Send noti˝cation aler ts for any er rors encountered when collecting emails by the
collectors.
olatic ket (OlaLevel_Tic ket)
Evaluate OLA levels for tickets.
passwordexpir ation (User)
Send noti˝cation aler ts for user passwords that expired and handle disabling the
a˙ected accounts.
pendingr eason_autobum p_autosolve (PendingReasonCron)
Automatically add followups for tickets that are in a pending status to tr y and
get a response from or to remind an
end-user of the pending reason. If the end-user doesn't respond after a cer tain
number of reminders, the ticket will be
automatically resolved.
planningr ecall (PlanningRecall)
Send noti˝cation reminders for planned events.
Purg eLogs (Purg eLogs)
Deletes histor ical data entr ies that are older than a cer tain amount of time.
The amount of time can only be changed
globally for all Entities, but some of the types of entr ies can be con˝gured with
di˙erent durations.
purg etic ket (Tic ket)
Purge tickets that have been closed for a cer tain amount of time. The delay can be
changed for each Entity.
q ueuednoti˝cation (QueuedN oti˝cation)
Tr y sending all queued noti˝cations. If a noti˝cation cannot be sent, the failure
is recorded and then the noti˝cation will
tr y to be sent again dur ing the next action r un in case it was a temporar y
issue. After continued failures, the noti˝cation
is cancelled.
q ueuednoti˝cationclean (QueuedN oti˝cation)
Deletes all noti˝cations that are older than a cer tain number of days. The number
of days can be con˝gured within the
action itself.
Recurr entItems (CommonITILRecurr entCron)
Create scheduled recur r ing tickets or changes.
r eser vation (Reser vationItem)
Send noti˝cation aler ts for the end of reser vations.
298
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

savedsearchesaler ts (SavedSearch_Aler t)
Send noti˝cation aler ts for saved searches.
session (CronTask)
Delete expired session ˝les.
slatic ket (SlaLevel_Tic ket)
Evaluate SLA levels for tickets.
sof twar e (Sof twar eLicense)
Send noti˝cation aler ts for software licenses that are about to expire.
Noti˝cations must be enabled for this action to
work. The expiration war ning delay can be changed for each Entity.
telemetr y (Telemetr y)
Send telemetr y infor mation.
tem p (CronTask)
Clean all temporar y ˝les older than an hour.
unloc kobject (ObjectLoc k)
Automatically remove locks on items older than a speci˝c number of hours. The
number of hours can be changed within
the action itself.
watcher (CronTask)
The watcher automatic action is an action that monitors the execution of the other
automatic actions. If one of them has
an er ror, a noti˝cation will be sent. For this to work properly, noti˝cations will
need to be con˝gured.
The di˙er ent t abs

Automatic action
For each action, it is possible to con˝gure :

Run frequency

Status (Allows you to disable the action if needed)

Run mode

Run per iod (Allows you to disable cer tain actions at night for example)

Number of days this action's logs are stored

The inter face also allows you to reset the execution date and to manually force
the execution manually.
Some automatic actions can have par ticular parameters, such as the maximum number
of emails to be sent each
time for the mailqueue action. Also plugins can de˝ne their own automatic actions.

St atistics
Displays infor mation about the execution of this task (number of executions, star
t date, minimum,
maximum, average and total durations).
Logs
Lists the last executions according to the parameter de˝ned in the
Automatic action
tab (see above). A
link on the execution date allows to have the details of a speci˝c execution.
3.2. Modules
299

GLPI User Document ation, Ver sion 10.0

The di˙er ent actions

Reset last run

: Clear the last r un
Fields unicity
GLPI has a mechanism to per for m uniqueness checks before the creation of an
object in the database.
This allows you to track and/or block the presence of duplicate objects based on
matching cer tain ˝elds. For example,
you can con˝gure a ˝elds unicity r ule for computers using the ser ial number ˝eld.
This applies to manual additions
and additions made from an exter nal source such as an inventor y tool.
Uniqueness is de˝ned by a name, an object type, and one or more ˝elds. When
multiple ˝elds are speci˝ed, all of them
are checked together instead of individually (Ex : ser ial number AND UUID match
another computer. Uniqueness
checks for ˝elds only apply if the ˝eld is not empty. For example, multiple
computers with a blank ser ial number would
be allowed. Each uniqueness r ule has options to refuse the addition of the object
and/or send a noti˝cation if it is
deter mined to not be unique.
Th cr iter ia added in the blacklists will be ignored when calculating uniqueness.
The di˙er ent t abs
Duplicates
The duplicates tab lists all the values cor responding to the cr iter ia that are
cur rently duplicated.
Histor y
The
Histor y
tab is used to show any changes made to an item. The following infor mation about
the changes is available :

ID of the change.

Date and time the change was made.

User who made the change. If this ˝eld is not ˝lled, it means that the action was
done automatically (For
example : automatic inventor y update).

Field that was changed.

Descr iption of the change that was made.

Tr igger ing event

Recipient(s)

Noti˝cation model used

Recipient(s) email address

300
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

All Information
For an item, all infor mation is displayed on one page from the
All
tab. This shows all of the tabs of an object's for m in
one view, one below the other.
Ser vice Levels
There are two types of ser vice level ag reements that can be tracked in GLPI. -
Ser vice Level Ag reement (SLA) :
Ag reement between an IT provider and the customer - Operation Level Ag reement
(OLA) : Ag reement between
g roups/depar tments of the IT provider
Both of these types of ag reements are used in GLPI to optionally track : - The
maximum amount of time that should
pass before a ticket has a technician assigned - The maximum amount o f time that
should pass before a ticket is resolved
A calendar can be associated with an SLA/OLA (see
calendars
). By default, no calendar is associated and calculations
are done on a working basis 7 days a week and 24 hours a day. It is also possible
to use the calendar associated with
the ticket (i.e. the one of the entity to which the ticket is attached).
ò
Note
If the maximum resolution time is expressed in days, all the calculations will be
done in days (D+1, D+4 for
example) taking into account the calendar to deter mine the working days. In the
use of the End of the working day
indicator, the due date will cor respond to the end of the cor responding working
day. If the maximum resolution
time is expressed in hours or minutes, then the calculations will be made taking
into account the opening hours.
For example, for an SLA in H+4 with a calendar de˝ning opening hours from 8am to
6pm, a ticket opened at 4pm
will have a due date of 10am the next day.
Changing the ticket to pending status puts the SLA in sleep mode. If the ticket
remains pending for 3 hours for example,
the due date will be postponed by 3 hours.
Automatic assignment of ser vice levels
You can automatically assign an SLA or OLA to tickets through the ticket r ules
engine. Th e association of the SLA
with the ticket allows the automatic calculation of its the expiration date.
Several SLA/OLAs can thus be de˝ned and
assigned according to precise cr iter ia.
For example, SLA 1 will be assigned if the ticket is associated to a speci˝c
categor y and SLA 2 for the other categor ies.
3.2. Modules
301

GLPI User Document ation, Ver sion 10.0

.
Avertissement
If an SLA/OLA is assigned manually when the ticket is opened (by the user or via a
ticket template), the business
r ules cannot rede˝ne it.
When it is assigned, it will be completely replayed and the actions associated with
the escalation levels will be executed.
Escalation levels
After adding an SLA/OLA to a ser vice level, you can click on the name of the
SLA/OLA in the related tab of the ser vice
level to con˝gure it more including escalation levels.
After adding an escalation level to an SLA/OLA you can click its name to con˝gure
the cr iter ia to tr igger it and the
actions to take after it is tr iggered.
Each level tr iggers automatic actions to resolve the ticket as soon as possible. A
level is tr iggered before or after the
expiration date of the SLA/OLA according to the de˝ned delay.
For example, one day before the deadline, the ticket
is
assigned to level
2
support
and

,
!
its priority
is
changed to High
.
Escalation levels can be conditioned by tr igger cr iter ia. Without cr iter ia,
the level will be tr iggered but if cr iter ia are
cr iter ia are de˝ned, they will be checked before applying the escalation level.
For example, if 1 day before the due date you want to send a reminder to the

,
!
administrator if the ticket is still in *New* status, you need to set the criteria
as
,
!
`
Status is New
`
.
Gener al con˝gur ation
GLPI general con˝guration allow global GLPI con˝guration. Some of the parameters
can be changed by users in their
session.
Gener al con˝gur ation
This tab per mits to customize main application appearance.
302
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Description of ˝elds

URL of the application

: used in di˙erent links provided in the application, in noti˝cations, and for the
API.
Its de˝ned at install time depending on the URL that has been used for it.

Text in the login box

: speci˝c text to be displayed at the top of the login block

Allow FAQ anonymous access

: allows
Frequently Asked Question <FAQ>
access without any login in
GLPI. A link to access the FAQ will be displayed below the login box when enabled.

Default search results limit

: maximum number of search results displayed at once on all search pages

Default characters limit

: maximum number of displayed characters visible in search results. If you display
a
ticket content for example, it will be tr uncated on this number of characters

Default url length limit

: same as the above, but applying on URLs

Default decimals limit

: number of decimals displayed for amounts

Translation of dropdowns
: allows dropdowns do be translated. Once this parameter enabled, a translation tab
will be added on dropdown for ms (see
dropdowns translations
)

Translation of reminders
: same as the above, but applying on reminders

Knowledge base translation

: same as the above, but applying on knowledge base entr ies

Simpli˝ed inter face help link

: link to help displayed for users using simpli˝ed inter face

St andard inter face help link

: link to help displayed for users using standard inter face

Page size for dropdown

: number of elements displayed in a dropdown on each scroll

Don't show search engine in dropdowns if the number of items is less than
: search in dropdown won't be
displayed if there are less results than con˝gured here

Items seen

Global search
: enable global search adding a search ˝eld at the top of the inter face
3.2. Modules
303

GLPI User Document ation, Ver sion 10.0

Default values
This tabs allows to con˝gure the display preferences that are used by default. Th
ey can be over r idden for each user (see
manage preferences
).
Per sonalization

Default language
The language to use in the GLPI inter face

Results to display by page

The number of results displayed in the search results list. If a user sets this
higher
than what is speci˝ed in the general setup, then they will be limited to the
general setup's value.

Display the complete name in tree dropdowns

Display the full name of child items in a tree dropdown

Show GLPI ID
Adds the GLPI ID after its name on the item's edit for m

Noti˝cations for my changes

Receive noti˝cations for the actions that the logged in user has done. This does
not apply to the creation of a ticket for which the noti˝cation is systematically
sent (proof of creation).

PDF export font

The font used when generating PDF expor ts

Go to created item after creation

If enabled, the user would be redirected to the edit from of the item after it
gets created. Other wise, they would remain on the new item for m to be able to add
more items.

Date format
Display for mat for dates

Number format
Display for mat for numbers

Display order of surnames/˝rstnames

Display order for a user's ˝rst and last name

Display counters
If enabled, the number of elements will be shown next to some tab names such as the
Items
tab in a Ticket.

CSV delimiter
Character to delimit ˝elds in a CSV expor t

Results to display on home page

The number of items to display in the Ticket, Change, and Problem tables
on the home page. If this parameter is set to 0, only the table titles will be
displayed but you can access their
respective contents by clicking on the name of the table.

Keep devices when purging an item

: If enabled, the components linked to an item that is being deleted can
be preser ved. Other wise, they will be deleted along with the item.
304
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Assist ance

Private followups by default

If enabled, followups are pre-selected to be pr ivate.

Private t asks by default

If enabled, tasks are pre-selected to be pr ivate.

Tasks st ate by default

Pre-selected state for tasks

Pre-select me as a technician when creating a ticket

The logged in user will automatically be assigned to the
ticket while creating it. This only applies to users who can be assigned to
tickets.

Priority colors
De˝ne the colors used in the inter face to di˙erentiate the di˙erent pr ior ity
levels.

Show new tickets on the home page

If the logged in user has the r ight to see all tickets, a table listing all
tickets
with the # New # will be displayed in the
Over view
tab of the home page.

Request sources by default

Pre-selected request source for new tickets

Automatically refresh dat a (tickets list, project kanban) in minutes

: Automatically refresh the infor mation
in the tickets list and Kanban. If set to 0, the automatic refresh is disabled.
Due date progr ession
Allows to de˝ne the colors that will be applied in the prog ress bar of an object.
These di˙erent states depend on the
thresholds set in percent, hours or days.
Dashboards
Con˝gure the default dashboards for the home page (central), assistance module,
assets module, and above the tickets
search results list.
Assets
This tab per mit to con˝gure global parameters for inventor y.
3.2. Modules
305

GLPI User Document ation, Ver sion 10.0

Assets

Enable the ˝nancial and administrative information by default

Applicable for all objects in the inventor y

Software category deleted by the dictionary rules

It is possible to automatically change the categor y of
software deleted by dictionar y r ules. By default they are automatically moved to
the FUSION categor y.

End of ˝scal year

Used in the Management section

Automatic ˝elds (marked by*)

When a template is created, it is possible to add automatically generated ˝elds
from a template. For example, the name of the asset or the inventor y number. The
values of these ˝elds can be
incremented either by entity or globally.

Restrict monitor management

Restrict device management

Restrict phone management

Restrict printer management

When creating a device manually, the user is asked to choose the type of mana-
gement (unitar y or global). A global management only impor ts an element once,
unlike a unitar y management
which impor ts it as many times as it is used. For example, a pr inter shared by
several users or a monitor connec-
ted to a screen switch. Subsequently, a unitar y managed equipment can be switched
to global management
mode. It is possible to restr ict the type of management depending on the
equipment.
Automatically update of the elements r elated to the com puter s
Inter facing with an inventor y tool makes it possible to take an automated
inventor y of the equipment. This inter facing
is possible through the native inventor y feature or a plugin.

When connecting or updating

When connecting a device (that is unit managed) directly to a computer, it is
possible to have infor mation retr ieved from the computer assigned to it such as
the User.
When disconnecting
When disconnecting a device (that is unit managed) from a computer, it is possible
to
remove some of the data in the Computer such as the User.
For example, When the inventor y is ˝rst retr ieved, you can de˝ne that the monitor
connected to the computer will have
the status # Production #. Then, when disconnected, it will take the status #
Available #.
Assist ance
This tab allows management of GLPI assistance par t.
306
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Assist ance
Fig. 12
# image

Step for the hours (minutes)

Amount of minutes between each step for minutes under an hour in duration
dropdowns. Example : 5 minutes shows 5, 10, 15, 20, . . ., 55, 60.

Default ˝le size limit imported by the mails receiver

Maximum size of ˝les to allow to impor t by the
receiver. This should be adjusted alon g with the maximum ˝le size option on the
management tab
and the
max_upload_size
PHP directive.

Default heading when adding a document to a ticket

Allows you to set a default classi˝cation for documents
uploaded to a ticket.

Keep tickets when purging hardware in the inventory

If enabled, the tickets related to an asset being purged
will remain. Other wise, they are purged along with the asset.

Allow anonymous ticket creation (helpdesk.receiver)

Anonymous ticket creation is disabled by default. Ac-
tivating the option is necessar y when using a collector or the anonymous ticket
entr y for m to allow the creation
of tickets by users not recognized by GLPI.

Limit of the schedules for planning

Time range displayed in the planning screen.

By default, a software may be linked to a ticket

Allow associating a software with a ticket by default.

Show personal information in new ticket form (simpli˝ed information)

Display the name, phone number,
and location of the user. If needed, the
Edit
button redirects to the main tab of the user's preferences.

Allow anonymous followups (receiver)

Allows a user not present in GLPI to respond to an email from GLPI.
Matrix of calculus for priority
The pr ior ity de˝nition matr ix allows you to de˝ne the pr ior ity of tickets
according to the level of impact and urgency.
The availability of these levels in the application can also be de˝ned but the
Medium level cannot be deleted.
3.2. Modules
307

GLPI User Document ation, Ver sion 10.0

Manag ement
The only con˝guration parameter available on this page is the size limit for
uploaded documents.
ò
Note
If the
upload_max_˝lesize
PHP directive is lower than what is set here, then
upload_max_˝lesize
will be the limiting
factor. You may also need to ensure the
post_max_size
directive is set at least a little above
upload_max_˝lesize
.
Logs purg e
Log purge con˝guration.
Con˝gure how long to keep histor ical log entr ies base on the type of the entr y
or globally.
The log purge is done by the
PurgeLogs
automatic action.
System
This tab allows you to view a summar y of infor mation about the web ser ver,
con˝gure the proxy infor mation, and to
de˝ne the logging infor mation to be recorded.

Logging level
Each inter nal event of the application is recorded in the logs which are visible
in
Administration
> Logs
.

Logs in ˝les (SQL, email, automatic action. . .)

: It is possible to record cer tain additional events (SQL, noti-
˝cations, automatic action. . .) in ˝les. These ˝les are then available in the
˝les/_log
director y.

Maximum number of automatic actions (run by CLI)

When con˝gur ing automatic actions, it is possible to
deter mine that they will be executed by a system exter nal to GLPI (CLI). By
default, it executes these actions
one by one. It possible to increase the number of executions launched
simultaneously.

SQL replica
Enable to usage of one or more replica databases. The replicas can be fur ther
con˝gured in the
SQL replicas
tab after this option is enabled.
A maintenance mode can be activated to allow a technical op eration such as an
update for example. A maintenance
message is con˝gurable and would show on the login page. In maintenance mode, you
can still access GLPI via
index.
php?skipMaintenance=1
.
In the case GLPI sits behind a proxy, it is necessar y to indica te the infor
mation to allow GLPI to access the Inter net.
This a˙ects the checking of new versions, fetching RSS feeds, etc.
308
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

The following screen lists all the infor mation of GLPI necessar y to repor t a
malfunction to the GLPI development team.
It is prefer red to click the
Copy system infor mation
button which will add a r ich-text version of the system infor mation
tables to your clipboard. This for mat shows up in a cleaner for mat on GitHub than
if you copy it directly.
Security
Secur ity related parameters such as the password secur ity policy and password
expiration policy.
Password security policy
The following options can be con˝gured as par t of the password secur ity policy :

Password secur ity policy validation - The secur ity policy is only enforced if
this is enabled

Password minimum length

Password need digit

Password need uppercase character

Password need lowercase character

Password need symbol

Password expir ation policy
The following options can be con˝gured as par t of the password expiration policy :

Password expiration delay (in days) - Can be set to never to disable password
expiration

Password expiration notice time (in days)

Delay before account deactivation (in days)

Per formances
Displays infor mation related to the di˙erent caching systems used by GLPI
including :

PHP opcode cache - Improves per for mance of the PHP engine when inter preting the
di˙erent PHP ˝les.

User data cache - General-pur pose cache used by GLPI.

Translation cache - Cache used for translations to avoid having to read the locale
˝les for all translations.
You also have the ability to clear the di˙erent caches from here.
The cache systems for user data and translations can be changed or con˝gured from
the
cache :con˝gure
CLI command.
API
API con˝guration parameters and access limitations.
Here you can see/set the URL for the API. This should match your GLPI URL with
/apirest.php
at the end.
There is also a link for the API documentation.
Authentication
There two methods of logging in to the API that can be individually enabled. -
Credentials - Allows the use of a user's
login and password - Exter nal token - Allows the use of a personal token which can
be found on the user's personal
page (Only visible to them)
You can also manage the registered API clients from this tab. Each client is compr
ised of a name, a logging method
(histor ical, logs, or none) and an application token at least. You may also
con˝gure an IP range to limit access to speci˝c
clients.
3.2. Modules
309

GLPI User Document ation, Ver sion 10.0

Im pact analysis
This tab allows you to control which types of items have the Impact analysis
feature enabled.
SQL r eplicas
GLPI can be con˝gured to use replica databases in some cases to improve per for
mance.
This tab is only visible if the option has been enabled in the
system tab
.
To activate the replica management, you just have to ˝ll in the connection
parameters. It is advisable to use a login that
has only read pr ivileges on the database.
You can use several replicates by separating them with a
blank space
. As the result in the con˝g_db_slave.php ˝le,
the dbhost parameter will be an ar ray.
A speci˝c por t can also be added.
.
Avertissement
If you use multiple replicas, the settings will apply to them all.
The SQL replicas will be used in at least the following cases :

The main ser ver cannot be reached. In this case, GLPI will switch to read-only
mode.

Running repor ts to reduce the load on the main ser ver.

It is also possible to use replicas for the search engine depending on the option
chosen.

Never

If synced (all changes)

GLPI will check the synchronization and use the replica if all changes have been
repli-
cated.

If synced (current user changes)

GLPI will check the synchronization and use the replica if all the changes
for the cur rent user have been replicated. If using a read-only account, the
replica will always be used.

If synced or read-only a ccount

GLPI will check the synchronization and use the replica if all changes have
been replicated. If using a read-only account, the replica will always be used.

Always
.
Avertissement
When always using the replica, it is possible that the results will be out of date.
A di˙erent option should be
considered before this one.
ò
Note
The replication con˝guration of your database is not set by GLPI. You still need to
con˝gure that with the appro-
pr iate tools for your database management system.
310
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

GLPI N etwork
Here you can enter your GLPI Network registration key.
External links
Some elements of GLPI can be associated with a set of links to exter nal
applications. These are visible from the
Links
tab of the var ious for ms.
To parameter ize a link, it is possible to use tags which will be replaced by the
values of the element. The tags are :

[LOGIN] : The logged in user's user name

[ID] : The inter nal numer ic ID for the item

[NAME] : The name of the item

[LOCATION] : The name of the item's location

[LOCATIONID] : The inter nal numer ic ID for the item's location

[IP] : The IP address of the item

[MAC] : The MAC address of the item

[NET WORK] : The item's network

[DOMAIN] : The item's domain. If more than one domain is associated with the item,
the ˝rst one is used.

[SERIAL] : The item's ser ial number

[OTHERSERIAL] : The item's inventor y number/asset tag

[USER] : The item's user

[GROUP] : The item's g roup

[FIRSTNAME] : The user's ˝rst name (Only applies to User exter nal links)

[REALNAME] : The user's sur name (Only applies to User exter nal links)

[FIELD :
*
] : If the ˝eld you want is not available as a separate t ag, it may still be
possible to use it by
referencing its internal ˝eld name.
For example, the comment ˝eld would be
[FIELD :comment]
. The ˝eld name is case sensitive and typically
it will need to be all lowercase.
Each link can be associated with one or more element types.
If the content is empty, a simple link will be generated. If content is present, it
is a link to the download of the content
that will be generated.
The link can be opened in a new window according to the
Open in new window
parameter.
A web type link
Create an exter nal protocol link with the name
https ://[IP]
and assign it to the network hardware.
An RDP link
For remote access on computers, create an exter nal protocol link with the name
link with the name
RemoteAccess.rdp
and set the
˝le content
by inser ting the content of an RDP type ˝le and replacing the ip / name / domain
by TAGS like
[IP], [NAME], [DOMAIN].
ò
Note
When using tags from network por ts (IP, MAC), if the hardware has several, then
this will create as many create as
many links as there are por ts. For example, for a machine with 2 di˙erent IP
addresses, 2 links will be displayed.
3.2. Modules
311

GLPI User Document ation, Ver sion 10.0

Remote control through a VN C extension
Some VNC implementations provide an extension that allows to take control of a
computer through a brow-
ser. In general, the por t used is 5900. The cor responding link will be of type
https ://[IP] :5900
or
https ://[NAME].[DOMAIN] :5900
.
Inst all and update plugins
Adding and maintaining extensions (plugins) in GLPI.
.
Avertissement
Before installing or updating a plugin, it is recommended that you per for m a back
up of your GLPI database.
Star ting in GLPI 9.5.0, you can install and update plugins directly from the GLPI
web inter face.
The ˝rst time you go to the plugins page under
Setup > Plugins
, you will be asked if you want to use the marketplace UI
by default or the older plugin list. Regardless of your choice, you can always
switch UIs by clicking the # Marketplace #
and # Plugins # buttons at the top of the page. You may install plugins using both
methods. If a plugin is install through
the marketplace and manually for some reason, the version installed through the
marketplace will be used.
Using the plugin marketplace
To use the marketplace, you will need a GLPI Network registration key. If you are
not paying for a GLPI Network
subscr iption, you can still get a free key from
https:// ser vices.glpi- network.com
. After you get the key, you may enter
it under
Setup > General
on the
GLPI Network
tab.
Finding plugins
In the plugin marketplace UI, click on the
Discover y
tab to view the list of all plugins o˙ered through the marketplace.
These include o˚cial plugins (free and subscr iption) and community plugins. On the
left, you can select a categor y to
˝lter plugins and use the search bar to fur ther limit the results.
Any plugin that has a
GLPI NET WORK
requires a non-free subscr iption. These plugins will also indicate the tier
required such as
BASIC
or
STANDARD
. Each paid tier includes the plugins from the lower tiers.
312
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Inst alling plugins
On the r ight side of each plugin, you should see a button to install it or one or
more er rors explaining why it cannot
be installed. When you ˝nd a plugin available to install, you can click the install
button to automatically download the
latest version available for your GLPI version and install it.
Plugins installed via the marketplace are stored in the
marketplace
folder in the root of your GLPI instance.
After installation, the install button will change to an enable toggle. You will
need to click that button to enable the
plugin after installation.
U pdating plugins
In the marketplace UI on the
Installed
tab, you can see all the plugins cur rently installed.
Similar to installing plugins, there will be an update button showing if an update
is available or one or more er rors if
there is some issue preventing an update. Like with installing plugin, you will
need to re-enable the plugins after an
update.
Manually managing plugins
The main way to discover new plugins is through the
plugin catalog
. Each plugin should have a download link that will
take you to a GitHub page, the GLPI Network Ser vices website (if it is a subscr
iption-only plugin), or some other page
that o˙ers the downloads.
ò
Note
A plugin can have several versions and each version usually suppor ts only cer tain
versions of GLPI so be sure to
download the version of the plugins that are compatible with your version of GLPI.
If you tr y to install or update a
plugin that is not compatible with your GLPI version, it should tell you in the
GLPI web inter face.
After you download the plugin, you will need to extract it to the
plugins
folder in your GLPI director y. The new folder
inside
plugins
should be the # inter nal # name of the plugin. This is an all lowercase identi˝er
containing no spaces.
Inside that folder should be at least two ˝les named
hook .php
and
setup.php
.
Once the plugin is in the
plugins
folder, it will be automatically detected by GLPI and will show up in your plugin
list.
All plugins listed will have a g roup of actions along the r ight side (or a
message indicating why they canno t be installed
or updated). After installing or updating a plugin, you will need to re-enable it.
U ninst alling plugins
When you uninstall a plugin using the uninstall button in the plugin list or in the
marketplace UI, it does not remove
the plugin code and the plugin will still show in the list of plugins to re-
install.
To per manently remove the plugin, it is necessar y to delete the plugin's folder.
After removing the plugin's folder there
should be a new # cleanup # action available for the plugin in GLPI. This will
remove the reference to the plugin from
the database.
3.3
Advanced Con˝gur ation
3.3.1
Using the cache
Infor mation on cache usage is available in Con˝guration / General / System).
Ajouté dans la version 9.2.
3.3. Advanced Con˝gur ation 313
GLPI User Document ation, Ver sion 10.0
Modi˝é dans la version 9.2.1.
If one of the APCu or WinCache cache systems is present on the ser ver, it will be
automatically used by GLPI. The
system is based on Symfony Cache.
The cache makes it possible to improve per for mance on cer tain relatively heavy
operations, such as loading translations,
or calculating entity trees.
There are two distinct caches in GLPI :

The database cache

The translations cache

This distinction makes it possible to avoid stor ing the translation cache on a
network, which could produce too many
requests on the network and ultimately have a negative impact.
Conversely, the database cache should be on the network in case of multiple front-
ends.
In order to allow you to re˝ne the settings, or to use another cache system, a
manual solution is proposed. To take
advantage of it, add to the
glpi_configs
table a
cache_db
and/or
cache_trans
key for the
core
context and adapt
the value according to what you want.
ò
Note
If the goal is to disable either of these caches, create the key in the table, but
leave the value blank.
{
"adapter"
:
"apcu"
}
{
"adapter"
:
"redis"
,
"options"
:{
"server"
:{
"host"
:
"127.0.0.1"
}}}
Refer to the
Config::getCache()
method and
Symfony Cache documentation
for more infor mation.
.
Avertissement
If you install several instances of GLPI on the same ser ver, the cache namespace
must be unique per instance, which
was not the case in GLPI before version 9.2.4.
If you have speci˝ed your own namespace in the con˝guration, make sure that it is
unique on each instance !
If your version of GLPI is earlier than 9.2.4, you will need to add the namespace
in the cache con˝guration of each
of your instances.
3.3.2
OPCache
OPCache stores pre-compiled PHP ˝les in memor y, which improves per for mance. The
only thing to do is to install it
on your PHP instance and con˝gure it (the default con˝guration should be ˝ne in the
vast major ity of cases).
However, on instances that could be heavily used, it may be useful not to include
font ˝les for PDFs in this cache.
Indeed, they take up a lot of space, and the gain is relatively minimal.
In order to exclude the font ˝les from the cache, all you have to do is enter their
full path in a blacklist ˝le for opcache.
The path to this ˝le is deter mined by the con˝guration diective
opcache.blacklist_filename
(
/etc/php.d/
opcache-glpi.blacklist
for example under Fedora). If your GLPI instance is in the folder
/var/www/
, the path to
exclude will be
/var/www/html/glpi/glpi-9.2.1/vendor/tecnickcom/tcpdf/fonts/
.
Of course, the location of the con˝guration ˝le and the path to the fonts should be
adapted according to your system
and your type of installation.
314
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

3.3.3
GLPI St atus Monitoring
GLPI contains a helpful endpoint for monitor ing its health at
/status.php
and the
glpi :system :status
CLI command. The
/status.php
endpoint does not require you to be logged in and therefore only shows basic status
infor mation. Sensitive
infor mation like the GLPI version and plugin names and versions (could be used to
identify vulerabilities) are not
shown. The di˙erence with the CLI command though is that since it isn't accessible
from the web, you can optionally
retr ieve pr ivate infor mation too.
Ser vices
The status of GLPI is separated into multiple # ser vices #. These ser vices can be
listed using the
glpi :sys-
tem :list_ser vices
CLI command.
A non exhaustive list of services available :
db - Database (Main and replicants)

cas - Central Authentication Ser ver

ldap - LDAP/Active Director y

imap - Email Ser ver(s)

mail_collectors - Email collectors

crontasks - Automatic actions

˝lesystem - Filesystem access

plugins - Plugins status

St atus Endpoint
By default, the
/status.php
endpoint provides a plain-text output of the public status infor mation. The plain-
text output
is deprecated in favor of the JSON for mat, but it remains the default for
backwards compatibility.
The following for mats are cur rently suppor ted and can be chosen by using the
HTTP
Accept
header or the
for mat
quer y
parameter. When using the
for mat
parameter, the shor t for mat identi˝er should be used.

JSON

HTTP Accept - application/json

For mat parameter - json

Plain-text (deprectated)

HTTP Accept - text/plain

For mat parameter - plain

You can ˝lter the output to a speci˝c ser vice using the
ser vice
quer y parameter.
CLI Command
Similar to the
/status.php
endpoint, the CLI command
glpi :system :status
only shows the public status infor mation by
default. However, since this tool is not available from the web inter face, you may
add the
-p
or
#private
option to see
all of the status infor mation.
By default, it uses the plain-text for mat for its output for backwards
compatibility, but this is deprecated. The same
for mats are suppor ted as listed above in the # Status Endpoint # section and the
shor t identi˝er can be passed in the
-f
or
#for mat
option.
You can ˝lter the output to a speci˝c ser vice using the
-s
or
#ser vice
option.
3.3.4
Override GLPI locales
GLPI uses the
gettext
tool to manage its translations. You can over r ide the default. This is the
prefer red method rather
than editing the or iginal po ˝les and r isk losing your changes when updating
GLPI.
To do so, you need to create a ˝le named
filename.po
in the
files/_locales/core/
director y. You can also create
over r ides for plugins with the same method in
files/_locales/pluginkey/
director y where
pluginkey
matches
the plugin folder name.
3.3. Advanced Con˝gur ation 315

GLPI User Document ation, Ver sion 10.0

ò
Note
Depending on your GLPI con˝guration, the
_locales
director y can be located elsewhere (if you provided a
local_define.php
˝le with a
GLPI_LOCAL_I18N_DIR
constant). It's possible to have multiple ˝les, to manage
several languages for example.
The ˝le must be a valid
gettext
˝le. You can use
Poedit
to create it.
# Override PO file
#
msgid
""
msgstr
""
"
Project-Id-Version:
PACKAGE VERSION\n"
"
Report-Msgid-Bugs-To:
\n"
"
POT-Creation-Date:
2019-04-13 10:43+0200\n"
"
PO-Revision-Date:
2019-04-13 10:43+0200\n"
"
Last-Translator:
Automatically generated\n"
"
Language-Team:
none\n"
"
Language:
en_GB\n"
"
MIME-Version:
1.0\n"
"
Content-Type:
text/plain; charset=UTF-8\n"
"
Content-Transfer-Encoding:
8bit\n"
"
Plural-Forms:
nplurals=2; plural=(n != 1);\n"
msgid
"Login"
msgstr
"Login from local gettext"
msgid
is the source str ing,
msgstr
is the translation. You can ˝nd the cor rect source sentences to use in the
locales/
glpi.pot
˝le.
Next you need to compile your .po ˝le into a .mo ˝le readable by GLPI. To do so,
you can use the following command :
$ cd files/_locales/core/
$ msgfmt -o filename.mo filename.po
Finally, GLPI uses a cache system to avoid loading MO ˝les at each request. You
need to clear the cache to see your
changes. To do so, in Debug mode , go to # Setup > General #, # Per for mance # tab
and click on # Reset # but-
ton on the # Translation cache # section. If you have command-line access, you may
also clear this cache using the
glpi :cache :clear
CLI command. If you clear the cache with the CLI command, make sure you r un the
command as
the web ser ver user.
3.4
GLPI command-line inter face
GLPI includes a CLI tool to help you to manage your GLPI instance. This inter face
is provided by the
bin/console
scr ipt which can be r un from the root of your GLPI director y.
Each command may have zero or more arguments or options. Arguments are positional
pieces of infor mation while
options are not and are pre˝xed by one or two hyphens
316
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

3.4.1
glpi :assets :cleansof twar e
Aliases :
assets :cleansof tware
Description
Remove software versions with no installation and software with no version
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#max
-m
Max items to handle in one execution
Yes
500
No
No
3.4.2
glpi :build :com pile_scss
Aliases :
build :compile_scss
Description
Compile SCSS ˝le.
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Nega-
table
#˝le
-f
File to compile (compile all SCSS ˝les by default)
No
[]
Yes
Yes
#dr y-
r un
Simulate compilation without actually save compiled CSS ˝les
No
No
No
3.4.3
glpi :cache :clear
Aliases :
cache :clear, glpi :system :clear_cache, system :clear_cache
Description
Clear GLPI cache.
Arguments/Options
There are no arguments for this command
Options :
3.4. GLPI command-line inter face 317

GLPI User Document ation, Ver sion 10.0

Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#context
-c
Cache context to clear (i.e. #core# or #plugin :plugin_name#). All contexts are
cleared by default.
Yes
[]
Yes
No
3.4.4
glpi :cache :con˝gur e
Aliases :
cache :con˝gure
Description
De˝ne cache con˝guration
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#context
Cache context (i.e. #core# or #plugin :plugin_name#)
Yes
core
No
No
#dsn
Cache system DSN
Yes
[]
Yes
No
#use-default
Unset cache con˝guration to use default ˝lesystem cache for
given context
No
No
No
#skip-
connection-
checks
Skip connection checks
No
No
No
Help
Valid cache systems are : <comment>Memcached</comment>, <comment>Redis
(TCP)</comment>, <com-
ment>Redis (TLS)</comment>.
Memcached DSN for mat : memcached ://[user :pass@][ip|host|socket[ :por t]][ ?
weight=int] Redis
(TCP) DSN for mat : redis ://[pass@][ip|host|socket[ :por t]][/db-index] Redis
(TLS) DSN for mat : re-
diss ://[pass@][ip|host|socket[ :por t]][/db-index]
Cache namespace can be use to ensure either separation or shar ing of multiple GLPI
instances data on same cache
system.
Usag e

glpi :cache :con˝gure #use-default

glpi :cache :con˝gure #dsn=memcached ://cache1.glpi-project.org

#dsn=memcached ://cache2.glpi-project.org

glpi :cache :con˝gure #dsn=redis ://redis.glpi-project.org :6379/glpi

318
Chapitr e 3. Sommair e
GLPI User Document ation, Ver sion 10.0
3.4.5
glpi :cache :debug
Aliases :
cache :debug
Description
Debug GLPI cache.
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Nega-
table
#key
-k
Cache key to debug.
Yes
[]
Yes
No
#context
-c
Cache context to clear (i.e. #core# or #plugin :plugin_name#).
Yes
core
No
No
3.4.6
glpi :cache :set_namespace_pr e˝x
Aliases :
cache :set_namespace_pre˝x
Description
De˝ne cache namespace pre˝x
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
pre˝x
Namespace pre˝x
Yes
There are no options for this command
3.4.7
glpi :con˝g :set
Aliases :
con˝g :set
Description
Set con˝guration value
Arguments/Options
Arguments (in order) :
Name
Description
Req ui-
red
De-
fault
key
Con˝guration key
Yes
va-
lue
Con˝guration value (ommit argument to be prompted for value)
Yes
3.4. GLPI command-line inter face 319

GLPI User Document ation, Ver sion 10.0

Options :
Name
Shor tcut
Description
Req uired
Default
Ar-
ray
Negatable
#context
-c
Con˝guration context
Yes
core
No
No
3.4.8
glpi :dat abase :chec k_schema_integrity
Aliases :
db :check_schema_integrity, glpi :database :check , db :check
Description
Check for schema di˙erences between cur rent database and installation ˝le.
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#str ict
Str ict compar ison of de˝nitions
No
No
No
#check-all-mig rations
Check tokens related to all databases mig rations.
No
No
No
#check-innodb-
mig ration
Check tokens related to mig ration from # MyISAM # to # In-
noDB #.
No
No
No
#check-timestamps-
mig ration
Check tokens related to mig ration from # datetime # to # times-
tamp #.
No
No
No
#check-utf8mb4-
mig ration
Check tokens related to mig ration from # utf8 # to # utf8mb4 #.
No
No
No
#check-dynamic-row-
for mat-mig ration
Check tokens related to # DYNAMIC # row for mat mig ration.
No
No
No
#check-unsigned-keys-
mig ration
Check tokens related to mig ration from signed to unsigned in-
tegers in pr imar y/foreign keys.
No
No
No
3.4.9
glpi :dat abase :con˝gur e
Aliases :
db :con˝gure
Description
De˝ne database con˝guration
Arguments/Options
There are no arguments for this command
Options :
320
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#db-host
-H
Database host
No
lo-
cal-
host
No
Yes
#db-name
-d
Database name
Yes
No
No
#db-
password
-p
Database password (will be prompted for value if option passed wi-
thout value)
No
No
Yes
#db-por t
-P
Database por t
No
No
Yes
#db-user
-u
Database user
Yes
No
No
#recon˝gure
-r
Recon˝gure database, over r ide con˝guration ˝le if it already exists
No
No
No
#str ict-
con˝guration
Use str ict con˝guration, to enforce war nings tr igger ing on depreca-
ted or discouraged usages
No
No
No
#default-
language
-L
Default language of GLPI
No
en_GB
No
Yes
#force
-f
Force execution of installation, over r iding existing database
No
No
No
#enable-
telemetr y
Allow usage statistics sending to Telemetr y ser vice (
https://
telemetr y.glpi- project.org
)
No
No
No
#no-
telemetr y
Disallow usage statistics sending to Telemetr y ser vice (
https://
telemetr y.glpi- project.org
)
No
No
No
3.4.12
glpi :dat abase :update
Aliases :
db :update
Description
Update database schema to new version
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#allow-
unstable
-u
Allow update to an unstable version
No
No
No
#force
-f
Force execution of update from v-1 version of GLPI even if schema did
not changed
No
No
No
#enable-
telemetr y
Allow usage statistics sending to Telemetr y ser vice (
https:// telemetr y.
glpi- project.org
)
No
No
No
#no-
telemetr y
Disallow usage statistics sending to Telemetr y ser vice (
https://
telemetr y.glpi- project.org
)
No
No
No
322
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

3.4.13
glpi :ldap :synchronize_user s
Aliases :
ldap :sync
Description
Synchronize users against LDAP ser ver infor mation
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#only-
create-
new
-
c
Only create new users
No
No
No
#only-
update-
existing
-
u
Only update existing users
No
No
No
#ldap-
ser ver-
id
-
s
Synchronize only users attached to this LDAP ser ver
No
[]
Yes
Yes
#ldap-
˝lter
-
f
Filter to apply on LDAP search
No
No
Yes
#begin-
date
Begin date to apply in # modifyTimestamp # ˝lter (see
http:// php.net/ manual/ en/ datetime.
for mats.php
for suppor ted for mats)
No
No
Yes
#end-
date
End date to apply in # modifyTimestamp # ˝lter (see
http:// php.net/ manual/ en/ datetime.
for mats.php
for suppor ted for mats)
No
No
Yes
#deleted-
user-
strategy
-
d
Force strategy used for deleted users (cur rent con˝gured action : # 1 #) Possible
values are :

0 : Preser ve

1 : Put in trashbin

2 : Withdraw dynamic author izations and g roups

3 : Disable

4 : Disable + Withdraw dynamic author izations and g roups

No
No
Yes
#restored-
user-
strategy
-
r
Force strategy used for restored users (cur rent con˝gured action : # 0 #) Possible
values are :

0 : Do nothing

1 : Restore (move out of trashbin)

3 : Enable
No
No
Yes
3.4.14
glpi :maintenance :disable
Aliases :
maintenance :disable
Description
Disable maintenance mode
3.4. GLPI command-line inter face 323

GLPI User Document ation, Ver sion 10.0

3.4.15
glpi :maintenance :enable
Aliases :
maintenance :enable
Description
Enable maintenance mode
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#text
-t
Text to display dur ing maintenance
No
No
Yes
3.4.16
glpi :marketplace :download
Aliases :
marketplace :download
Description
Download plugin from the GLPI marketplace
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
plugins
The plugin key
Yes
[]
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Nega-
table
#force
-f
Force download even if the plugin is already downloaded
No
No
No
3.4.17
glpi :marketplace :info
Aliases :
marketplace :info
Description
Get infor mation about a plugin
324
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
plugin
The plugin key
Yes
There are no options for this command
3.4.18
glpi :marketplace :search
Aliases :
marketplace :search
Description
Search GLPI marketplace
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
ter m
The search ter m
No
There are no options for this command
3.4.19
glpi :migr ation :appliances_plugin_to_cor e
Aliases :
None
Description
Mig rate Appliances plugin data into GLPI core tables
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#skip-er rors
-s
Do not exit on impor t er rors
No
No
No
3.4.20
glpi :migr ation :build_missing_timest am ps
Aliases :
None
3.4. GLPI command-line inter face 325

GLPI User Document ation, Ver sion 10.0

Description
Set missing
date_creation
and
date_mod
values using log entr ies.
3.4.21
glpi :migr ation :dat abases_plugin_to_cor e
Aliases :
None
Description
Mig rate Databases plugin data into GLPI core tables
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#skip-er rors
-s
Do not exit on impor t er rors
No
No
No
3.4.22
glpi :migr ation :domains_plugin_to_cor e
Aliases :
None
Description
Mig rate Domains plugin data into GLPI core tables
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#skip-er rors
-s
Do not exit on impor t er rors
No
No
No
3.4.23
glpi :migr ation :dynamic_row_format
Aliases :
None
Description
Conver t database tables to # Dynamic # row for mat (required for # utf8mb4 #
character suppor t).
3.4.24
glpi :migr ation :myisam_to_innodb
Aliases :
None
326
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Description
Mig rate MyISAM tables to InnoDB
3.4.25
glpi :migr ation :r ac ks_plugin_to_cor e
Aliases :
None
Description
Mig rate Racks plugin data into GLPI core tables
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#ignore-
other-
elements
-i
Ignore # PluginRacksOther # models and elements
No
No
No
#skip-
er rors
-s
Do not exit on impor t er rors
No
No
No
#tr uncate
-t
Remove existing core data
No
No
No
#update-
plugin
-u
Run Racks plugin update (you need version 1.8.0 ˝les to do this)
No
No
No
#without-
plugin
-
w
Enable mig ration without plugin ˝les (we cannot validate that plugin data
are compatible with suppor ted 1.8.0 version)
No
No
No
3.4.26
glpi :migr ation :timest am ps
Aliases :
None
Description
Conver t # datetime # ˝elds to # timestamp # to use timezones.
3.4.27
glpi :migr ation :unsigned_keys
Aliases :
None
Description
Mig rate pr imar y/foreign keys to unsigned integers
3.4.28
glpi :migr ation :utf8mb4
Aliases :
None
3.4. GLPI command-line inter face 327

GLPI User Document ation, Ver sion 10.0

Description
Conver t database character set from # utf8 # to # utf8mb4 #.
3.4.29
glpi :plugin :activate
Aliases :
plugin :activate
Description
Activate plugin(s)
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
director y
Plugin director y
No
[]
Options :
Name
Shor tcut
Description
Req uired
Default
Ar-
ray
Negatable
#all
-a
Run command on all plugins
No
No
No
3.4.30
glpi :plugin :deactivate
Aliases :
plugin :deactivate
Description
Deactivate plugin(s)
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
director y
Plugin director y
No
[]
Options :
Name
Shor tcut
Description
Req uired
Default
Ar-
ray
Negatable
#all
-a
Run command on all plugins
No
No
No
328
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

3.4.31
glpi :plugin :inst all
Aliases :
plugin :install
Description
Run plugin(s) installation scr ipt
Arguments/Options
Arguments (in order) :
Name
Description
Req uired
Default
director y
Plugin director y
No
[]
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#all
-
a
Run command on all plugins
No
No
No
#pa-
ram
-
p
Additionnal parameters to pass to the plugin install hook function

# -p foo # will set # foo # param value to tr ue

# -p foo=bar # will set # foo # param value to # bar #

No
[]
Yes
Yes
#user-
name
-
u
Name of user used dur ing installation scr ipt (among other things to set plugin
admin
r ights)
Yes
No
No
#force
-
f
Force execution of installation, even if plugin is already installed
No
No
No
Usag e

glpi :plugin :install -p foo=bar -p force myplugin

3.4.32
glpi :rules :process_sof twar e_categor y_rules
Aliases :
r ules :process_sof tware_categor y_r ules
Description
Process software categor y r ules
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#all
-a
Process r ule for all software, even those having already a de˝ned categor y
No
No
No
3.4. GLPI command-line inter face 329

GLPI User Document ation, Ver sion 10.0

3.4.33
glpi :rules :r eplay_dictionnar y_rules
Aliases :
r ules :replay_dictionnar y_r ules
Description
Replay dictionnar y r ules on existing items
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#dic-
tion-
nar y
-
d
Dictionnar y to use. Possible values are : CableType, ComputerModel, ComputerType,
DatabaseIns-
tanceType, GlpiSocketModel, ImageFor mat, ImageResolution, Manufacturer,
MonitorModel, Monitor-
Type, NetworkEquipmentModel, NetworkEquipmentType, OperatingSystem,
OperatingSystemArchi-
tecture, OperatingSystemEdition, OperatingSystemKer nel, OperatingSystemKer
nelVersion, Operating-
SystemSer vicePack, OperatingSystemVersion, Per ipheralModel, Per ipheralType,
PhoneModel, Phone-
Type, Pr inter, Pr interModel, Pr interType, Software
Yes
No
No
#manufacturer-
id
-
m
If option is set, only items having given manufacturer ID will be processed. Cur
rently only available for
Software dictionar y.
Yes
No
No
3.4.34
glpi :security :chang e_key
Aliases :
None
Description
Change password storage key and update values in database.
3.4.35
glpi :system :chec k_r eq uir ements
Aliases :
system :check_requirements
Description
Check system requirements
3.4.36
glpi :system :list_ser vices
Aliases :
system :list_ser vices
Description
List system ser vices
3.4.37
glpi :system :st atus
Aliases :
system :status
330
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Description
Check system status
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#for-
mat
-f
Output for mat [plain or json]
No
plain
No
Yes
#pr i-
vate
-p
Status infor mation publicity. Pr ivate status infor mation may contain potentially
sen-
sitive infor mation such as version infor mation.
No
No
No
#ser-
vice
-s
The ser vice to check or all
No
all
No
Yes
3.4.38
glpi :t ask :unloc k
Aliases :
task :unlock
Description
Unlock automatic tasks
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Ne-
ga-
table
#all
-a
Unlock all tasks
No
No
No
#cycle
-c
Execution time (in cycles) from which the task is considered as stuck (delay =
task frequency * cycle)
No
No
Yes
#de-
lay
-d
Execution time (in seconds) from which the task is considered as stuck (default :
1800)
No
No
Yes
#task
-t
Itemtype : :name of task to unlock (e.g : # MailCollector : :mailgate #)
No
[]
Yes
Yes
3.4.39
glpi :tools :chec k_dat abase_keys
Aliases :
tools :check_database_keys
Description
Check database for missing and er rounous keys.
3.4. GLPI command-line inter face 331

GLPI User Document ation, Ver sion 10.0

Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Req ui-
red
De-
fault
Ar-
ray
Nega-
table
#detect-misnamed-keys
Detect misnamed keys
No
No
No
#detect-useless-keys
Detect misnamed keys
No
No
No
3.4.40
glpi :tools :chec k_dat abase_schema_consistency
Aliases :
tools :check_database_schema_consistency
Description
Check database schema consistency.
3.4.41
glpi :tools :delete_orphan_logs
Aliases :
tools :delete_or phan_logs
Description
Delete or phan logs
Arguments/Options
There are no arguments for this command
Options :
Name
Shor t-
cut
Description
Re-
q ui-
red
De-
fault
Ar-
ray
Nega-
table
#dr y-
r un
Simulate the command without actually delete anything
No
No
No
3.5
Glossar y
Accepted
State of a demand which has been validated by an approver.
Accredit ation
Author ization to per for m a set of actions on several entities, given by r ights
attr ibution process.
Actions
Grouping in a list of available handling of GLPI objects.
Active Directory service
Director y ser vice compatible with
LDAP director y
, provided by Microsoft. Also known as
AD
.
Adaptive rule
Rule in which at least one action is the result of a regular expression de˝ned in a
cr iter ia.
332
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Administrative closing
Modi˝cation of a ticket status to closed (manually or automatically).
Alert threshold
Minimal value from which an aler t is tr iggered.
Asset
Gener ic ter m for an element that can be inventor ied and managed in GLPI.
Automatic action
Process for regular actions tr igger ing, either inter nal to GLPI or exter nal
(Unix cron, Windows planned tasks. . .).
Automatic closing
GLPI inter nal process that closes unresolved tickets after a given time.
Booking
Element that is booked for a given per iod.
Bookmark
Stored link to a GLPI page that allows to access the page quickly.
Budget
Accounting operation that g roups all provisional expenses and receipts.
Cartridge
Consumable used by a pr inter and speci˝cally managed in GLPI.
Case
Physical element that contains a computer's components (motherboard, processor,
disk. . .).
Closed (ticket)
Status of a ticket whose solution has been approved by the ticket issuer or that
has been close automatically.
Collector
Functionality of GLPI that allows to create tickets or followup by impor ting
messages from a mailbox.
Connection (network)
Link between two network por ts.
Cont act
Referent person linked to a supplier.
Contract
Financial document linked to assets and to suppliers.
Controller
Device that inter faces with other per ipheral device.
Criteria
Element or patter n used by search engines to select an infor mation or used by r
ules engines and dictionar ies to
per for m actions.
Default pro˝le
Pro˝le attr ibuted by the application in the absence of par ticular settings (r
ules, manual attr ibution. . .).
Depreciation type
Character istic of depreciation which balance can be linear or declining.
Dictionary
Set of r ules that allow to modify GLPI data.
Direct connection
Physical link between a computer and another asset.
Document
Element that de˝nes a link and/or store a ˝le and that can be associated to other
objects of GLPI.
Domain
Group of assets connected to a network.
3.5. Glossar y
333

GLPI User Document ation, Ver sion 10.0

Dropdown
Customizable dropdown list used in GLPI and plugins.
Entity
Organizational object allowing to par tition view and action scope of users.
Express renewal
The contract is renewed only if both par ties ag ree for its renewal (opposite to
tacit renewal).
External link
Link displayed on an asset for m in GLPI and built dynamically using the asset
data.
Financial information
Data for invoicing and war ranty.
Followup
Exchange between a ticket issuer and the persons in charge of it.
FQDN
A
FQDN
(Fully quali˝ed domain name) is a fully quali˝ed domain name.
For example :
www.glpi-project.org
,
forge.glpi-project.org
. . .
Frequently Asked Questions (FAQ)
Speci˝cally in GLPI, selection of elements of the knowledge base that can be
provided independently, for
example ar ticles that are made accessible to users having only access to the
simpli˝ed inter face.
Global management
Management mode in which a unique inventor y object can be connected to several
computers.
Global note
Public note that is also visible from sub-entities.
Global right
Per mission on objects that are not linked to an entity.
Global view
In a GLPI menu, display of columns in a list that is common to all users.
Group
Grouping of users.
Grouping
Action of merging similar elements of distinct entities into the parent entity.
Hive
Entr y in Windows registr y.
ICAL (ICalendar)
Calendar impor t/expor t for mat.
ID
Technical identi˝er of an element.
Identi˝er
Connection name of a user (login).
IMAP/POP
IMAP
(Inter net Message Access Protocol) and
POP
(Post O˚ce Protocol) are messaging protocols allowing to
retr ieve mail messages.
Impact
Measure of the e˙ect of an incident, problem or change in business process.
In progress (attributed) (Ticket)
Status of a ticket that is attr ibuted to a technician or a g roup of technicians.
In progress (planned) (Ticket)
Status of a ticket that is attr ibuted to a technician or a g roup of technicians
and for which an action is planned.
334
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Incident
Unplanned inter r uption or quality decrease of a ser vice.
Intervention
Action of a technician to solve an incident.
Knowledge base
Database allowing to gather, analyze, store and share knowledge and infor mation
inside an organization.
Label FQDN
A
FQDN
is composed of labels separated by dots (#
.
#).
For example,
www.glpi-project.org
is composed of labels
www
,
glpi-project
and
org
.
A computer name is composed of a label and the name of the domain it belongs to,
for example
www
name in
domain
glpi-project.org
.
In GLPI, labels are compliant with section 2.1 of RFC 1123.
LDAP directory
Director y ser vice using the
LDAP protocol
(Lightweight Director y Access Protocol). Allows in par ticular to
store user accounts.
Local right
Per mission applicable to a given scope (entity).
Location
Name in GLPI allowing geog raphical localization of an asset.
Logs
List of events occur r ing dur ing use of GLPI application.
Mail domain
Par t of a mail adress that is after character
@
.
Manufacturer
Company producing a hardware.
Mount point
Director y from which the data contained in a par tition can be accessed.
Network
Name de˝ning the connection type (inter net, local. . .).
Network port
Network inter face that can be vir tual or physical.
Networks
Hardwares providing interconnection of computer equipments.
New (ticket)
Default status of a ticket.
Path
Address allowing to localize an element in a tree str ucture.
Pattern
Character str ing used for compar ison in a cr iter ia.
PDU
Power Distr ibution Unit.
Pending (Ticket)
Status of a ticket which processing is temporar ily suspended (does not impact
processing time).
Personal note
Note visible only by its wr iter.
Personal view
In a GLPI menu, display of columns in a list that is speci˝c to a user.
3.5. Glossar y
335

GLPI User Document ation, Ver sion 10.0

Planning
Scheduling of a task in time scale.
Plugin
GLPI extension that allows to add functionalities and/or to modify application
behaviors.
Power supply
Bloc providing electr ic cur rent to the components of a computer.
Preferences
Personal parameters of a user.
Priority
Scale that identi˝es the relative impor tance of a ticket and that results from
impact and urgency.
Private
Element that is visible only by its wr iter (bookmark, note. . .).
Pro˝le
Set of r ights.
Provider
Legal str ucture toward which a contractual relation can be established (purchase,
contract. . .).
Public
Element that is visible by all author ized users of an entity.
Public note
Note that is visible by all users of the note's entity.
Purge
Per manent deletion of elements placed in the trash bin.
Recursivity
Proper ty of an object belonging to an entity that makes it visible from sub-
entities.
Refused
State of a demand that has been invalidated.
Registered user
Person having an accreditation allowing to connect to GLPI.
Regular expression
Character str ing (often called patter n) that descr ibes a set of accepted str
ings according to a well-de˝ned syntax.
Replicate (MySQL)
MySQL database used by GLPI if main database is not available.
Report
Document that sums up GLPI data.
Requester
Person at the or igin of an incident ticket or a ser vice request.
Restoration
Recover y of an element of the trash bin.
Right
Author ization of a user for a given action.
Root entity
First entity of GLPI entities tree str ucture, that is always present even if no
other entity is de˝ned and that cannot
be deleted.
Rule
List of cr iter ia that tr ig a list of actions if cr iter ia are satis˝ed.
Saved search
Recording of GLPI search engine state that allows to store and per for m again the
search.
336
Chapitr e 3. Sommair e

GLPI User Document ation, Ver sion 10.0

Service
General action of GLPI listed in the events.
Simpli˝ed inter face
GLPI user inter face that gives access to a reduced set of functionalities and that
targets end users (opposite to
standard inter face
).
SLA
SLA (for Ser vice-Level Ag reement) is a contract between a ser vice provider and a
client that de˝nes the re-
quested quality of ser vice and the responsibilities in case of failure.
Solved (ticket)
Ticket state when a technical solution was provided for an incident.
SSO
Unique authentication system (
SSO
(Single Sign On)).
St andard inter face
GLPI user inter face that gives access to all functionalities (opposite to
simpli˝ed inter face
).
St atistics
Summar y of GLPI data linked to tickets.
St atus
State of an asset or of a ticket, belonging to its life cycle.
Sub-entity
Child entity of an entity ; on a for m, indicates recursivity status.
Subject
Title or question of an element of the knowledge base.
Supervisor
Person in charge of a g roup of users.
Tacit renewal
The contract is renewed automaticaly if none of the par ties declares its will to
break it.
Tagged VLAN
A tagged
VLAN
(Vir tual Local Area Network) is a
VL AN
which tag is transmited in network frame (see
802.1Q
).
Task
Action cor responding to a technical operation that can be planned.
Technician
User in charge of tickets processing.
Template
Reusable model of object containing prede˝ned ˝eds and allowing easier user entr y.
Ticket
GLPI object representing an incident or a ser vice request.
Tier type
Categor y of providers.
Transfer
Action of moving an object from one entity to another.
Trash bin
Container of elements deleted by users. Similar to the trash bin in a desktop
environment, it is an inter mediate
state before purge.
Tree
Hierarchical organization of data using a tree str ucture.
Unit ary management
Management mode in which an inventor y object can be connected to only one
computer.
3.5. Glossar y
337

GLPI User Document ation, Ver sion 10.0

Urgency
Cr iter ia de˝ned by the requester that speci˝es for a ticket the desired
resolution speed.
User
User of an asset that is not registered in GLPI user base.
Validation
Action of author izing a ticket processing.
Validator
Person per for ming the validation of a ticket.
VCard
Vir tual visit card.
Virtual network port
A vir tual network por t is a por t which does not cor respond to a physical
network hardware.
VLAN
VLAN
: Vir tual Local Network.
Volume
Storage area attached to a computer.
Webcal
Exchange for mat for calendar data.
338
Chapitr e 3. Sommair e

CHAPITRE
4
Licence de cette documentation
Cette documentation est distr ibuée sous les ter mes de la
Creative Commons License Attr ibution-ShareAlike 3.0 France
(CC BY-SA 3.0 FR)
.
Pour les ter mes complets de la licence, veuillez vous référer à
https:// creativecommons.org/ licenses/ by- sa/ 3.0/ fr/
legalcode
.
Vous êtes libre de :

Par tager - copier et redistr ibuer cette documentation sur n'impor te quel suppor
t ou for mat

Adapter - remixer, transfor mer et générer cette documentation à n'impor te quelle

˝n, même commercialement.
Le concédant ne peut pas révoquer ces liber tés tant que vous respectez les ter mes
de la licence.
Aux ter mes suivants :

Attr ibution Vous devez donner le crédit appropr ié, four nir un lien vers la
licence et indiquer si des modi˝-
cations on t été appor tées. Vous pouvez le faire de toute manière raisonnable,
mais en aucun cas suggérant que
le concédant vous approuve ou approuve votre utilisation.

Par tage dans les mêmes conditions Si vous remixez, transfor mez ou générez cette
documentation, vous devez
distr ibuer vos contr ibutions sous la même licence que l'or iginal.
Aucune restr iction supplémentaire Vous ne pouvez pas appliquer des ter mes jur
idiques ou des mesures technolo-
giques qui empêchent légalement les autres de faire tout ce que la licence autor
ise.
339

GLPI User Document ation, Ver sion 10.0

340 Chapitr e 4. Licence de cette document ation

Index
A
Accepted
,
332
Accreditation
,
332
Actions
,
332
Active Directory service
,
332
Adaptive rule
,
332
Administrative closing
,
333
Alert threshold
,
333
Asset
,
333
Automatic action
,
333
Automatic closing
,
333
B
Booking
,
333
Bookmark
,
333
Budget
,
333
C
Cartridge
,
333
Case
,
333
Closed
(
ticket
),
333
Collector
,
333
Connection
(
network
),
333
Contact
,
333
Contract
,
333
Controller
,
333
Criteria
,
333
D
Default profile
,
333
Depreciation type
,
333
Dictionary
,
333
Direct connection
,
333
Document
,
333
Domain
,
333
Dropdown
,
334
E
Entity
,
334
Express renewal
,
334
External link
,
334
F
Financial information
,
334
Followup
,
334
FQDN
,
334
Frequently Asked Questions
(
FAQ
),
334
G
Global management
,
334
Global note
,
334
Global right
,
334
Global view
,
334
Group
,
334
Grouping
,
334
H
Hive
,
334
I
ICAL
(
ICalendar
),
334
ID
,
334
Identifier
,
334
IMAP/POP
,
334
Impact
,
334
In progress (attributed)
(
Ticket
),
334
In progress (planned)
(
Ticket
),
334
Incident
,
335
Intervention
,
335
K
Knowledge base
,
335
L
Label FQDN
,
335
LDAP directory
,
335
Local right
,
335
Location
,
335
341

GLPI User Document ation, Ver sion 10.0

Logs
,
335
M
Mail domain
,
335
Manufacturer
,
335
Mount point
,
335
N
Network
,
335
Network port
,
335
Networks
,
335
New
(
ticket
),
335
P
Path
,
335
Pattern
,
335
PDU
,
335
Pending
(
Ticket
),
335
Personal note
,
335
Personal view
,
335
Planning
,
336
Plugin
,
336
Power supply
,
336
Preferences
,
336
Priority
,
336
Private
,
336
Profile
,
336
Provider
,
336
Public
,
336
Public note
,
336
Purge
,
336
R
Recursivity
,
336
Refused
,
336
Registered user
,
336
Regular expression
,
336
Replicate
(
MySQL
),
336
Report
,
336
Requester
,
336
Restoration
,
336
Right
,
336
Root entity
,
336
Rule
,
336
S
Saved search
,
336
Service
,
337
Simplified interface
,
337
SLA
,
337
Solved
(
ticket
),
337
SSO
,
337
Standard interface
,
337
Statistics
,
337
Status
,
337
Sub-entity
,
337
Subject
,
337
Supervisor
,
337
T
Tacit renewal
,
337
Tagged VLAN
,
337
Task
,
337
Technician
,
337
Template
,
337
Ticket
,
337
Tier type
,
337
Transfer
,
337
Trash bin
,
337
Tree
,
337
U
Unitary management
,
337
Urgency
,
338
User
,
338
V
Validation
,
338
Validator
,
338
VCard
,
338
Virtual network port
,
338
VLAN
,
338
Volume
,
338
W
Webcal
,
338
342
Index

Getting started with Adobe Acrobat Pro
From Everand
Getting started with Adobe Acrobat Pro
Rémy Lentzner
5/5 (1)
GLPI User Documentation - Documentation GLPI 9.5
No ratings yet
GLPI User Documentation - Documentation GLPI 9.5
5 pages
SRS - How to build a Pen Test and Hacking Platform
From Everand
SRS - How to build a Pen Test and Hacking Platform
alasdair gilchrist
2/5 (1)
CA Dynam For VSE User Guide
No ratings yet
CA Dynam For VSE User Guide
668 pages
Glpi User Documentation Readthedocs Io FR Master
No ratings yet
Glpi User Documentation Readthedocs Io FR Master
342 pages
Glpi User Documentation Readthedocs Io FR Latest
No ratings yet
Glpi User Documentation Readthedocs Io FR Latest
344 pages
GLPI
No ratings yet
GLPI
4 pages
GLPI Instalacion DocWeb
No ratings yet
GLPI Instalacion DocWeb
2 pages
glpidoc-0.85-en-partial
No ratings yet
glpidoc-0.85-en-partial
4 pages
Google Keep For Beginners: The Comprehensive Guide To Note Taking, Organizing, Editing And Sharing Notes, Creating Voice Notes, And Setting Reminders For Effective Workflow
From Everand
Google Keep For Beginners: The Comprehensive Guide To Note Taking, Organizing, Editing And Sharing Notes, Creating Voice Notes, And Setting Reminders For Effective Workflow
Voltaire Lumiere
No ratings yet
Google Sheets For Beginners: The Ultimate Step-By-Step Guide To Mastering Google Sheets To Simplify Data Analysis, Use Spreadsheets, Create Diagrams, And Boost Productivity
From Everand
Google Sheets For Beginners: The Ultimate Step-By-Step Guide To Mastering Google Sheets To Simplify Data Analysis, Use Spreadsheets, Create Diagrams, And Boost Productivity
Voltaire Lumiere
No ratings yet
The Procedure Is As Follows: Glpi Installation
No ratings yet
The Procedure Is As Follows: Glpi Installation
3 pages
Google Drive For Beginners: The Ultimate Step-By-Step Guide To Mastering Google Drive To Streamline Your Workflow, Collaborate With Ease, And Effectively Secure Your Data
From Everand
Google Drive For Beginners: The Ultimate Step-By-Step Guide To Mastering Google Drive To Streamline Your Workflow, Collaborate With Ease, And Effectively Secure Your Data
Voltaire Lumiere
No ratings yet
Java™ Programming: A Complete Project Lifecycle Guide
From Everand
Java™ Programming: A Complete Project Lifecycle Guide
Nitin Shreyakar
No ratings yet
Software Testing Interview Questions You'll Most Likely Be Asked
From Everand
Software Testing Interview Questions You'll Most Likely Be Asked
Vibrant Publishers
No ratings yet
The Software Programmer: Basis of common protocols and procedures
From Everand
The Software Programmer: Basis of common protocols and procedures
S Mathioudakis
No ratings yet
Go Debugging from Scratch: A Practical Guide with Examples
From Everand
Go Debugging from Scratch: A Practical Guide with Examples
William E. Clark
No ratings yet
Automating Software Tests Using Selenium
From Everand
Automating Software Tests Using Selenium
Hugo Peres
No ratings yet
Jump Start Git
From Everand
Jump Start Git
Shaumik Daityari
No ratings yet
ChatGPT for Beginners Al-Powered Producivity
From Everand
ChatGPT for Beginners Al-Powered Producivity
Ary S. Jr.
No ratings yet
Glpi Install Readthedocs Io en Develop
No ratings yet
Glpi Install Readthedocs Io en Develop
33 pages
Oracle: Protect Your Data
From Everand
Oracle: Protect Your Data
Floribert TCHOKO
No ratings yet
Learning NAGIOS 3.0
From Everand
Learning NAGIOS 3.0
Wojciech Kocjan
No ratings yet
20 Windows Tools Every SysAdmin Should Know
From Everand
20 Windows Tools Every SysAdmin Should Know
padmin
5/5 (2)
Hands-on Go Programming: Learn Google’s Golang Programming, Data Structures, Error Handling and Concurrency ( English Edition)
From Everand
Hands-on Go Programming: Learn Google’s Golang Programming, Data Structures, Error Handling and Concurrency ( English Edition)
Sachchidanand Singh
5/5 (1)
IBM Cognos Business Intelligence
From Everand
IBM Cognos Business Intelligence
Dustin Adkison
No ratings yet
GLPI Installation
No ratings yet
GLPI Installation
33 pages
OpenID Connect - End-user Identity for Apps and APIs: API-University Series, #6
From Everand
OpenID Connect - End-user Identity for Apps and APIs: API-University Series, #6
Matthias Biehl
No ratings yet
Heaven Sent Me
From Everand
Heaven Sent Me
Mary Jinkens
No ratings yet
Java: Tips and Tricks to Programming Code with Java
From Everand
Java: Tips and Tricks to Programming Code with Java
Charlie Masterson
No ratings yet
Java: Tips and Tricks to Programming Code with Java: Java Computer Programming, #2
From Everand
Java: Tips and Tricks to Programming Code with Java: Java Computer Programming, #2
Charlie Masterson
No ratings yet
Feature Flagging with LaunchDarkly: Modern Approaches to Progressive Deployment
From Everand
Feature Flagging with LaunchDarkly: Modern Approaches to Progressive Deployment
Robert Johnson
No ratings yet
Google Sites For Beginners: The Complete Step-By-Step Guide On How To Create A Website, Exhibit Your Team's Work, And Collaborate Effectively
From Everand
Google Sites For Beginners: The Complete Step-By-Step Guide On How To Create A Website, Exhibit Your Team's Work, And Collaborate Effectively
Voltaire Lumiere
No ratings yet
Artificial Intelligence - A beginners Guide
From Everand
Artificial Intelligence - A beginners Guide
Gopi K
No ratings yet
Git Basics and Version Control
From Everand
Git Basics and Version Control
Sankar Srinivasan
No ratings yet
Mastering ChatGPT: Unlock the Power of AI for Enhanced Communication and Relationships: English
From Everand
Mastering ChatGPT: Unlock the Power of AI for Enhanced Communication and Relationships: English
Vasyl Kolomiiets
5/5 (2)
Chatgpt | Generative AI - The Step-By-Step Guide For OpenAI & Azure OpenAI In 36 Hrs.
From Everand
Chatgpt | Generative AI - The Step-By-Step Guide For OpenAI & Azure OpenAI In 36 Hrs.
AJIT DASH
No ratings yet
Linux, Apache, MySQL, PHP Performance End to End
From Everand
Linux, Apache, MySQL, PHP Performance End to End
Colin McKinnon
5/5 (1)
Google Workspace Guide: Unlock Every Google App - Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery
From Everand
Google Workspace Guide: Unlock Every Google App - Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery
Kevin Pitch
5/5 (2)
Google Workspace Guide: Unlock Every Google App – Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery
From Everand
Google Workspace Guide: Unlock Every Google App – Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery
Kevin Pitch
5/5 (23)
Go Programming Cookbook: Over 75+ recipes to program microservices, networking, database and APIs using Golang
From Everand
Go Programming Cookbook: Over 75+ recipes to program microservices, networking, database and APIs using Golang
Ian Taylor
No ratings yet
Go Programming Cookbook
From Everand
Go Programming Cookbook
Ian Taylor
No ratings yet
Python Debugging from Scratch: A Practical Guide with Examples ASIN (Ebook):
From Everand
Python Debugging from Scratch: A Practical Guide with Examples ASIN (Ebook):
William E. Clark
No ratings yet
Building Your Own GPT: A Step-by-Step Guide to Creating Custom AI Models
From Everand
Building Your Own GPT: A Step-by-Step Guide to Creating Custom AI Models
Peter Lengyel
No ratings yet
How to use ChatGPT
From Everand
How to use ChatGPT
Bernhard Gaum
No ratings yet
Java for Beginners: A Crash Course to Learn Java Programming in 1 Week
From Everand
Java for Beginners: A Crash Course to Learn Java Programming in 1 Week
Brady Ellison
5/5 (2)
The Datadog Handbook: A Guide to Monitoring, Metrics, and Tracing
From Everand
The Datadog Handbook: A Guide to Monitoring, Metrics, and Tracing
Robert Johnson
No ratings yet
Rich Text 101
From Everand
Rich Text 101
Ben Langhinrichs
No ratings yet
Debugging Like a Pro: A Practical Guide with Examples
From Everand
Debugging Like a Pro: A Practical Guide with Examples
William E. Clark
No ratings yet
Google Forms For Beginners: The Complete Step-By-Step Guide To Creating And Sharing Online Forms And Surveys, And Analyzing Responses In Real-time
From Everand
Google Forms For Beginners: The Complete Step-By-Step Guide To Creating And Sharing Online Forms And Surveys, And Analyzing Responses In Real-time
Voltaire Lumiere
No ratings yet
Software Development Fundamentals
From Everand
Software Development Fundamentals
IntroBooks Team
No ratings yet
Basic Setup of FortiGate Firewall
From Everand
Basic Setup of FortiGate Firewall
Dr. Hidaia Mahmood Alassoulii
No ratings yet
Agile Scrum Handbook – 3rd edition
From Everand
Agile Scrum Handbook – 3rd edition
Nader K. Rad
No ratings yet
Basic Principles of an Operating System: Learn the Internals and Design Principles
From Everand
Basic Principles of an Operating System: Learn the Internals and Design Principles
Priyanka Rathee
No ratings yet
The ChatGPT Handbook
From Everand
The ChatGPT Handbook
PA BOOKS
No ratings yet
Facebook Apps Secrets: Facebook Apps Secret For Businesses and Marketers
From Everand
Facebook Apps Secrets: Facebook Apps Secret For Businesses and Marketers
John Hawkins
No ratings yet
Nios4 FIRST STEPS
From Everand
Nios4 FIRST STEPS
Gessica Monteforte
No ratings yet
Version Control with Git for New Developers: A Practical Guide with Examples
From Everand
Version Control with Git for New Developers: A Practical Guide with Examples
William E. Clark
No ratings yet
Unlocking ChatGPT: Productivity Secrets for Professionals
From Everand
Unlocking ChatGPT: Productivity Secrets for Professionals
Bill Vincent
No ratings yet
ORACLE PL/SQL Interview Questions You'll Most Likely Be Asked
From Everand
ORACLE PL/SQL Interview Questions You'll Most Likely Be Asked
Vibrant Publishers
5/5 (1)
Go Algorithms for Beginners: A Practical Guide with Examples
From Everand
Go Algorithms for Beginners: A Practical Guide with Examples
William E. Clark
No ratings yet
Full SIWES Reort
No ratings yet
Full SIWES Reort
22 pages
Quick Guide: ZM-VE500
No ratings yet
Quick Guide: ZM-VE500
52 pages
Mini Project Final
No ratings yet
Mini Project Final
38 pages
San Diego Hyperautomation and Low-Code 4-8-2023
No ratings yet
San Diego Hyperautomation and Low-Code 4-8-2023
5 pages
Change Date Format
No ratings yet
Change Date Format
27 pages
Project Planning Monitoring Tool Macro
No ratings yet
Project Planning Monitoring Tool Macro
11 pages
AC500 - Application Note 3ADR010315
No ratings yet
AC500 - Application Note 3ADR010315
31 pages
Azure Cloud Architect: Master's Program
No ratings yet
Azure Cloud Architect: Master's Program
25 pages
Lecture 4 Basic Input-Output Programming
No ratings yet
Lecture 4 Basic Input-Output Programming
15 pages
Windows Cluster Interview Questions and Answers - Mohammed Siddiqui - Academia
No ratings yet
Windows Cluster Interview Questions and Answers - Mohammed Siddiqui - Academia
4 pages
Global App Testing - The Ultimate QA Testing Handbook
No ratings yet
Global App Testing - The Ultimate QA Testing Handbook
71 pages
7.vim Editor and Basic Scripting
No ratings yet
7.vim Editor and Basic Scripting
9 pages
Information About The SAP Load Generator
No ratings yet
Information About The SAP Load Generator
3 pages
VP HDRI Skydomes README
No ratings yet
VP HDRI Skydomes README
3 pages
Algorithm and Flowchart
100% (1)
Algorithm and Flowchart
37 pages
VSAM
100% (1)
VSAM
19 pages
UNIX System and Network Performance Tuning
No ratings yet
UNIX System and Network Performance Tuning
64 pages
Using Combine Book
100% (1)
Using Combine Book
196 pages
Cloud Technology Presentation
No ratings yet
Cloud Technology Presentation
9 pages
B. Specification and Function Guideline PDF
No ratings yet
B. Specification and Function Guideline PDF
24 pages
Unit 4: Defining The CDS Data Model Projection: Week 2: Developing A Read-Only List Report App
No ratings yet
Unit 4: Defining The CDS Data Model Projection: Week 2: Developing A Read-Only List Report App
9 pages
Lab 5 Server 2016
No ratings yet
Lab 5 Server 2016
9 pages
All Saints' College of Technology: Nabeela Ali & Iffat Khan
No ratings yet
All Saints' College of Technology: Nabeela Ali & Iffat Khan
43 pages
Documentation of Nagios
No ratings yet
Documentation of Nagios
17 pages
Changes To DNS
No ratings yet
Changes To DNS
31 pages
Nvflash
No ratings yet
Nvflash
6 pages
MachPanel Control Server Installation
No ratings yet
MachPanel Control Server Installation
16 pages
SQL RDBMS
100% (2)
SQL RDBMS
289 pages
WWW - Aka.ms/pathways: Getting Started Doing More With Power BI Role Based Certification Additional Study
No ratings yet
WWW - Aka.ms/pathways: Getting Started Doing More With Power BI Role Based Certification Additional Study
1 page