If your users have Offline Files enabled, and you try to delete those files 
locally on their hard drives, they'll get re-synched with the online source 
(fileserver) at the next sync time.

To get rid of the offending files in the CSC (Client side cache), you should 
remove them from the real source on the server and it will remove them when it 
synchs up if their Offline files are working.  You can look in Sync Center 
(Windows 7 & Up) to see what's going on for a client.

The directory structure you're seeing is how it has been changed in Windows 7 
and later. You aren't supposed to manage those directories explicitly in 
Windows 7 and up.  You can do it with XP if memory serves.

Last year, I went through a huge amount of time getting the offline files 
issues straight when we were doing file server migrations.  This really showed 
up where users had their "My Documents" redirected to the server and Offline 
Files was enabled via GP.

You can manage these directories (meaning the client side cache) with some VB 
code that Microsoft provides - look at the link for KB977229 below.

Here are some links that may help explain it a bit more...
https://community.spiceworks.com/topic/1105563-demystify-offline-files

This link has the VB code and explantion:
https://support.microsoft.com/en-us/kb/977229

And another one with more links ;)
https://social.technet.microsoft.com/Forums/en-US/cb503d98-8878-45d5-a692-8a12684bc888/windows-7-32bit-offline-folders-file-server-replacement?forum=w7itproinstall

Don K

<https://social.technet.microsoft.com/Forums/en-US/cb503d98-8878-45d5-a692-8a12684bc888/windows-7-32bit-offline-folders-file-server-replacement?forum=w7itproinstall>



From: [email protected] [mailto:[email protected]] On 
Behalf Of [email protected]
Sent: Friday, November 6, 2015 12:02 PM
To: [email protected]
Subject: Re: [NTSysADM] RE: Folder in c:\Windows

Offline Files....shudder
Sent from my BlackBerry(r) smartphone on O2
________________________________
From: Daniel Chenault <[email protected]<mailto:[email protected]>>
Sender: <[email protected]<mailto:[email protected]>>
Date: Fri, 6 Nov 2015 09:27:29 -0800
To: 
[email protected]<[email protected]<mailto:[email protected]%[email protected]>>
ReplyTo: <[email protected]<mailto:[email protected]>>
Subject: RE: [NTSysADM] RE: Folder in c:\Windows

http://blogs.msdn.com/b/oldnewthing/archive/2003/08/27/54712.aspx

c:\windows\csc is "client-side caching" or what used to be called offline 
files. Disable that first.

________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] RE: Folder in c:\Windows
Date: Fri, 6 Nov 2015 17:24:15 +0000
Take ownership and then replace the permissions? You need local admin for that, 
which I am assuming Domain Admin should have

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Richard McClary
Sent: 06 November 2015 17:20
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] Folder in c:\Windows

Greetings!

Working though PCI-DSS compliance, we run "Identity Finder", which scans all 
workstations and servers searching for credit card information.  We need to 
delete those files.

Problem-

We have about a dozen files in a folder, 
"C:\Windows\CSC\v2.0.6\namespace\aspca\mwo\HomeShares\[User Name]".  It seems 
being a Domain Admin is insufficient for access to this folder.  (At least 
remotely, using either Windows Explorer or "Hyena".)

Worse, we find files of the same name elsewhere in the file system and delete 
them.  However, the copy in this inaccessible folder restores it.

How to get into that folder to delete the offending files?

Thanks!
The information contained in this e-mail, and any attachments hereto, is from 
The American Society for the Prevention of Cruelty to Animals(r) (ASPCA(r)) and 
is intended only for use by the addressee(s) named herein and may contain 
privileged and/or confidential information. If you are not the intended 
recipient(s) of this e-mail, you are hereby notified that any dissemination, 
distribution, copying or use of the contents of this e-mail, and any 
attachments hereto, is strictly prohibited unless authorized by the sender. If 
you have received this e-mail in error, please immediately notify the sender by 
reply email and permanently delete this e-mail and any printout thereof.

Reply via email to