This tool allows you to move your offline files cache to a different volume. By default it is created on the root volume.
If space is becoming low on the root volume, you will need to move the cache to a different volume and allowing Offline Files access to more disk space.
To run the program, decide onto which volume you wish to place your offline files cache. Make sure you have access to the volume and that there is free space on it. Then launch the program and select the volume from the list displayed. CacheMov will then proceed through the steps of moving the cache and setting up the necessary security on it.
Requirements :
- You must be an Administrator to run this program.
- You can only move the cache to a local fixed disk. You cannot place the cache on a network drive or a removable drive.
- If you move the cache to a non-system drive and then do something to change the drive letters on the system, Offline Files may not work correctly.
- It is a good idea to back up important files periodically. Although this tool has been tested thoroughly, further measures should be taken to protect your data from power failures and other contingencies.
- It is best to keep the cache on an NTFS drive, so that non-administrators will not have access to the cache's internal files. However, Offline Files will function properly from a FAT or FAT32 volume as well.
Unattended Mode
To run CacheMov in unattended mode, use the following command line:
cachemov -unattend v:
where v: is the volume to which you wish to move the cache.
All results are logged to the Application Event Log. The DLL is needed only for unattended setup, and must be in the same directory as the Cachemov.exe executable.
File Required
Cachemov.exe
Cchmvmsg.dll
Troubleshooting : CSC Does Not Synchronize Files But Reports That Synchronization Was Successful
During the synchronization process, a temporary file gets generated. If the drive is formatted with the NTFS file system, the user who is running the synchronization must have modify permission to the location where the temporary file is created. The synchronization process looks for a temporary folder in the root of the drive that holds the CSC folder. If a temporary folder does not exist, the synchronization process writes the temporary file in the root of the drive itself.
For example, by default the CSC folder is located in the %SystemRoot% folder. If the %SystemRoot% folder is located on drive C, the CSC cache is in the C:WinntCSC folder. The synchronization process then looks for a C:Temp folder to write the temporary file into during the synchronization. If the CSC folder is moved to another partition by using the Cachemov.exe utility, the synchronization process looks at that drive for the temporary folder. If the temporary folder does not exist, it then writes the temporary file to the root of that drive.
This can be a problem if users are not given NTFS permissions to write to the root of a drive. If the temporary file cannot be created, the modified files never get synchronized with the server. (From support.microsoft.com)
No comments:
Post a Comment