File Director
This page refers to an older version of the product.View the current version of the online Help.
File Director telemetry
Ivanti learns most about our products from the real-world experience of our valued customer base. We greatly value the feedback provided to us. However, to make the best-informed decisions on future developments of our products we need a wide view of deployment and adoption data.
Telemetry data can help us measure the quality, scalability, reliability and capabilities of our products. Using such data could enable us to deliver the solutions our customers demand faster, and alert us to areas which customers would find less useful.
Ivanti want to ensure a high level of transparency on this topic. The telemetry data that we gather is listed below. It is the same set of data that our customer support teams use to resolve user issues. The gathering of this data is in-line with our existing EULA agreement. Nevertheless, any customers not wishing to participate can withhold this data from being sent.
Data gathered
Data is gathered from each appliance and sent to a secure Application Insights instance. File Director telemetry was introduced in 2019 and the initial release gathered basic usage information.
Data collected:
• Customer name
•License key
•License key count
•Server version number (Marketing No.)
•Cluster ID (this is a hash of the cluster name and port)
•Appliance Hostname
•Support mode status.
In 2019.3 the data capture was extended to include information from the client and from the server.
Client telemetry
• OS build number and version number.
The current telemetry also includes feature usage - as defined by the use of engineering keys.
The data retrieved states whether the feature (engineering key) is enabled on the client.
Client feature usage telemetry
•Admin Pause Enabled
•Bandwidth Control in Use
•Base Folder Overidden
•Cache Cleanup Mid-Session in Use
•Cache Cleanup Logoff in Use
•Cache Expiry Changed
•Conflict File Format
•Cleanup Cache if Sync Wait Times Out
•Delay Logoff Until In-Sync
•Delta Threshold Defaults Changed
•Disable Search Indexing
•Disable Loopback Installation
•Driver Threads Changed
•Electives
•Electives Overrides
•Exclusions
•Exclusion Overrides
•Force Manual Mode
•Http Timeouts
•ILS
•ILS Outside of Profile
•Kerberos SSO
•Low Priority File Types
•Map Drives
•Manual Conflict Resolution
•NTLM SSO
•Optimize Leaf Folders
•Overlay Mask
•Process Blacklist (not default)
•PST Delta Failsafe Enabled
•PST Unlinking
•Redirection Overrides
•Screen Messages
•Server Locking Enabled
•Shadow Sync File Types
•Shadow Sync Options
•Status Updates
•Sync Status Debounce
•Sync Threadpool Adjusted
•User Language (Localization)
Server telemetry
The current server telemetry data also includes feature usage - as defined by your configuration settings.
Server feature usage:
•Kerberos
•Quality of Service
•Syslog Audit
•Account Lockout
•IP Restriction
•LBS
•Map Point Policy
•Remote Wipe
•Secure LDAP
•Verified Devices
•Connector Types
Firewall changes
To allow this data to reach Ivanti there is a requirement to open some outgoing ports within your server’s firewall.
Please refer to the Outgoing Ports > Telemetry section of this Microsoft article.