You are thinking about this way too complicated. The account called "Administrator" should be for this purpose. It does have all rights it needs to do anything to anything. This makes it a bad account to use for assigning to staff working on the network. If you are the be-all end-all of I.T. for your company, then it's okay for you to use the Administrator account. If you have a crew, don't have all of them use the account. You can add them to the "Domain Admins" group, which gives them rights to move files around, and make most changes they would need, except taking ownership of objects they don't automatically have access to. This also creates a much more reliable log of who has done what on the systems. You should even use a personal account for yourself and be a "Domain Admin". This also protects your network from yourself in certain senarios, for example, If you are testing a new program for network management and you accidentally have it reset the ownership on some objects, there is a possibility of locking everyone out of the object permanently. If you are not the "Administrator" administrator, you can't really make any changes to the permissions that can't be reset by the real administrator account. Email me for some more network admin questions.
craig@jacksoncomputing.us