GEODI Desktop Explorer (GDE) is the solution for indexing data on Client Computers in a central GEODI. It works in windows, Linux, macOS and Pardus environments.
GDE is installed on each computer manually or automatically with Application distribution tools (SCCM, PDQ, ..). Which directories will be indexed can be specified with the settings.
GDE processes the new and changed files every 3 hours.
GDE may run as a Windows Service.
GDE does not copy the contents to the server. The contents found as a result of a search are found and opened from the respective computer. If the computer or GDE is not turned on, you can search but not access the document. If you want to make a backup of the documents, you should turn on the "Backup Contents" setting for the corresponding Resource in the GEODI project.
Conditions for connection
Token and URL
Directory configuration file to scan in GEODI Server
GDE Agents Installation Files
Installation Checklist
Subject | Description |
|---|---|
GEODI resource name | GDE data can be located under a source you specify in GEODI. You should use this information when purchasing tokens. Incoming data will appear in the “Sources” and data discovery reports in the GEODI Search Interface. A ready-made panel called “Discovery” will come with your project. In order for the data counts from clients in this panel to work correctly, you must also add the recognizer named GDE to your Project. |
Settings | GDE runs on a large number of clients. The settings are determined centrally. This page explains how to make the settings. A separate set of settings can be specified for FileServer installations or for each client if needed. |
Client Installation | Installation steps for Windows, Linux and MacOS are indicated on the subpages. |
Client Monitoring | With the method described GEODI Agent Management Panel on the page, information such as the health of the agents and the version can be monitored. |
GDE central rule setting
Settings should be GEODI server <GEODI_APP>/Settings/Geodi.DesktopExplorer folder named default.json. Installed GDEs will automatically retrieve this setting.
Any changes will be effective in about an hour. You may change the settings while GEODI is running.
To define different rules for each machine, you may use different files named <ClientIP>.json, <ClientUserName>.json, or <ClientMachineName>.json.
{
"FolderList": ["%UserProfile%"],// "*" scan all directory //
"ExplorerPort": 1982,
"IgnoreFiles":["*.MP4","*.MOV","*.MP3"],
"MetaData": {
"LDAPDN":"=d.CurrentUser!=null?d.CurrentUser.DistinguishedName:null",
"IP":"=d.ClientIP",
"ComputerName":"=d.ClientMachineName",
"UserName":"=d.ClientUserName"
}
}
Setting Name | Type | Description |
|---|---|---|
FolderList | string[]* | Used to specify the folders to be scanned. Folders can be identified by separating them with "," The default directory is %UserProfile% (includes documents, downloads, desktop...). A complete list can be found at https://docs.microsoft.com/tr-tr/dotnet/api/system.environment.specialfolder?view=netframework-4.0. Values are case sensitive. Subdirectories can also be defined as %UserProfile%\\Desktop. You can use ["*"] if you want to scan all disks. |
ExplorerPort | int | If a value above 0 is entered, Explorer will run in APP→GEODI→APP mode. Firewall settings must be made in this mode. When a port to be used is defined, as long as the client is open, the content can be viewed on Geodi. |
EnableLDAP | bool | If true value is given, LDAP authorizations of the files are also indexed. Default value: false |
IgnoreFolders | string[] | List of folders to ignore. * is accepted. Used in combination with the settings under Geodi Settings/IgnoreFolders. Example: Default value: null |
IgnoreFiles | string[] | List of folders to ignore. * is accepted. Used in combination with the settings under Geodi Settings/IgnoreFileTypes. Default value: |
Metadata | You can define metadata for parsing files from clients. These metadata are specified in the settings file. The values used in the default settings can be seen in the example file. Searching with metadata is done with <metaname>:<value> Example The defined metadata and their values will be visible in the GEODI search interface. |
Token Creation
Log in with a user accessing the Source that GDEs will feed.
Open the page: Generating a GEODI Token .
Check Feed Checkbox and enter the name of the Source in the AllowList.
Now you are ready to create the Token.
Troubleshooting
If no data is received after setup,
please check your Firewall/Antivirus settings and contact your IT consultant.
The client may be Closed
Check if GDE is installed
Check if GDE is running (Geod.Desktopexplorer.exe should be running)
Check if the port (default 1982) is available or not blocked.
Check if the GEODI server is accessible from the client(use ping or a browser).
GDE continuously feeds the GEODI server. A Firewall/Virus scanner may be blocking the communication.
Be patient; The GEODI Server queues and processes data from many clients simultaneously. So the client data eventually be indexed if no other problem exists.
If the IP or Name of the client changes, previous files will be visible again in about 3 hours.
If the client is formatted, it is assumed a new client. The Old index is preserved.
Central setting changes take effect within 1 hour.
Only the name and date are indexed for files larger than 100 MB to preserve network resources by default. This limit is 500MB for compressed file contents. The values may be changed.
When
"Client is null \q \n"warning is received on GetLastEror, URL information should be checked through the Registry.
GDE Windows Client MSI Parameters
Action | Command |
|---|---|
Setup | "<path>GEODI.DesktopExplorer.msi" /quiet GEODI_URL="https://icdemo.dece.com.tr/" GEODI_TOKEN="EAAAAL2FcQ9RvjWM…" UPDATE_URL="http://192.168.1.26:3323/GUI/autoupdate.txt" |
Remove | msiexec.exe /x /qn /norestart "GEODI.DesktopExplorer.msi" |
Update | start "GDE" "%ProgramFiles(x86)%\DECE Software\GEODI Desktop Explorer\Updater.exe" |
Parameter | Description |
|---|---|
GEODI_URL= | The address that agents will use to access GEODI. It is recommended that DNS/port/SSL operations are completed and finalized before installations are made. |
GEODI_TOKEN= | It is explained in the TOKEN Creation step on this page. It is necessary to use a different user and keep the password of this user. If the password changes, it may need to be recreated and reinstalled. |
UPDATE_URL | Optonal parameter for closed networks or if you prefer a different adres for updates. |
GDE Windows Service Installation
GDE installation may be converted to a Windows Service using the WindowsServiceInstall.bat script in the GDE folder.
WindowsServiceUninstall.bat uninstalls the service setup.
Service mode does not require a login user.
GDE Software Update
In the default installation, packages use the DECE server to check and download current versions. If there is access to these servers after the above operations, the update is done without any problems.
If there is no access, the following steps should be followed.
Add the UPDATE_URL parameter to the first installation step. The link to the autoupdate.txt file where updates will be checked should be given as http/https.
You can request the updated GDE package and autoupdate.txt file from the DECE Support team. After receiving this file, the URL= in it should be changed.
You can put the updated MSI file in a user-accessible directory and give the path to it as http/https or file://<filepath>.
On the machine installed for Linux/MacOS update, the new version is automatically installed when the new package is to be installed.
Deployment of the GDE Client Package
Script structures vary in tools such as PDQ, ManageEngine, and SCCM, but the operations are the same.
Ready scripts exported for the PDQ Deploy tool are in the XML file. PDQ can be imported and used.
Setting Name | Type | Description |
|---|---|---|
FolderList | string[]* | Used to specify the folders to be scanned. Folders can be identified by separating them with "," The default directory is %UserProfile% (includes documents, downloads, desktop...). A complete list can be found at https://docs.microsoft.com/tr-tr/dotnet/api/system.environment.specialfolder?view=netframework-4.0. Values are case sensitive. Subdirectories can also be defined as %UserProfile%\\Desktop. You can use ["*"] if you want to scan all disks. |
ExplorerPort | int | If a value above 0 is entered, Explorer will run in APP→GEODI→APP mode. Firewall settings must be made in this mode. When a port to be used is defined, as long as the client is open, the content can be viewed on Geodi. |
EnableLDAP | bool | If true value is given, LDAP authorizations of the files are also indexed. Default value: false |
IgnoreFolders | string[] | List of folders to ignore. * is accepted. Used in combination with the settings under Geodi Settings/IgnoreFolders. Example: Default value: null |
IgnoreFiles | string[] | List of folders to ignore. * is accepted. Used in combination with the settings under Geodi Settings/IgnoreFileTypes. Default value: |
Metadata | You can define metadata for parsing files from clients. These metadata are specified in the settings file. The values used in the default settings can be seen in the example file. Searching with metadata is done with <metaname>:<value> Example The defined metadata and their values will be visible in the GEODI search interface. |