File Director for Administrators
Google Drive connector
File Director can now be configured to connect to and utilize Google Drive storage for user home shares. Once configured, users can update files within their Home Directory using File Director on any of the supported platforms and will see the changes seamlessly sync with Google storage.
The end user does not have to change the way they work, and there is no training required to adapt to a different storage location. File Director will simply take the files from the native profile locations such as the user’s Desktop (In-Location-Sync), and sync them with Google storage, with files delivered either on demand or automatically at logon as defined by the Administrator.
For further information see Google Drive connectors for home map points.
Cache Management – Remove all local cache at user logoff
In a significant extension to the client-side Cache Management capabilities, the ability to selectively remove the local copy of the user’s cache at Logoff has been provided.
With this enabled, Administrators can ensure local disk space is managed efficiently with File Director leaving zero-touch at the end of the session.
For further information see Cache Cleanup.
Enhanced Map Point configuration
•New Map Points are now disabled by default.
For further information see Map Point Policy.
•Home (Private) Map point configuration.
Cluster wide log collection
With previous versions of File Director gathering appliance logs from each node within a clustered environment could be a time-consuming task. We now provide Administrators with the ability to download logs from across the cluster from the Cluster Management page of any node.
For further information see Clustering.
•FDmon: Endpoint Analysis Tool forFile Director.
•File Director Performance Monitoring Dashboards.
For further information see Sizing and Monitoring your Deployment.
Version 2018.3 SP1
Option to disable PST Smart Unlinking
The background task of PST unlinking and relinking takes place to prevent any user delay at logon. By default, this background activity is enabled. The File Director 2018.3 SP1 release introduces an engineering key to disable this activity. See PST smart linking
Cloud Connectors tab
Within the Admin console, OneDrive registration has been moved from the Directory Services tab to a new Cloud Connectors tab. This will allow us to add future cloud connectivity functions to the same location and enable improved user navigation. See One Drive Registration
Specify backup for Kerberos Authentication
It is now possible to specify a backup server for Kerberos authentication. See Configure Kerberos in the File Director Admin Console
New File Director Base Image
Security and compliance are further enhanced with the release of a new base image. Previously, the base image utilized a version of the operating system FreeBSD which is no longer supported. File Director 2018.3 introduces a brand-new base image making use of version 11.2p3 of FreeBSD.
Windows Client Cache Management
File Director 2018.3 introduces an automatic cache cleanup function configurable to your requirements. This can help simplify maintenance and reduce endpoint hard disk usage.
The cache cleanup removes inactive files from the cache. It will apply only to files that have been synced, where the user is online, and where no uploads are pending. As an administrator, you determine the length of time unused files may remain in the cache before being removed. When this period expires the cached files are removed from the local cache.
Rules can be specified to exclude specific file types from the cleanup, and processes (such as web browser applications) that frequently open and close files without user action. See Cache Cleanup.
New version numbering
File Director version numbering has been changed to reflect the rest of our product portfolio.
One Drive for Business connector scalability
This version introduces several improvements to both the File Director server and Windows client when used with OneDrive for Business connector:
Internationalization of the Windows client
With 2018.1 it is now possible to configure the Windows Client to display end-user messages in the following, local languages:
▪ Portuguese Brazilian
▪ Chinese Simplified
▪ Chinese Traditional
Bidirectional OneDrive Synchronization
Updates made to files on map points using any File Director client or the OneDrive for Business web or desktop clients are now synchronized.
Cluster Health Check
File Director now provides information relating to the performance and health of appliances. It is now possible to monitor and report upon a wide range of metrics including:
This new functionality provides the File Director administrator with the ability - via tools such as Splunk and Graylog - to monitor the health of their appliances and clusters, giving them the insight they need to drive operational performance and ensuring a high level of end user experience.
Improvements to File Delta Synchronization
With this release File Director now synchronizes the changes (or Deltas) that are made to files asynchronously. This means that files are now synchronized in a more robust, scalable and efficient way improving the end user experience whilst reducing the amount of bandwidth and server resources that are required.
This approach also ensures that uploads are not affected by any issues such as infrastructure timeouts, for example.
Smart PST Linking
When opening Outlook on a new endpoint for the first time and the Outlook profile is expecting to find a local PST file, the end user will experience an application hang whilst the file is downloaded. This is a scenario that can be common when a user is migrating to Windows 10 from Windows 7, for example.
File Director now offers the ability to unlink any remote Outlook Data Files (PST) before a user opens Outlook on a new endpoint for the first time. This occurs before the desktop has been loaded, ensuring that the end user experience is not affected whilst potentially large PST files download.
Once PST files are downloaded, File Director then performs a relink in the background, ensuring a smooth onboarding process for the end user throughout.
Removal of the 200 Worker Thread Limit per Server
The introduction of HTTP Persistent Connections also called HTTP keep-alive, or HTTP connection reuse in this release, introduces improved resource management for the File Director server. This has allowed the number of processing threads that are available to each server to be increased from 200 to 400.
The introduction of more threads means that each server can now process more requests at the same time resulting in faster response times to the File Director client.
These changes enhance the user experience when interacting with files that are being managed by File Director.
Storage connector for OneDrive for Business
File Director brokers users access to existing storage infrastructures without the need for administrators to ring-fence storage solely for the service. This unique on-premises server-agent architecture means we can solve problems companies face when trying to utilize the free storage every Office 365 user has. Using cloud storage successfully means its implementation should not impact the user experience or remove the existing enterprise control.
File Director 4.3 is our first release with a cloud storage connector. Customers upgrading to 4.3 can utilize each users 1TB of OneDrive storage for break/fix or Windows migration projects, and in virtual desktop environments.
For more information, see: OneDrive connector for Home map points
Command Line Interface
The File Director Appliance provides a sealed operating environment for the server application, configuration options for customer environments, and gives the ability to cluster the service. As part of the new OneDrive storage connector we have introduced a lightweight CLI for customers to perform more advanced tasks, such as diagnosing network communication issues.
For more information, see: Command Line Interface
Over time the features and functionality of DataNow has moved from a file access and sharing product, to a mature synchronization technology uniquely positioned to solve the common IT headaches around migration, break fix and multi-endpoint access.
As part of the Ivanti rebrand we felt it was the right time to take the opportunity to rename DataNow with a more descriptive product name. DataNow has been renamed File Director.
File Director has been updated to reflect the new company name of Ivanti (see here for more details). In addition, components on the endpoint have been updated to reflect these changes.
You may still see references to the ‘AppSense’ name used in certain areas, such as the Registry or Windows Services. This is to make the transition as least disruptive as possible for existing users of File Director.
Kerberos constrained delegation in cross realm environments
Credential Guard was introduced in Windows 10 Enterprise and uses virtualization-based security to isolate NTLM password hashes, Kerberos Ticket Granting Tickets, and credentials stored by applications as domain credentials, all so that only privileged system software can access them.
File Director 4.2 now supports constrained delegation with support for crossing realms for customers who have a requirement to use Kerberos authentication in their environment.
For more information, see Kerberos constrained delegation.
Toggle TLS 1.0
PCI compliance required us to disable SSL v3/TLS 1.0 in File Director. As outlined in this Microsoft support article configuring endpoints to default to a secure protocol (TLS 1.1 or TLS 1.2) requires the implementation of registry settings and potentially an update. Customers that are unable to implement this change can now toggle TLS 1.0 on in File Director 4.2.
In the File Director web admin console, navigate to Configuration > Advanced. TLS 1.0 support can be enabled for endpoints in the TLS 1.0 (for legacy clients) pane. Note that when enabled this is done across the cluster.
Ivanti recommends turning off TLS 1.0 support as soon as all legacy endpoints in the environment are updated or replaced.
For more information, see TLS 1.0.
New Server delta sync mechanism
DataNow 4.1 provides a new delta sync feature, built to reduce the both network traffic and the time to calculate and upload file deltas. Our SMB library supports block copies from the client endpoints.
Every step of the sync request had been optimized from client endpoint to DataNow server and on from DataNow server to the back end storage.
For more information, see File Sync.
Windows PST sync optimizations
In DataNow 4.1 we have heavily optimized the syncing of PST files, leveraging the new delta sync feature in the DataNow server. PST files can now be synchronized from the endpoint based on amount changed or time period.
PST synchronization in 4.1 sends only the local changes to the PST (that is, the delta), significantly reducing the network traffic and the time to complete the sync activity.
For more information, see PST Synchronization.
Windows client sync prioritization
Earlier versions of the Windows client would synchronize content based on discovery. In DataNow 4.1 we have moved to sync content based on age - newest first. The new sync prioritization provides users a better experience when moving from old to new devices but syncing the important content first. This is ideal in migration or break fix IT workloads.
Administrators can actively exclude files from the age priority list. This can be done by file type or size.
For more information, see File Prioritization
Appliance Set Up
Configure the Appliance
Set Up Link Based Sharing
|Which Ports do I need to configure for File Director?||How do I access my File Director log files?|
Was this article useful?
Copyright © 2019, Ivanti. All rights reserved.