Some careful digging reveals that taking ownership sometimes destroys existing permissions and sometimes doesn't. It all seems to depend on whether you try and do it recursively. Note that Windows does warn you when it is going to replace the existing permissions, but (in the GUI at least) it's very easy to just OK the message without reading or understanding it fully.
To see it, you'll need a directory (c:\SomeFolder in this example) that is owned by a different user account and to which you and the administrators group have zero access.
Command Line
Using the command line "takeown" tool:
TAKEOWN /A /R /F c:\SomeFolder
you should see something like
SUCCESS: The file (or folder) "c:\SomeFolder" is now owned by the administrators group.
You do not have permissions to read the contents of the directory "c:\SomeFolder"
Do you want to replace the directory permissions with permissions granting you full control ("Y" for YES, "N" for NO, "C" for CANCEL)?
Note that if you answer yes here, it really does mean replace the permissions. Any existing permissions will get destroyed. If you answer no, you still have no permissions on the folder but are now the owner so can give yourself permissions normally and without destroying any that already exist.
If you don't specify the recursive flag (/R), you don't get the warning and the owner is changed without affecting any other permissions.
GUI
You'll need to use the "security" tab of the properties window to alter anything via the GUI. This gives you two buttons: "continue" and "advanced". Advanced gives you a window with the four tabs: "permissions", "auditing", "owner" and "effective permissions". Continue gives you just the "owner" tab.
If you select a new owner and tick the "apply to sub-folders" box, hitting OK or apply gives you a "Do you want to replace the permissions" message box that, again, really does mean replace permissions. If you don't check the sub-folders box, you don't get the warning and everything behaves as expected.
It is very easy to not read this message box fully, assume it's just another box asking you to confirm something non-destructive and just hit enter to OK it. It's also very easy to assume they couldn't possibly really mean replace because nobody sane would ever want to do that.
Taking ownership does not (or at least, should not) destroy the current permissions on the folder. (I've just tried this out and it worked as expected - the permissions were unchanged.) To be on the safe side, you might prefer to use the command-line tool, takeown, instead of the GUI tools. This tool definitely won't change the permissions. – Harry Johnston – 2011-11-14T02:51:40.560
Well, after taking ownership, I can't see any permisssions except for the account that just took ownership. Other folders seem to behave properly. I suppose it's possible that the folder was created without any permissions for anybody or had them all stripped out but it seems odd though. – Nigel Hawkins – 2011-11-14T15:56:06.740
The process of taking ownership shouldn't have changed the permissions at all, not even by adding your account. Did you use the takeown command-line tool or Explorer's Advanced Security Settings dialog? – Harry Johnston – 2011-11-15T01:57:38.470
Tried it both ways. As I said, other folders seem to behave properly when the owner is changed. I've come to the conclusion that it must have had no permissions for anybody to start with. So it just looked like it had deleted all the old permissions when I took ownership. – Nigel Hawkins – 2011-11-18T12:06:09.177