Requirements for Connection

1. A user with sufficient privilege levels to install agents on client machines.

   1. Variations may exist for Linux and macOS clients.

2. A tool like ManageEngine or SCCM for deploying to a large number of clients.

3. Client machines must have access to the <geodi> server.

4. <geodi> server must have access to the client machines, with port 1982 (configurable) open.

The GDE Agent can be accessed at: <geodi_url>/GUI/Agents/GDE

Here, <geodi_url> refers to the GEODI Server address.

1. Check if the client has access to the GEODI Server. GEODI should be accessible through a browser on the client. Enter the GEODI address in a browser on the client; there should be access.

2. The GEODI server should be accessible from the client's GDE. Using a browser on the client, enter <ClientIP>:<1982>/DEW?op=GetLastError. If everything is fine, it should return null. The ExplorerPort specified in GDE rules, e.g., ExplorerPort=1982 (or the chosen port), should be open.

3. Inspect the Firewall, Antivirus, or any similar tool to ensure there is no blocking mechanism preventing communication.

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

5. Verify the status of the received TOKEN: <GEODI_URL>/API/token_parser.html.

6. Examine the Agent Management Panel; if the endpoint's status looks good, waiting for a while may resolve the issue. The GEODI Server queues incoming data, so the files at the endpoint might not be due yet.

7. If everything seems correct but data is still not coming through, check the FolderList and IgnoreFolders values in the GDE rules.

8. If you are not receiving the expected file type, ensure that the extension is not listed in the IgnoreFiles value in the GDE rules.

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.

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 about an hour.

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

1. You can change 1982 to anything available. Please be careful about not assigning ports that have already been used.

2. You may set the GDE port to 0, but GEODI can not open the remote files in this case. The search and discovery are unaffected.

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.

The GEODI legacy data classification tool classifies remote files if you have the classification agent installed on the same endpoint.

Yes, GEODI remediation tools cover remote files as well. The only requirement is that the user should have delete/update permission on the remote machines. This way, GEODI deletes, makes, or encrypts remote files like the local ones.

Search is unaffected, but you can not open/view or remediate the 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.

1. Sistem Admins see all files.

2. Other users' permissions depend on Enable LDAP settings. If LDAP is enabled, then local permissions are used.

3. It is possible to set each user to see their PC files. Please ask the DECE team how to do that.

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

{
  "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"
	}
}

Requirements for Installation

In addition to the Windows MSI requirements:

1. The Windows Service user must have read-only access to the FileServer directories.

2. A separate configuration file must be created under the GEODI Server for each File Server to define the directories to be indexed and other rules. Details are provided on the main page..