Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

The GDE agent indexes/discovers many PCs or FileServers w/o defining a share. The GDE agent runs on Windows, Linux, or MacOS.

GEODI may discover FileServers if there is a share. Then, GDE is not required.

GDE crawls the EndPoint or FileServer and sends selected files to a GEODI Server. This way, you can discover and search local files w/o sharing any folder. GDE continuously crawls every 3 hours to find changed files.

With the GEODI Classifier, it is possible to classify the local files remotely.

After discovery, it is possible to remediate the local files remotely.

Installation and Configuration

A configuration file on the GEODI server determines which local folders and file types to include. This configuration may be customized by client IP, ClientUser, or ClientMachine name. So, you may target a different area for each FileServer or client.

The Agents can be manually installed on FileServers or EndPoints. But if you have many EndPoints, then using a tool like ManageEngine or SCCM for deployment is suggested.

GDE software updates are auto. It may be set to update from a local source.

GEODI Server has a monitor panel to watch EndPoints. GEODI Agent Management Panel

Conditions for connection

  1. GEODI Server

    1. Server URL → This URL must be accessible from the endpoints

    2. A GEODI project or a source in an existing project to index files

    3. A token with permission to feet the GEODI Projesi or the source

    4. Folder and file types to index on the endpoints. Configuration may be customized per server or IP.

  2. Endpoints

    1. Access to the server URL

    2. Port 1982 must be open for request from the server

    3. You may install it manually for a File Server or a few PCs, but you will need a tool like ManageEngine or SCCM if there are many endpoints.

Installation Checklist

Subject

Description

Create a new project or choose an existing project to index files.

A separate project is OK for discovery purposes, but it is better to add PCs to an existing project if you have Enterprise Search.

This project URL must be accessible from the EndPoints.

The recognizer, GDE must be on the project. Find GDE recognizer from IT group.

Create a token

Follow the procedure on this page to get the Token. As a best practice, we suggest you create a separate user for the Token.

Follow the procedures for different OSs

These pages will lead you to each OS.

GDE Configuration Settings

The settings determine which local folders and file types to discover. There may be a single setting for all, or you may customize it by clients.

Client Monitoring

Activate GEODI Agent Management Panel

Troubleshooting

 Indexing does not start

  1. Check Agent Management Panel; if the health of the endpoint looks ok, then waiting a while will solve the problem. GEODI Server queues the incoming data. So, the time for the files on the endpoint may yet to come.

  2. Check if endPoint has access to the GEODI Server. GEODI must be accessible from a browser.

  3. Check if the port (default 1982) is available and not blocked.

  4. Check the Firewall, Virus, or any similar tool; do not block the communication.

  5. Check if the client machine is up and running. GDE is installed and running (Geodi.Desktopexplorer.exe should be in the task list)

  6. Check if the token is active , QQQ

 Settings are not effective,

  1. The Setting file may not be a valid JSON. Validate it with an online tool.

  2. Settings will generally be adjusted in an hour. If the IP of the endpoint has changed, this may take up to 3 hours.

 Some files are not indexed

  1. The default settings block some large files, like videos. Files larger than 100 MB or compressed files larger than 500MB are blocked. You may change the settings. The settings will be effective in an hour.

 The endPoint has been formatted

  1. Install the GDE as usual. The endpoint will be treated as new. The old data is preserved.

FAQ

 How can query files from a specific endpont?

It is no different than the other. Add layer:GDE <machinename> into query.

  1. layer:GDE <machinename> will query the files.

  2. layer:GDE <machinename> doc:*.pdf will list the PDF files.

  3. layer:GDE <machinename> doc:*.pdf contract will list the PDF files with the word contract.

 Does GDE copy local files?

No, GDE does not copy the local files. But if you need to backup local files, check the “backup content” in the GEODI source dialog. You may activate or deactivate this setting at any time.

 Who is going to see an endpoints files?

  1. Admins see the files. But they may not have permission to open the files. QQQ

  2. Enable LDAP on the settings.

  3. Enable … on GEODI source to have everyone see only their files. … (link)

 What happens if the endPoint is formatted?

  1. Install the GDE as usual. The endpoint will be treated as new. The old data is preserved.

GDE configuration settings

Settings should be GEODI server <GEODI_APP>/Settings/Geodi.DesktopExplorer folder named default.json. Installed GDEs will automatically retrieve this setting in about an hour.

  • 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 additional 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, desktops, etc.). 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 ["*"] 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 a 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: ["*:\\data","C:\User*"]

Default value: null

IgnoreFiles

string[]

List of folders to ignore. * is accepted and used with the settings under Geodi Settings/IgnoreFileTypes.

Default value:["*.MP4","*.MOV","*.MP3"]

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 IP:192.168.1.1

The defined metadata and values will be visible in the GEODI search interface.

Token Creation

  1. Log in with a user accessing the Source that GDEs will feed.

  2. Open the page: Generating a GEODI Token.

  3. Check the Feed Checkbox and enter the Source's name in the AllowList.

  4. Now you are ready to create the Token.

  • No labels