The file tracing function cannot be used according to the compression and decompression log of the compression software (such as the ZIP, LZH, and compression tools provided by Microsoft).
The application operation log of adding functions on Internet Explorer(R) or Windows Explorer will not be collected.
When the OS is Windows Vista(R), Windows Server(R) 2008, Windows(R) 7, Windows(R) 8, or Windows Server(R) 2012, if authority upgrade is allowed through UAC and operation is continued, the program name in the collected log is displayed in Content of Log List of Log Viewer).
When the file displayed in the Open File dialog box exists, even if the file is not opened, the viewing log will be collected.
When a large file is copied, a large number of file operation logs will be collected.
Under the following conditions, the file size may not be obtained normally.
When a file is moved and renamed repeatedly or the device that stores the processed file is added, deleted, and ejected within 30 seconds.
When file operations are performed before logoff or shutdown.
When you use the TEMP or TMP user environment variable in Windows Explorer to create a file, "Create" logs will not be collected.
When Excel file operation logs are collected, "View" logs are created even under the following conditions:
Excel containing a link to another sheet is reference, and
There is no link destination file
When you use WordPad to update a docx file in Windows(R) 8 or Windows Server(R) 2012, an "Update" log may not be output.
When you run the "Save as" operation, "Save as", "Create", and "Update" logs may be collected.
When you shut down or restart immediately after an operation that generates a large volume of logs (*1), some logs generated before the restart may not be collected.
When you perform such an operation, wait a while before performing shutdown processing.
After an operation that generates a large volume of logs, Systemwalker Desktop Keeper processes may temporarily experience high load.
This is not an issue if the high load is temporary, but if it occurs periodically, take measures such as removing folders for which a large volume of logs are likely to be created.
*1: For example: Operations such as batch copy and deletion of folders that contain several tens of thousands of files
Regular file operations that use batch processing
When the following software or command is used, the file operation log will be collected as described in "8.2.19 File Operation Log".
Windows Explorer
Notepad
Wordpad
Microsoft(R) Word (2003, 2007, 2010, and 2013)
Microsoft(R) Excel (2003, 2007, 2010, and 2013)
Microsoft(R) PowerPoint(R) (2003, 2007, 2010, and 2013)
Commands in the Command Prompt window (COPY, XCOPY, MOVE, DEL, ERASE, RD, REN and MD)
However, pay attention to the following items.
The "Update" operations (such as Save As and Replace) of Microsoft(R) Word are collected as the log of Create operation.
In Microsoft(R) Word, Excel, and PowerPoint, the "Create" operation may be collected as an "Update" log (Microsoft(R) Office 2013).
Same as Windows Explorer and XCOPY, for a process registered in the File operation, if the scope of file operation log of this process is set to Get operations excluding viewing, the View logs of the process will not be collected.
The excessive logs that are not listed in "8.2.19 File Operation Log" may be collected sometimes even when the software or command mentioned above is used.
When the software or command apart from the above is used, the operation log that does not conform to the actual operation may be collected sometimes (For example, "Copy" or "Move" logs cannot be collected, but they will be collected as View, Create, Delete, or Rename operation.
When the "Move" operation is performed in the above software or commands, "Copy" and "Create" (move source) logs may be collected.
When the Redirect command (> or >>) or MD command is run in Command Prompt, logs cannot be collected.
When the data in the local drive is written to a DVD/CD by using the burning software, this operation can only be collected as a View operation instead of Copy because information of access to DVD/CD cannot be collected.
For output to a tape device, communication through cross cable such as RS-232C, or operation via IrDA (Infrared device), since the information of target drive cannot be obtained, only the information of local drive will be collected during log collection.
When moving a large file (it takes more than 30 seconds to move one file), the log may be divided into two pieces sometimes, which are Copy and Delete.
When the Move command is used to move a file by overwriting in the same drive, if the overwriting operation is performed after the prompt for confirmation of overwriting is displayed for more than 30 seconds, the log will be Rename instead of Move. When other commands are used, if the conformation prompt is displayed, the collected log may be different from the actual one sometimes.
If the COPY or XCOPY command such as COPY A.TXT+B.TXT C.TXT or COPY *.TXT C.TXT is executed in Command Prompt, it will be collected as the Create log of C.TXT.
A maximum of 259 halfwidth characters (129 fullwidth characters) can be collected as the information of File Name, Target File Name, or Source File Name in a collected log.
When a path that does not exist is specified in the file operation of command prompt, the operation will fail, but the log will still be collected.
When the operation of displaying the confirmation window is performed, even if the operation is cancelled, the file operation log will still be collected.
In Windows Vista(R), Windows Server(R) 2008, Windows(R) 7, Windows(R) 8, or Windows Server(R) 2012, when the operation of displaying the confirmation window (copy by overwriting, move by overwriting), the log type will not be recorded as Copy or Move. The collected logs will be the "Update" log of the copy destination file or move destination file, the "Delete" log of the move source, and the "Rename" log of the copy source file and copy destination file, or the move source file and move destination file, if the same drive is used.
Under virtual environment, the file name of physical drive of drive mapping may contain extra information sometime [\\Device\PicaDriveRedirector\].
Example: [\\Client\F$\Customer\CustomerInformation.xls] will be obtained as [\\Device\PicaDriveRedirector\Client\F$\Customer\CustomerInformation.xls].
In a virtual environment, when you operate a file from the command prompt, the full path may not be obtained for the file name of physical drive of drive mapping.
Example: [\\Client\F$\Customer\CustomerInformation.xls] will be obtained as [\\CustomerInformation.xls] or [\\Customer\CustomerInformation.xls]
In a virtualization environment, operation logs may not be obtained for files that have a size of 0 bytes.
In a virtualization environment, superfluous "Create" logs may be obtained when you perform file operations.
In a virtualization environment, folder operation logs may not be obtained.
When you perform file operations in Microsoft(R) Office, operation logs may be obtained for the temporary files (such as .dll, .dat, and .lnk) that are created by the operating system.
When you use Microsoft(R) PowerPoint and save all pages in an image format (such as jpg or tif), a separate image file is output for each page. However, a "Save as" log is recorded only for the page image file for which you specified the file name in the Save as dialog box. The file operation logs for the other pages are recorded as "Create" logs.
When you operate (such as update or rename) a file after creating it, a "Create" log may not be output.
When collecting operation logs, register the process that requires the file operation log to be recorded in the File operation. At the time, If the Select according to Extension option is set to Get all extensions, information about all files accessed by the process (application) will be collected Apart from data file, these files also contains execution modules and temporary files such as files with "exe", "dll", "ini", "tmp, "lnk" or "inf" extensions. All these operation logs will be collected.
The operation log of playing music CDs cannot be collected.
An operation log cannot be collected when you directly save data in Internet storage.
The file operation log relating to network drive to be collected is the file and folder operation performed for computers in the network from the client (CT) of Systemwalker Desktop Keep.
The file operation log relating to network drive is displayed in UNC format or the UNC format in which part of the computer name is IP address. However, in the following conditions, the Target File Name information of log will be displayed with the absolute path of file name or folder name.
Allocate a drive letter for the network drive and perform rename operation in the drive letter
Allocate a drive letter for the network drive and perform move operation in the drive letter.
For the drive letter that is allocated as a network drive, perform the move operation from the folder that directly accessed to the network drive with the same drive letter as the allocated one.
For moving operations between the drive letter that is allocated to a network drive and the folder that directly accessed to the network drive with the same drive letter as the allocated one, the logs listed in "8.2.19 File Operation Log" will be collected, but the following information in the collected logs, however, may be different.
In File operation > About log of files under the folder > In same drive, logs of Rename instead of x will be collected.
In File operation > About log of folder > In same drive, logs of Create, Delete, and (Delete) instead of Rename, (Rename), and (Delete) will be collected.
When you delete a file from the network drive (including access via a UNC path) in Windows(R) 8 or Windows Server(R) 2012, a "Delete" log may not be output.
When you move a file from the network drive (including the access time in a UNC path) in Windows(R) 8 or Windows Server(R) 2012, the "Move" log may be output as a "Copy" log.
Based on the setting of the excluded folder for obtaining the file operation log, even for built-in disk, when the OS identifies it as a removable drive, the disk will not be excluded.
Even if the excluded folder is enabled, the operation logs related to the folders that are not excluded will be obtained.
All the folders, subfolders, and files under an excluded folder are targets to be excluded.
When modifying the configuration value of system environment variable TEMP and TMP, the value after modification will take effect after the next startup of OS. The configuration value prior to modification will be used before the OS is restarted.
When modifying the configuration value of user environment variable TEMP and TMP, the value after modification will take effect upon the next user logon. The configuration value prior to modification will be used before the next logon.
When only symbols such as "\" and "\\" have been set in the configuration value of TEMP and TMP of system environment variable and user environment variable, the setting will be invalid.
"\" indicates that the root directory of current drive while the program is running, but it will not be excluded because it cannot be fixed.
In addition, "\\" indicates the beginning of network path in UNC format, but it is meaningless when it contains only "\\", and it will not be excluded at this time.
When the folders of system environment variable TEMP and TMP and the temporary Internet files are specified to target for exclusion if the file name is a path of more than 260 halfwidth characters (130 fullwidth characters), the exclusion setting will be invalid and the file operation log will be collected.
However, if the path is 260 halfwidth characters (130 fullwidth characters) and the 260th character is "\", the setting will be valid.
When the path of excluded target in Windows Vista(R), Windows Server(R) 2008, Windows(R) 7, Windows(R) 8, or Windows Server(R) 2012 contains dedicated Unicode characters, it will not become the target for exclusion.
