...
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. |
Windows Setup
Info |
---|
Action | Command | Notes |
---|---|---|
Setup | "GEODI<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" The MSI is distributed with the parameters mentioned above. “GEODI.DesktopExplorer.msi“ should be the directory of the MSI package. Some tools make you select the MSI package. This command is not needed. /quiet is an msiexec parameter.https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/msiexec UPDATE_URL is optional. It is explained in the update step. | |
Remove | msiexec.exe /x /qn /norestart "GEODI.DesktopExplorer.msi"MSI is run with the uninstall parameter. | |
Update | start "GDE" "%ProgramFiles(x86)%\DECE Software\GEODI Desktop Explorer\Updater.exe" | Updater is runned. |
Windows Servis Setup
GDE installation may be converted to a Windows Service using the WindowsServiceInstall.bat script in the GDE folder.
WindowsServiceUninstall.bat reverses uninstalls the service setup.
Service mode does not require a login user.
In order for For GDE Exe and GDE Service Mods not to run at the same timesimultaneously, GDE Exe must be uninstalled from under startup.
Setting file (default.json)
- Settings are available on the GEODI server in the default.json.sample file in the
. ---> QQQ nasıl?
Token Creation
Anchor | ||||
---|---|---|---|---|
|
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.
...
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.
View file | ||
---|---|---|
|
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.
GDE central rule setting
Settings should be GEODI server <GEODI_APP>/Settings/Geodi.DesktopExplorer folder named default.
...
json. Installed GDEs will automatically retrieve
...
Settings can be changed after setup and while indexing is in progress, changes will take effect in about 1h.
To scan different directory on multiple machines:
...
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>.
jsonjson, or <ClientMachineName>.json
are added in the <GEODI_APP>/Settings/Geodi.DesktopExplorer directory, these files will only be used for the relevant computer.
Code Block | ||
---|---|---|
| ||
{ "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. |
...
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.
...
Deployment of the GDE Client Package
Script structures vary in tools such as PDQ, ManageEngine, and SCCM, but the operations to be performed are the same.
Ready scripts exported for the PDQ Deploy tool are in the XML file. PDQ can be imported and used.
View file | ||
---|---|---|
|
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 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 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>.
...
. |
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 may not be installed on the clientGDE on the client may not be active is installed
Check if GDE is running (Geod.Desktopexplorer.exe may not should be running)
The port required for Server-Client communication Check if the port (default 1982) may be closed is available or not blocked.
The client may not be able to access Check if the GEODI server (GEODI Server may not have a public address). You can also run this test on the client through the browser.
GDE is a continuous feeding software. Firewall/Virus software may be set to block continuous communication.
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. Therefore, the scanning process will necessarily progressSo 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 feeding machine client is formatted, etc., GDE starts feeding from the beginning as if it has never been fedit is assumed a new client. The Old index is preserved.
Central setting changes take effect within 1 hour.
By default, only Only the name and date of are indexed for files larger than 100Mb are indexed by default in order not to slow down the Network Speed while feeding.
It is set to 500Mb100 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.