As part of quota management, sometimes it's useful to change the ownership of a file, or all files within a certain directory, to a different user so that those files are "owned" by the appropriate person that is responsible for the files/directories. Also, sometimes it's appropriate to change the ownership of a file(s) so that they are not counted against a user's quota - particularly if it's a large file shared by multiple people (Access database for example). There's also the instance that you (as an administrator) may copy/restore a file for a user from some location to your network volume, and now you become the owner of the file instead of the user that uses the file. Wouldn't it be nice to easily change the ownership of the file to the user that will use that file?
I'm a big advocate of JRB Utilities. I often say, "If you're managing a network without JRB as part of your toolkit, you're working too hard!". One of the JRB utilities is SETOWNER, which allows you to change the ownership of a file. I wanted to be able to easily assign file ownership by using Windows Explorer's Send To functionality and JRB's SETOWNER utility - which is exactly what my SetOwnerSendTo utility does.
Manually run SetOwnerSendTo (no parameters) to create a "SendTo Extension" off your Windows Explorer context menu:
You can now browse to a folder, and multi-select a file(s)/directory(ies), right-click, Send To..., Set Owner:
You'll be prompted for a network username to be the owner (your login is filled in by default):
Once you select OK, you'll be prompted whether to process subdirectories or not. After answering that prompt, the selected files/directories will be set to the owner name you specified.
If you do not set an owner - leaving the entry blank - you'll be prompted with this dialog box:
If you select Yes, the file ownership will be associated with user object named "UNOWNED" (which is another Cool Tip I'll explain in another article). Otherwise, by selecting No, the file will not have an owner. You might do this for a file that you don't know who the "right" owner is.
Perhaps the next person to ACCESS the file is a candidate to be the owner of the file at which time, you can make that person the owner of the file(s). (you must have sufficient rights to your tree to create a user object for this to work)
For full functionality of SetOwnerSendTo, you'll need to have the following JRB utilities available in your search path:
The \JRB32 versions:
The .\GUI1\SETOWNER.EXE version needs to exist in your path as: