Hi all,

We are using 2 Windows 2000 Servers in 2 distant sites (connected trhough
a slow link) and use DFS (distributed file system) to replicate some shared
resources. Let's say we have \\SERVER1\Orders and \\SERVER2\Orders . Under
those 2 shared folders, a hierarchical tree of order numbers appear:

01000-01999
01100-01199
01100
01101
01102
....
01199
01200-01299
...
01900-01999
02000-02999
02000-02099
02100-02199
..
02900-02999

Within the leaf directory of the tree, users save documentation regarding
the order of the same number. They need rights to create, delete, update
files within those final directories. Even to create new directories under
that one if the order is too big and they need to organise themselves for
that order.

We have almost 3Gb of information shared this way, and perfectly
replicated through DFS. Every order is easily localised inside its own
directory grouped by thousands, hundreds and finaly its own directory.

And here is the problem: Users sometimes make a mistake and do a 'drag and
drop' without noticing. It has happened us some times. When they move one
(or several) directory(es) to another place some problems arise:
1. Replication to the other site collapses the link for several hours/days
depending of the amount of data moved.
2. Later on, users are not able to find those orders anymore (since the are
not in their logical place) and...
3. Call the administrator (me) to solve the problem (which sometimes means
doing a partial restore of most recent backups and having to wait again for
the replication to complete).

And here is my question: Is there any way to prevent MOVING of
directories? I have tried almost everyghing using NTFS access rights, but I
always reach to a point of no return: for example, if I set rights to not
being able to delete files or directories, users cannot either delete nor
rename directories they try to create themselves using explorer (explorer
first creates a folder called 'New Folder' and then tries to rename it to
whichever name you wanted later).

I think NTFS handles MOVING of files as is a proccess of renaming the
file, but I have not seen any right dealing with renaming either.

Any light on this subject would be greatly appreciated. Thanks for
everything in advance.

In Ntfs, the same rights that control delete also control
"rename-within-a-directory"
and "rename-across-directories". So the answer is... you can't do this.
Sorry!


--
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.




"David Lightman Robles" <dlightman@_nospam_iname.com_nospam> wrote in
message news:(E-Mail Removed)...
> Hi all,
>
> We are using 2 Windows 2000 Servers in 2 distant sites (connected
trhough
> a slow link) and use DFS (distributed file system) to replicate some
shared
> resources. Let's say we have \\SERVER1\Orders and \\SERVER2\Orders . Under
> those 2 shared folders, a hierarchical tree of order numbers appear:
>
> 01000-01999
> 01100-01199
> 01100
> 01101
> 01102
> ....
> 01199
> 01200-01299
> ...
> 01900-01999
> 02000-02999
> 02000-02099
> 02100-02199
> ..
> 02900-02999
>
> Within the leaf directory of the tree, users save documentation
regarding
> the order of the same number. They need rights to create, delete, update
> files within those final directories. Even to create new directories under
> that one if the order is too big and they need to organise themselves for
> that order.
>
> We have almost 3Gb of information shared this way, and perfectly
> replicated through DFS. Every order is easily localised inside its own
> directory grouped by thousands, hundreds and finaly its own directory.
>
> And here is the problem: Users sometimes make a mistake and do a 'drag
and
> drop' without noticing. It has happened us some times. When they move one
> (or several) directory(es) to another place some problems arise:
> 1. Replication to the other site collapses the link for several hours/days
> depending of the amount of data moved.
> 2. Later on, users are not able to find those orders anymore (since the
are
> not in their logical place) and...
> 3. Call the administrator (me) to solve the problem (which sometimes means
> doing a partial restore of most recent backups and having to wait again
for
> the replication to complete).
>
> And here is my question: Is there any way to prevent MOVING of
> directories? I have tried almost everyghing using NTFS access rights, but
I
> always reach to a point of no return: for example, if I set rights to not
> being able to delete files or directories, users cannot either delete nor
> rename directories they try to create themselves using explorer (explorer
> first creates a folder called 'New Folder' and then tries to rename it to
> whichever name you wanted later).
>
> I think NTFS handles MOVING of files as is a proccess of renaming the
> file, but I have not seen any right dealing with renaming either.
>
> Any light on this subject would be greatly appreciated. Thanks for
> everything in advance.
>
>