Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.
Categories: TreeSize | Show all categories
In our customer area, you can find an offer to upgrade to this version at a discount.
To change this, please use the command line parameter /SIZEUNIT N
For more information on this, please refer to this page in the manual for TreeSize.
The XML export's purpose is to be used to save a complete scan and to be able to load it later on, as well as using it for comparisons.
If you are only interested in the top level or a low depth, please consider using the Excel or CSV export instead.
It is also possible to reduce the size of the XML file by disabling the statistics for age of files, file owners and extensions in the scan settings.
If a SharePoint Online site is configured to require a multi-factor authentication, TreeSize will perform a browser based authentication. For a detailed explanation on how to set everything up, please refer to this page in our user manual.
TreeSize offers the possibility to use filters for this. Please navigate to "Scan" -> "Filter" -> "Customize filters". There you can define criteria to exclude files or directories.
Two examples:
1: Name does not match thumbs.db would only include objects that are not named "thumbs.db" (= excludes files that have this name).
2: Full Path does not start with C:\Windows excludes the "C:\Windows" directory and all its subfolders and files from the scan.
This is possible by using the advanced search and using the following filter:
Name matches pattern *.
In general, the exporting speed highly depends on the amount of data that is exported.
Exporting single files massively increases the amount of data for the export so if you do not need to include individual files, setting the export to only include folders and file nodes is a very good idea.
It is recommended to remove all columns from the export that you do not need.
Besides these factors, there are certain columns that are known to slow down the export by a lot. Especially SHA256 takes a lot of time but the MD5, "Owner" and the "Permissions" columns can increase the duration by a noticeable amount as well.
The "File Content" comparison method uses MD5 checksums by default for the comparison.
If you wish to change this to SHA256, you can go into the file search options, enable the expert mode under "View" and after that you can find the setting in the "Search Engine" category under the headline "Duplicate Search - File Content".
Unfortunately, this is not a supported feature at this point.
That is because there is no universal flag for such files and there would have to be a unique implementation for every file type that can potentially be password-protected.
A list of scan targets that are supported by TreeSize and TreeSize File Search can be found here.
