The main reason for this is that if we included the data of single files, the exported XML files would grow considerably and reach a size that cannot be handled reasonably.
Other export types, like Excel or PDF for example, allow including single files if it has been configured like this in the settings.
Since v9.0 you can also export the whole scan, including single files to an SQLite file. These database files can be reimported and worked with in TreeSize, just as you already know it from the XML files.
In case you need data like history data or growth reports on file level, we would like to recommend our product SpaceObServer. It regularly collects the file system information using a background agent and stores it in an SQL database, including size development and (optionally) all permissions. The reporting is faster and more flexible compared to TreeSize, because it is built on a database and collects data on file level. SpaceObServer offers advanced scripting capabilities through OLE Automation.
Yes. This web page provides an overview on the permissions reporting capabilities of TreeSize.
Right clicking on the header of the Details list will show a popup menu that allows to choose additional columns showing the permissions.
If you export a scan to Excel, these columns will be included as well. (To get a full report in Excel, you need to check-mark the option "Tools > Options > Export > Excel > Export the full directory branch" and optionally "Include single files in export"). Excel Auto-Filter is a good tool to filter the exported lists for specific users or groups, or to find folders or files where inherited permissions are mssing or own permissions are added.
Our advanced disk space and file manager SpaceObServer has better reporting capabilities for permissions.
Are the "Owner" or the "Permissions" column active and part of the export? In Active Directory environments, Windows can take a long time to query these values. To speed this up, please disable these columns if they are not needed.
You can compare a scan to another folder using "Scan > Compare with path". This will show the size and file count differences on folder level between the path that was scanned, and the one that was selected for comparison.
No. TreeSize does not actively change the archive bit, and the system only changes the archive bit if a file is written. TreeSize works strictly read-only when scanning and searching and also does not modify the last access date if possible,
This error code indicates that the root certificate is not trusted on the system. We just recently updated the certificate we used to sign our applications, so it still seems to be the case that this root certificate is not yet up to date.
These certificates are usually being updated and installed online and/or along with Windows updates. These updates might be disabled manually though.
Please check for pending or available Windows updates first.
If this doesn't work, please try to download and install the updated certificates manually. They are issued from GlobalSign and should therefore be considered safe:
Root certificate https://secure.globalsign.com/cacert/codesigningrootr45.crt
Intermediate certificate https://secure.globalsign.com/cacert/gsgccr45evcodesignca2020.crt
Please ensure to install the root certificate to the correct store (root certificates). Having Windows select the store automatically, it might select the wrong store for this certificate.
You can choose the NAS as a regular scan target in the scan dialog if it is either mapped to a drive letter or has a UNC path that you can use. It is currently not possible to access a NAS over a https:// address.
You can use the duplicate search of the file search that is integrated into TreeSize for this use case.
Please open the duplicate search and select both the source directory, as well as the destination directory, as search paths.
In the "Duplicate Search" ribbon, you can choose "Unique files" and use it in combination with the (default) comparison method "File Content". Now, when running a duplicate search, instead of finding all duplicate files, only files that do not have a duplicate file are shown in the result list.
If no files are found, it means every file has a duplicate and this indicates that the copy operation worked fine.
To grant permissions on the respective site collections to be scanned via TreeSize/SpaceObServer, the PowerShell cmdlet Grant-PnPAzureADAppSitePermission can be used.
The user that is used for granting the permission must be a site collection admin of the respective site collection. The role 'Owner' is not sufficient.
For more information about the used cmdlets please see: https://pnp.github.io/powershell/cmdlets/
For files, the value of the file itself is taken. For folders, the highest value of all child elements and optionally (this setting is enabled by default) the value of the folder itself is used.
If you do not want TreeSize to use the value of the folder itself, you can enable the option "Include only file dates in folder date calculation" in the "General" options.