Microsoft KB Archive/303256

= Cachemov Does Not Work on Localized Versions of Windows 2000 =

Article ID: 303256

Article Last Modified on 1/31/2007

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2

-



This article was previously published under Q303256



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
If you are using a localized version of Windows 2000 and you attempt to use the Cachemov utility from the Microsoft Windows 2000 Resource Kit on an NTFS drive, you receive the following error message at the &quot;Check the Destination&quot; stage:

Failed to reset security on cache. Move cannot continue.



CAUSE
Cachemov uses the name of the Administrators group instead of the well-known security ID (SID) to build the Access Control list (ACL) for the new folder. This does not work on standard localized versions of Windows 2000 because this group name is localized.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this issue, use any of the following methods:  Rename the existing Administrators group to &quot;Administrators&quot;. Create an &quot;Administrators&quot; group that you populate with the appropriate members. Add this group to the ACL of the target folder manually with Full Control rights. Reformat the target volume with the FAT16 or FAT32 file system. You can later convert the volume to NTFS. Make sure to set the security on the folder to the default for the local CSC folder (Administrators and SYSTEM have full control). For new deployments, the CSC directory can be created in a different location during or right after installation, before any files are cached. To do this, create this registry key:

HKLM\Software\Microsoft\Windows\CurrentVersion\NetCache

Value: DatabaseLocation

Type: REG_SZ

Data:

This approach won't work when CSC is already using the existing directory.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
When you are using client-side caching (CSC) and you are running short on space on the system volume, among other options to free up space (such as moving the paging file), you can move the CSC data to a different volume by using Cachemov.

Keywords: kbnofix kbwin2000presp3fix kbprb KB303256

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.