-> Forgive me for jumping in.  I agree you can remove rights from
-> accounts. However, I don't believe you'll be very successful trying
-> to block any account with Supervisor rights to the file server
-> object.  Seems to me, if you have Supervisor rights to the file
-> server object, you automatically gain supervisory rights to every
-> file that the file server contains. And these rights cannot be
-> blocked.
The file server object has the same abilities/limitations as other NDS 
objects, including the ability to block the Supervisor object right by new 
trustee assignment or by setting an IRF on the server. Once you cross into 
the file system, yes, Supervisor cannot be blocked, but BEFORE you cross over 
you can block it.
This ability was created to permit someone to be made a container 
administrator, without requiring that person to be the server administrator. 
Before you block the supervisor object rights to the server, you need to make 
a trustee assignment for someone at that server, granting supervisor object 
rights, so the server can be administered. This is also true with containers, 
although the server is not a container.
Alan, CNE, CNI
--- InterEcho 1.19
---------------