Configuring Exclusions and Electives in the DataNow Windows Client

Version 8

    Verified Product Versions

    File Director 3.6File Director 3.5File Director 4.0File Director 4.1File Director 4.2File Director 4.3File Director 4.4File Director 4.5File Director 2018.1File Director 2018.3


    DataNow 3.5 and above features new rule based bi-directional exclusions which can target attributes, such as age and size.


    Additionally, a new feature called 'Elective Downloads' is also introduced which allows an administrator to define what data is excluded from being populated automatically in a user’s cache by default in automatic map points.


    If you are using an earlier version of the DataNow Windows Client, then please refer to the following article:


    Configuring Upload Exclusions in the DataNow 2.x and 3.0.x Windows Client


    DataNow Version 3.5 - 4.1 Exclusion and Electives


    DataNow 3.5 introduces advanced bi-directional client-side conditionalexclusions based on regular expressions with new criteria that can be evaluatedby type, age, size and path.

    DataNow 3.5 Exclusion Registry Keys:

    DataNow exclusions are controlled via four new registry keys:




    The FilePolicy key is concerned with file sync exclusions and elective download policies

    The DeltaPolicy key allows the administrator to control which file types are excluded from ‘delta sync’ where we only sync portions of the file that has changed.


    Exclusion expressions can be built based on combinations of:

    • File & Folder Paths
    • File Extension
    • File Age
    • File Size

    By default, DataNow excludes certain temporary files from syncing to and from the server. For reference these are:

    • Files with the extension tmp, lnk, partial, crdownload, part and download
    • Office backup files starting with ~$
    • Excel temporary files
    • Open Office temporary files
    • The Recycle Bin


    In V 3.5 (only), if any custom exclusions were defined in the registry, the implicit default exclusions were ignored

    which needed be re-added with the following expression:

    (Ext In [tmp lnk partial crdownload part download]) OR (Name == /~\\$.*/) OR (Name == /[0-9A-F]{8,8}/) OR (Name == /\\.~lock.*#?/) OR (Name == /.*~/) OR (Path == /\\$Recycle.Bin$/)

    In V 3.6 and above, the following default default exclusions apply, however do not need to be re-added to the policy. If you want to override any of the default exclusions, simply add them to the 'Exclusion Override' section (see below):

    (((Ext In [tmp partial crdownload part download]) OR (NOT ServerLocking AND (Name == /~\\$.*/)) OR (Name == /[0-9A-F]{8,8}/) OR  (Name == /\\.~lock.*#?/) OR  (Name == /.*~/))  AND Type == File) OR (Path == /.*\\$Recycle.Bin.*/)

    This expression is added as a registry string value with an arbitrary name under the following key:


    NOTE: Regex is case sensitive so the map points and folders must be written as they appear on the file system.  This means that the home Map Point, must be specified with a lower case h (home). Alternatively the /i switch can be used to make the regex case insensitive  (but be aware this is only supported on V4 and above)



    The following example, demonstrates configuring DataNow so that it will only sync files that are younger than 1 year AND under 100MB but NOT Word or excel files (these can sync regardless of size / age).

    First configure the exclusion:

    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\Exclusions
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Age> 1Y And Size > 100Mb"


    This puts a blanket bi-directional sync exclusion on files matching both of the above criteria (you could use the OR statement if you wanted to block either).

    The Exclusion Overrides key can be used to add exceptions to all configured rules, including overriding the default exclusions, and are evaluated after all exclusion rules have been processed.

    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\ExclusionOverrides
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Ext In [doc docx xls xlsx]


    Note: if an exclusion is applied that matches existing in-sync data, the exclusion for that data is ignored and will continue to sync changes, invoked locally or out-of-band. If new content is created that matches the exclusion filter, then the exclusion will be applied.


    Electives are synonymous with ‘Automatic’ map points, and offers a way to administratively override content from being synced down to a user endpoint by default on an automatic map point.
    Electives are defined in a similar way to exclusions, with same degree of granularity:
    DataNow 3.5 and above Elective Registry Keys:
    As per exclusions, elective expressions can be built based on combinations of:
    - File & Folder Paths
    - File Extension
    - File Age
    - File Size
    In the following Elective policy configuration example, an automatic map point will download everything to an endpoint except for .ISO or .EXE files that are over 500MB and older than a year, unless they’re in a specific folder (\ImportantISOs) in which case they will be downloaded automatically:
    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\Electives
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Ext In [iso exe] And Size > 500Mb And Age > 1Y
    The above rule creates a 'blanket' elective rule to apply to all files with an extension of .iso or .exe
    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\ElectiveOverrides
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Path == /ImportantISOs\\.*\..*/
    The above rule overrides the blanket rule to ensure that any file in the 'ImportantISOs' folder will sync automatically
    If you want to create an elective rule to, for example, mark all files in an automatic map point (Home) as elective downloads (manual) EXCEPT for those in two sub-folders, you could use the following example:
    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\Electives
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Path == /.*\\home\\.*/
    and the override:
    Registry Key: HKCU\Software\AppSense\DataNow\FilePolicy\ElectiveOverrides
    Value Type: REG_SZ (String)
    Value Name: (arbitrary)
    Value Data: Path == /.*\\home\\AutoSyncFolder1\\.*/ OR Path == /.*\\home\\AutoSyncFolder2\\.*/

    NOTE: Regular expressions are case sensitive. See Solution 150622351968622 for further details


    Upgrade information:
    If upgrading from V2 or V3.0 and you have pre-existing exclusions defined, be aware that these are NOT automatically converted to V3.5 syntax and will need to be re-added.
    4.1 update 1 changes
    DataNow exclusions have been enhanced as of 4.1 update 1 (4.1.545.0)
    Headline features are:
    - Exclusions are now actioned at the driver level for much better performance
    - The use of variables is now supported in expressions
    - There is a new 'beneath' feature to simplify common path exclusions
    - The default exclusion list has been expanded to support 'Total Profile Sync' (TPS)
    - We no longer sync Internet Explorer favorites or LNK files - these are best handled by Environment Manager Personalization (but can be overriden if required using exclusion overrides)
    The default exclusions in 4.1 update 1 are as follows:
    Path Exclusions:


    File Exclusions:
    (((Ext In [tmp partial crdownload part download]) OR
    (NOT ServerLocking AND (Name == /~\\$.*/)) OR  (Name == /[0-9A-F]{8,8}/) OR(Name == /\\.~lock.*#?/i) OR (Name == /NTUSER.DAT.*/i) OR (Name == /NTUSER.INI/i) OR (Name == /.*~/)) AND Type == File)


    'Beneath' feature - this can be used to exclude all content in a given path


    It can also be used to override the default 'favorites' exclusion, for example:

    BENEATH == “%userprofile%\favorites”

    CAUTION: Because the DataNow driver will ignore requests under these paths, it is not possible to place a high level 'Beneath' exclusion followed by a deeper path exclusion override.


    Additional Notes for customers using OneDrive map points
    When using OneDrive map points, there currently is an additional caveat when configuring exclusions and electives on the File Director Windows Client. The OneDrive API returns a file size and age for folders when queried by the DataNow server, this means that in certain configurations, unexpected behaviour may be observed with exclusions or electives applying to folders instead of files. To mitigate this, when configuring exclusions or electives for OneDrive map points that are only intended to target files, modify the syntax as follows:
    The example below shows syntax to configure an elective for items older than one year:
    Age > 1Y
    When using OneDrive, to ensure that the item only applied to files and not folders, the syntax should be modified to:
    Age > 1Y AND Type = File