Hi Andy,
I want to explain a few things before I answer your questions.
The folder that you're trying to access,
C:\Documents and Settings\All Users\Application Data isn't actually a folder, it's what's known as a junction point. It's just a compatibility feature of Windows Vista and Windows 7 as it redirect calls to this folder to another location.
There is a junction point for
C:\Documents and Settings goes to
C:\Users, so the folder you're trying to access is actually:
C:\Users\All Users\Application Data
Well, it would be if this was a folder - there's one more junction point in there.
C:\Users\All Users\Application Data is a junction point redirecting files to
C:\ProgramData <-- This is the folder that you have changed the ACL for. You can't double click on junction points to see where they go, instead you have to use a program to view them, of which I would recommend
NTFSLinksView (by NirSoft).
So you have effectively taken permission of
C:\ProgramData.
Code:
==================================================
Name : Application Data
Full Path : C:\Users\All Users\Application Data
Type : Junction
Target Path : C:\ProgramData
==================================================
==================================================
Name : Desktop
Full Path : C:\Users\All Users\Desktop
Type : Junction
Target Path : C:\Users\Public\Desktop
==================================================
It's strange that the Desktop folder has the same permissions as Application Data. They're the same on my system, but I haven't changed either of them.
You don't need to specify a location to save the ACL export because it will just save it in the folder that command prompt has been run in. If it displays C:\ with a blinking underscore, it will be saved there. That's why this all had to be done from the same window, so it could grab the export without me having to specify a location.
Considering they're the same, you can ignore my instructions then as it wouldn't do a thing.
Yeah, I was trying to replace the ACL of Application Data with that of Desktop.
You haven't mucked anything up!
If the restore point was made before the command was run, then yes, it should fix this. Give it a shot, and let me know how it goes
Tom