- Glasswall CDR
- Embedded Engine
- About Embedded Engine
- Overview
- Getting Started
- API
- Engine Release Notes
- Release 16.5.1
- Release 16.5.0
- Release 16.4.0
- Release 16.3.0
- Release 16.2.0
- Release 16.1.0
- Release 16.0.1
- Release 16
- Release 15
- Release 14
- Release 13.1 (beta)
- Release 13
- Release 12
- Release 11
- Release 10
- Release 9
- Release 8
- Release 7
- Release 6
- Release 5.4
- Release 5.3
- Release 5.2
- Release 5.1
- Release 5
- Release 4
- Legacy
- Supporting Tools
- Appendix
- Terms of Service
- Halo
- About Halo
- Glasswall Halo FAQs
- Overview
- Getting Started
- Evaluation via AWS Marketplace
- Evaluation via minikube
- Deployment
- Deployment Overview
- Shared Responsibility Model
- Glasswall Artifact Registry
- Configuration Changes
- Authentication
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- Amazon EC2
- EKS
- EKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to EKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Create secrets in Secrets Manager
- Step 4 - Enable access to Glasswall's Artifact Registry
- Step 5 - Pull Helm charts
- Step 6 - Install and configure prerequisite components
- Step 7 - Install CDR components
- GKE
- GKE Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to GKE
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Enable your GKE cluster to access Secrets
- Step 4 - Manage Secrets
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- OKE
- Single Node VM
- License Management
- Functionality
- Using Halo
- Halo Release Notes
- v2.7.2
- v2.7.1
- v2.7.0
- v2.6.2
- v2.6.1
- v2.6.0
- v2.5.4
- v2.5.3
- v2.5.2
- v2.5.1
- v2.5.0
- v2.4.15
- v2.4.13
- v2.4.12
- v2.4.11
- v2.4.10
- v2.4.9
- v2.4.8
- v2.4.7
- v2.4.6
- v2.4.5
- v2.4.4
- v2.4.3
- v2.4.2
- v2.4.1
- v2.4.0
- v2.3.0
- v2.2.1
- v2.2.0
- V2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.7
- V2.0.6
- V2.0.5
- v2.0.4
- v2.0.3
- v2.0.2
- Single Node VM
- v2.7.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.7.0 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.0 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.4 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.3 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.4.13 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.12 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.11 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.10 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.9 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.8 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.7 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.3.0 RHEL8.8 RKE1.25.9+rke2r1
- v2.2.1 RHEL8.8 RKE1.25.9+rke2r1
- Appendix
- Terms of Service
- Constellations
- About Constellations
- Constellations FAQs
- Overview
- Getting Started
- Architecture
- Deployment
- Glasswall Artifact Registry
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create namespaces
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install Glasswall Halo services
- Step 9 - Install Constellations components
- Constellations Release Notes
- Terms of Service
- Performance
- Meteor
- About Meteor
- Meteor Versions
- Getting Started
- Using Meteor
- Meteor Connect
- About Meteor Connect
- Minimum Requirements
- Install Glasswall Meteor Connect
- User Interface
- Preferences
- File Versions
- Support
- Storage Protocols
- Connect Mode
- Meteor Connect Release Notes
- Cloud Folders
- Meteor Release Notes
- Appendix
- Terms of Service
- Glasswall REST APIs
- Glasswall Research
- PDF
Preferences
- PDF
General
Save Workspace
Save all mounted volumes when quitting to be restored while relaunching.
Bookmarks
Change the size of the menu items in the status bar menu. Choose between Small, Medium, and Large icons.
Sync
Connect Mode
Change the default synchronization option. You can disable synchronization by default for all bookmarks by switching to Online. Refer to Connect Mode.
Index Files
Index files on the server for a mounted connection in the background after connecting to ensure you can browse all directories when offline. Enabling this option will make sure new files available on the remote storage are detected without manually choosing Reload in the context menu. When enabled, remote directories previously opened are polled for changes and new files periodically every 10 minutes.
This feature is not available in *Online* connect mode. You cannot browse folders or open files as soon as the server connection gets interrupted.
Enable Buffering
Choose whether the file contents should be buffered. The option allows buffering file contents in a temporary location which is only deleted when quitting the application.
- Allows faster access when reading or writing files with random access patterns from applications in Online mode.
- With the option enabled in Smart Synchronization mode, buffered file contents will be copied to the cache and the file can be opened when offline.
Temp Buffer
Buffered files are saved in %temp%
for Windows.
Lock Files
Enable to prevent conflicting edits when accessing documents from a shared environment. Refer to File Locking.
Mount Location
Tip - Only available on macOS using the standalone version.
Volumes are mounted in the Volumes folder in the application support directory. You can change the default to another folder that is writable.
Cache Location
Change the location where to store cache files required for offline access. By default the *Cache* folder is in `%LocalAppData%\Cyberduck`. You must select NTFS formatted drives with support for *NTFS Alternate Data Stream (ADS)*. FAT, FAT32, exFAT, and similar formatted drives are not supported. Network drives may not support alternate data streams as well.
Warning - Do not manually move, delete or modify files in the obfuscated local cache location.
Cache Limitations
Periodically free up space with cache limitations to purge unused files from the cache at regular intervals in the background keeping only a placeholder with metadata. You can choose a limit for the synchronization cache per bookmark and can select a timeframe for unused files to be purged.
The following options are available:
- Limit by size. Limit cache size per bookmark by selecting a maximum folder size within the preference. Exceeding the maximum cache size, larger files are purged first.
- Limit by time. Purge files not accessed within a selected period of time automatically.
Tip - Files selected to always keep offline are never automatically removed from the cache.
By default, files are kept in cache for 30 days and the cache is limited to a maximum size of 5GiB.
Attention - The settings apply separately for each bookmark. The synchronization cache gets cleared based on the choosen cache limit after Mountain Duck is started and every 24h as long as Mountain Duck is running.
Notifications
Set which type of notifications you want to receive. Alternatively, you can choose Open System Preferences to disable the notifications all together.
You can disable notifications in *Settings → System → Notifications and Actions*. Uncheck *Show notification banners* and *Play a sound when a notification arrives*. Keep *Show notifications in action center* to see the notifications in Windows action center anytime if required.
Profiles
Select connection profiles to be installed. Either scroll through the list or use the search function to look for a specific profile. The connection profiles will be installed after ticking the corresponding checkboxes. Installed protocols are displayed in the protocol dropdown menu in the bookmark window. To disable the connection profile simply untick the checkbox.
Default Connection Profiles
The connection profiles for default protocols are always enabled.
Login Item
Reconnect after restarting the computer. If you choose Enable Login Item and Save Workspace in Preferences → General and do not manually eject the volume prior to reboot it will reconnect after login.
Updates
An auto-update feature will alert you when a new version is available and self updates the application. Choose Preferences → Automatically check for updates. You can also choose to update to snapshot or beta builds.
- Snapshot builds: Include the latest changes and are published continuously. These builds are not manually tested.
- Beta builds: Published before a release and include the latest features and have been tested but might not have release quality yet.
Tip - You receive no update notification if your user is missing administrator permission.
Hidden Configuration Options
If not existing yet you need to create the file %AppData%\Cyberduck\default.properties. Add the setting as follows:
property=value
These settings are shared with Cyberduck.