The employees table is primarily fed by the LDAP synchronization but you can actually manually add employees. This is all due to the fact that the database respective application did grow throughout time. It started of with a manual table that then was fed by a simple user-synchronization and finally a complete LDAP change reporting was implemented. Please keep that in mind when looking in to it.

In any case, employees are used for workstations, software, phone DIDs and within the rights matrix.

Manual employee entries are possible and might help to compensate for some special purposes, while you in general and most cases should just rely on the LDAP synchronization process and the table being fed by LDAP / Active Directory.

Additionally it allows you to actually see if the entry comes from LDAP or if it was manually created using the synchronized / Sync column. If it was synchronized, you further have a LDAP last seen column that indicates if the user was actually deleted in your Active Directory.

Even further is there a column # Wkst. that will show you how many workstations are assigned to the employee.

All of this information is useful to filter e.g. for all deleted users that have one or more workstation assigned, to accomplish this do the following:

  • LDAP last seen = >=7/18/2018
  • # Wkst. = >0

Setting those two filters would show you all deleted user accounts that still have workstations assigned in you database. You could implement similar counter columns for software, phones and the rights matrix by just changing the qryEmployees in SQL and adding the columns in Sys Columns in just a few minor steps.