There's an outside chance a robocoy or richcopy might re-mark the attributes once there then, but I've never tried.
If not, then you might have to be like Nineh Cherry and take a Buffalo Stance. -sc From: David Lum [mailto:[email protected]] Sent: Tuesday, January 19, 2010 10:08 AM To: NT System Admin Issues Subject: RE: Buffalo NAS - weird read only issue Kind of what I figured. Yes you can mark it RO once it's there. I just checked another client with a Buffalo NAS, same issue. Who knew? From: Steven M. Caesare [mailto:[email protected]] Sent: Tuesday, January 19, 2010 6:43 AM To: NT System Admin Issues Subject: RE: Buffalo NAS - weird read only issue Chances are it's using something samba-ish on the NAS for the CIFS connectivity, and a filesystem that may not be FAT on the discs. I'm not sure that they support file attributes, as opposed to file permissions. Can you re-mark it as RO once it's on the device? -sc From: David Lum [mailto:[email protected]] Sent: Tuesday, January 19, 2010 9:37 AM To: NT System Admin Issues Subject: Buffalo NAS - weird read only issue I have a client with a Buffalo NAS and if they have a file marked read only on an PC and they move it to the NAS the read-only attribute is stripped. Same thing for moving from folder to folder on the NAS. Has anyone else seen this before? Any idea if there's a way to fix it? It has to be due to how the folder is shared or how the file system in Unix-y, but I can't find any kind of setting that mighty change the behavior. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
