The two ‘excel’-files of this check
(check_service_desk_contacts _[n]ok.TXT) have got the
structure:
|
column
|
remark
|
|
VMTEL
ID
|
reference id for the
contact name (not used in this output)
|
|
VMTEL
Name
|
contact name in
vmtel.txt (not used in this output)
|
|
Service Desk
Name
|
contact name the new database (last name + space +
first name)
|
|
state
|
result of the
check
|
Depending on the value of
‘state’ the contact name is listed in either the
‘_ok’ or the ‘_nok’
file.
-
state of the ‘_ok’ file and
actions to be done
In this file the
state-column has got three values:
-
ok
-
inactive
in Service Desk, not found in VMTEL
-
inactive
duplicate entry, active entry found in Service Desk and
VMTEL
state ‘ok’
The name of the new database is found in the vmtel
file (referenced by the vmtel id, whether the name is correct has
been checked by ‘Explanation of check
‘check_vmtel_contacts (2)’).
state ‘inactive in Service Desk, not found
in VMTEL’
The name in the new database is marked as inactive
and is not listed in vmtel, no action has to be
taken.
state ‘inactive duplicate entry, active
entry found in Service Desk and VMTEL’
The name in the new database is marked as inactive
but it is listed in vmtel. Since there is an active entry in the
new database with this id no action has to be
taken.
-
state of the ‘_nok’ file and
actions to be done
In this file the
state-column has got the values:
-
inactive
in Service Desk, but found in VMTEL
-
not found
in VMTEL
state ‘inactive in Service Desk, but found
in VMTEL’
The name in the new database is marked as
inactive. These names have to be set to active or in case of a
correct inactive status vmtel has to be
corrected.
state ‘not found in
VMTEL’
The name of the new database is not found in the
vmtel file. The entry can be an entry only of the Service Desk or a
deleted entry in vmtel. Depending on the situation the entry has to
be updated.
1. Hardware Requirements
