J
John Myers
I have a strong feeling that the way junctions are being treated in NTFS
needs to be revised. The issue I see is that, once I have created a junction
from, say C:\FolderTarget pointing to D:\FolderSource, if I check permissions
on C:\FolderTarget, I will see the permissions of that folder, NOT the ones
of D:\FolderSource. Worse, if I change permission for C:\FolderTarget, none
of these changes will be propagated to subfolders/files in D:\FolderSource.
So, let's say I decide that I want to move my Public folders in Vista to a
separate partition. No problem, I move the files over, and create a junction
in C:\Users\Public pointing to the new location. HOWEVER, now Public Folder
Sharing will not work anymore (not from the Network and Sharing Center,
anyway): If I turn Public Folder Sharing on, then Vista will change
permissions for C:\Users\Public accordingly, but since this has no effect on
the permissions of the files at my new location, network users will not be
granted access to any of the files. The only way to give users access to
these files is to change file and sharing permissions of the source folder
manually.
I think what should be done is this: When I create a junction, the system
should check if the source and target folders have identicakl permissions. If
not, it should offer me to change permissions on either the source or the
target folder so that they are identical. Then, if I change permissions on
the target folder, permissions on the source folder should be changed in
lockstep.
Anybody with me on this one? Anybody care? ;-)
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://windowshelp.microsoft.com/co...ndows.vista.administration_accounts_passwords
needs to be revised. The issue I see is that, once I have created a junction
from, say C:\FolderTarget pointing to D:\FolderSource, if I check permissions
on C:\FolderTarget, I will see the permissions of that folder, NOT the ones
of D:\FolderSource. Worse, if I change permission for C:\FolderTarget, none
of these changes will be propagated to subfolders/files in D:\FolderSource.
So, let's say I decide that I want to move my Public folders in Vista to a
separate partition. No problem, I move the files over, and create a junction
in C:\Users\Public pointing to the new location. HOWEVER, now Public Folder
Sharing will not work anymore (not from the Network and Sharing Center,
anyway): If I turn Public Folder Sharing on, then Vista will change
permissions for C:\Users\Public accordingly, but since this has no effect on
the permissions of the files at my new location, network users will not be
granted access to any of the files. The only way to give users access to
these files is to change file and sharing permissions of the source folder
manually.
I think what should be done is this: When I create a junction, the system
should check if the source and target folders have identicakl permissions. If
not, it should offer me to change permissions on either the source or the
target folder so that they are identical. Then, if I change permissions on
the target folder, permissions on the source folder should be changed in
lockstep.
Anybody with me on this one? Anybody care? ;-)
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://windowshelp.microsoft.com/co...ndows.vista.administration_accounts_passwords