Knowledge Base

Not directly as SharePoint doesn't persist its data on a file system but in a database instead. You can however map the file system of a SharePoint Server as a regular network drive in Windows. TreeSize can then process and analyze the data of that drive.

How to map the contents of a SharePoint Server as a network drive is explained here:
http://ashrafhossain.wordpress.com/2012/02/23/using-sharepoint-document-library-as-a-network-drive/

The NTFS deduplication segments files with fractionally equal content into so-called "chunks" which are moved into a the subfolder "System Volume Informaton\Dedup\ChunkStore\" (SVI) located on the corresponding NTFS partition. After the deduplication has been applied, the original files are replaced by a pointer to the corresponding chunk in the SVI directory. Two identical files will only require half of the disk space they occupied before after a NTFS deduplication. Since the original files now only contain a small pointer, the allocated disk space will be indicated by Windows with a much smaller value than before (for two identical files the occupied disk space would be indicated as "0 Byte"). To make TreeSize show the original file and folder sizes again, simply switch the view mode from "Allocated Space" to "Size". The "allocated size" shown in TreeSize is the disk space you would obtain by deleting the corresponding file

The line chart can only be shown if there was a scan of the same root folder performed at an earlier point in time. Furthermore, for a reasonable comparison the scans must have the same exlcude filters defined.

When using Excel as export format, TreeSize will create a spreadsheet with the current timestamp and save the data into this sheet.

If the same file is selected for another export, TreeSize will create another sheet and append it to the file, so you won't lose the data from the previous export.

You can also specify a "Default Export File", so you don't need to select a file, every time you want to export the data. This can be done either in the Options of TreeSize (Tools -> Options -> Columns/Export -> Excel Export -> Default Export File") or in the corresponding export dialog (File -> Export -> Export to Excel -> "Always use this filename and add a new sheet when exporting").

When the default file was defined, you can simply go to "File -> Export -> Export to Excel" and TreeSize will add the current scan data to its own Excel sheet, using the default export file.

By default, TreeSize will ask for a file name, every time an Excel report is created. If the file from a previous export is selected, the data will be overwritten.

If you would like TreeSize to create an Excel sheet for each export, you need to define a "Default Export File". This can be done either in the Options of TreeSize (Tools -> Options -> Columns/Export -> Excel Export -> Default Export File") or in the corresponding export dialog (File -> Export -> Export to Excel -> "Always use this filename and add a new sheet when exporting").

When the default file was defined, you can simply go to "File -> Export -> Export to Excel" and TreeSize will add the current scan data to its own Excel sheet, using the default export file.

Please note that this is not required when using the command line options of TreeSize. If an Excel report is created using a command line option (e.g. TreeSize.exe /EXCEL "D:\MyReport.xls" D:\), an Excel sheet will be appended if the file "MyReport.xls" already exists. Please refer to our online manual for more information about the available TreeSize command line options:
http://www.jam-software.com/treesize/online_manual/EN/index.html?command_line_opt.html

The command line options are automatically defined by TreeSize, based on your settings in the "Scheduled Task" window.

If you want to edit the command line manually, please save the current task and click on "All Tasks". In this view, please right-click the recently created task. In the context menu, click on "Edit Task in Windows". A new window will open which allows you to edit the command line options of the task manually.

This issue typically occurs if an application which extends the Windows context menu fails for some reason. In such cases, the faulting application will also crash TreeSize. Besides TreeSize, several other applications such as "WinRar" or "DropBox" extend the Windows context menu. As those applications share the same resource (the context menu) with TreeSize, an exception in one application might cause the application where the context menu is called from to fail.

Identifying the actual source of the problem is not an easy task. If the problem has occured only recently, you should check in the software list of Windows which applications have been installed recently. If one of these applications extends the Windows context menu, you should try to uninstall the application and check if the problem still persists.

For further questions or assistance please contact the TreeSize customer support under  (TreeSize@jam-software.com).


 

In general, TreeSize uses the date settings of Windows. Due to a problem in Windows 7 and Windows Server 2008 it may however display the 'wrong' date format.

To fix this problem, please open the "Regional Settings" ("Clock, Language and Region") in the Window Control Panel and click "Additional Settings". In the following dialog, click "Reset". After the confirmation, close the dialog and restart TreeSize. The problem should be fixed.

For each scan that is executed on a specific folder, TreeSize automatically saves the size from that scan for the use in the "History" view. If another scan on that same folder is done, TreeSize will add the new size data and create a graphical trend for this folder. This is the reason why you might see different periods of time for different drives and/or folders.


As you mentioned, SpaceObServer is much more powerful in regards to creating reliable statistics for the increase/decrease of disk usage of your systems. SpaceObServer scans local and network drives as well as Exchange mailboxes using a background service and stores their structure, sizes and properties in an SQL database.
In an Explorer-like user interface the collected data can be viewed and browsed in hierarchical or tabular views, 3D bar, pie, line charts and tree maps. Using the archived data you are able to track the development of the space usage from past to present, and forecast future size usage.

We are sorry but TreeSize does not yet support scanning the file system of a mobile device that is connected via USB. TreeSize supports different kind of file systems but it requires them to be mounted as a regular drive (local and/or network) to your system. An attached mobile device is usually not mounted as a drive but as an external device which uses a special kind of API which is not yet supported by TreeSize. We plan to integrate this feature for a future TreeSize release.

Given that your mobile device uses a memory card, you can however use a memory card reader which usually provides the content of the card as a file system that can be processed by TreeSize.

If you use the /GROUPSCANS switch, TreeSize combines your scan paths into a virtual root folder which is referred to as expand level 0. Following this, /EXPAND 0 will only show the virtual folder. 

/EXPAND 1 will show the virtual folder plus the given scan paths (M:\_PROJECTS" "R:\_PROJECTS in your case)
/EXPAND 2 will show the virtual folder plus the given scan paths plus their first level of files and folders. 

In order to expand the first level of each defined scan path you will need to use "/EXPAND 2".

The described behaviour does typically occur, if the evaluation period for the application has expired. You need to purchase a copy of the application in order to use it again. If you haven't installed any trial version before, please contact our support to receive further instructions.