Printout Header

LEX Online Manual Content

Application Options - General

In this dialog, you can configure some basic application settings.

Application options: General

Run LEX in ReadOnly mode

If you activate the ReadOnly Mode, all buttons and menu option which are related to write access operations (edit / delete / move / rename and so on) are disabled. This prevents that you change the directory data accidentially:

Deactivated write access

Deactivated write access

Default configuration: Active

Automatic logon with the last used connection profile

If you activate this option, LEX connects automatically to the LDAP server of the last used connection profile when you start the application. The focus jumps to the object again which was selected when you closed the application before.

This is only possible when you used a LDAP connection profile before - just in the moment when you shut down the last time. IF you were connected by manual configuration or if you were disconnected at this moment, no automatic connect will performed.

Default configuration: Active

Check for program updates on the web

This option specifies whether and how often LEX checks online for product updates. This is only possible if the regarding workstation where LEX - The LDAP Explorer is installed has a HTTP connection to the internet. You can use the Check Now button to perform the check immediately.

If LEX checks for product updates by requesting a small text file over standard HTTP (Port 80). This text file contains the release and build number of the most current official release, which can be compared to the release of the installed program. The URL of the file is

A typical content of this file would be this text lines:


If there is a difference detected between your local version and the official release on the product web site, the following message will be displayed:

Update available message

The http-get command to read this update check file is the only contact that LEX will try to establish to 'call home'. Under no circumstances LEX will transfer any other data from your computer into the internet!

Default configuration: Active, Check weekly

Profile and filter storage path

This specifies the disk path where LEX stores the following data:

  • The LDAP connection profiles, these are binary encoded files which contains all information to establish an LDAP connection to an director server. Please note that the connection information is stored on your hard disk as Rijndael (AES Advanced Encryption Standard) encrypted binary files. So if a user password is contained in the profile, it is very well protected against disclosure. The files are named 'LEXProfile-xxxxx.ini'.

  • The saved LDAP filters, which can be used in the object list filter, in directory searches or generally in the LEX Filter Factory. LDAP filters are saved as simple text files which contain the filter string, these files are stored in the subdirectory 'LDAPFilter'. There is also a manual topic which describes the LDAP filter syntax.

  • The saved LDAP attribute sets, which can be used in attribute list filters and object list column header definitions. LDAP attribute sets are saved as simple text files which contain the attribute names (one per line), these files are stored in the subdirectory 'LDAPAttributeSets'.

Default configuration: %APPDATA%\LEX\

Directory cache storage path

This specifies the disk path where LEX stores the caches directory tree information. This information holds the tree hierarchy of an LDAP connection to show the LEX treeview panel very fast. LEX store this cache in an XML file (storage location can be set in Tools - Options - General - Directory Cache Storage Path). In the Directory Cache Storage Path, a subdirectory is created for every LDAP server which was connected to with LEX. In this subdirectory, there are separated files for each different LDAP port, for each LDAP base DN and for each user. So different cache information for every combination of LDAP-Server/LDAP-Port/LDAP-BaseDN/LDAP-User is stored in a separate cache XML file. This is because a directory tree can look very different from different point of views - depending on which user reads the tree and depending on the technical configuration of the connection. The cache filenames are built like this:


Next time a connection is opened with a known combination of LDAPServer, Port, BaseDN and user, LEX builds up the directory tree hierarchy visible in the Treeview Panel very fast - it's read from the XML cache file.

Default configuration: %APPDATA%\LEX\