Hello and welcome to our Knowledge Base. Our experts provide answers to the most frequently asked questions of our customers. Start your information search here to find your answer quickly and easily.
Please enter your query or select one of the above categories.
All entries (Page 1 / 15)
If we would include also the metadata of files, the XML files would grow by factor 10-20 and reach a size that cannot be handled reasoably.
If you need history datas and growth report on file level, we would likew to recommend our product SpaceObServer. It regularly collects the file system information using a background agent and stores it in a 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.
In order to store credentials for a task, TreeSize uses Windows' credential manager. However, the setting that allows to store these credentials can disabled by the Administrator, via group policy. In that case, creating new tasks is not possible.
You can change this setting by starting the security policy manager "SECPOL.MSC". Navigate to "Security Settings > Local Policies > Security Options" and locate the option "Network access: Do not allow storage of passwords and credentials for network authentication". Make sure that this setting is disabled, if you want to create an automated task.
Treesize.exe is digitally signed using an AuthentiCode certificate issued by VeriSign. One possible cause for this error is that the VeriSign root certificate is missing, so the certificate chain is broken. The Verisign root certificates are deployed through Windows updates.
There are only two possible resolutions if you want to use our products on that system:
- Install the product using our installer, or
- please make sure all available Windows updates are installed on this system.
In the unlikely case both options did not resolve the option, please point a Windows Explorer to “C:\Windows\JAM Software\TreeSize\”, right click on TreeSize.exe, select “Properties”, go to the tab “Digital Signatures”, select the item “sha256”, then press the “Details” button, then press the button “View Certificate”. Please send us a screenshot of the tab “Certification Path” of the dialog window which pops up then and a screenshot of the actual error dialog.
Yes, that is possible with the command line parameters of TreeSize Professional.
You can simply add the paths at the end of your command line to specify which paths should be scanned. For example:
"C:\Program Files\Jam Software\TreeSize\TreeSize.exe" "C:\" "D:\" "E:\"
You can also use the parameter /SCAN can to define a text file, which contains a list of paths that should be scanned when TreeSize is started.
The text file should contain a simple list of scan paths, separated by a newline:
An example command line call for this would be:
"C:\Program Files\Jam Software\TreeSize\TreeSize.exe" /SCAN “C:\scanpaths.txt”
It may also be useful to create a dedicated shortcut that executes one of these command lines. To this end, just create a shortcut to Treesize.exe, open the "Properties" dialog of the shortcut, and append the command line parameters as arguments in the "Target" field.
It seems that Carbon Black is not compatible with the license management and anti piracy component that we integrated in TreeSize. Disabling Carbon Black when using TreeSize solves the problem. To do so, perform the following steps:
- Disabling Carbon Black for the system temporarily during install.
- Editing the permissions on the Carbon Black ‘Policy’ by adding a ‘Bypass’ action for TreeSize.
A similar problem has been reported for Lumension Endpoint Security.
These type of problems can occur, if the option "Force randomization for images" (mandatory ASLR) in Windows Defender is enabled, which overrides application specific settings.Activating this setting will disregard the compatibility information of the application and can cause the application to crash immediatly, or not start at all, as is the case with TreeSize.
To fix this, you can either disable this feature completely, or add TreeSize as exception to your ruleset in Windows Defender:
Open Windows Defender Security center and navigate to "App & browser control > "Exploit protection > Exploit protection settings". Under "System settings", you can deactivate "Mandatory ASLR", or use "Add program to customize" under "Program Settings", to deactivate this for TreeSize.exe only.
Other security software like Carbon Black may also be blocking Treesize or its installer.
The user who should use TreeSize needs to have read access on the folders that should be scanned, or alternatively the user must be permitted to request the Windows backup privilege, which is the case by default for administrators. Using the Windows backup privilege TreeSize is also able to query meta data like size and last change date. It may be necessary to explicitly run TreeSize "as administrator". User do not need read access on the file content unless you want to use the TreeSize duplicate file search with options that take the actual file content into account, and not only the meta data of the files.
With Windows Vista / Server 2008 Microsoft introduced "Client Caches" with the SMB2 protocol in order to speed up the queries about gathering file and directory meta information on network drives. This approach helps also to utilize the available network bandwidth more efficient. However, these caches do always return an incorrect value for the NTFS hardlinks (always shown as "1").The responsible caches can be disabled by the following steps:
- Run "regedit.exe".
- Open the path "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters".
- Choose "New > DWORD value" in the right click menu and set the name to "FileInfoCacheLifetime" and the value to "0".
- Restart Windows
After these steps TreeSize should work properly with hardlinks. For further information about client caches please visit https://technet.microsoft.com/en-us/library/ff686200(WS.10).aspx
Our 3rd party library which manages our installation keys iterates the registry key HKEY_LOCAL_MACHINE\CLSID which takes magnitudes longer under App-V virtualization than on a normal system. A possible solution is described here: https://social.technet.microsoft.com/Forums/en-US/1648d88e-72bb-4bf9-92b3-4a803e431650/problem-to-sequence-treesize-professionnal?forum=mdopappv
We will replace the library that handles the installation in keys in TreeSize V7.1 so that this iteration will no longer take place.
Yes you can!
Please go to the 'Help' tab and click on 'Check for update'. Doing so will actually check for updates and bring up a notification window stating the result of the check. The same notification window would show up, if an automatic check has found an available update.
The checkbox at the bottom of this notification allows you to choose whether to 'Check for updates regularly'.
Read this knowledge base entry to learn how to disabale the automatic check for updates or the "Check for updates" button programatically.