I have two windows 7 x64 Ent non-SP1 builds. They were built with different ISOs. The ISOs are different sizes so there’s at that level something different between the two. But the difference I’ve found is how they move files around within the same volume. On build A when the contents of c:\A are moved to to c:\1 the newly moved contents of c:\1 have the inherited permission from c:\A. On build B when the contents of c:\B are moved to c:\2 the newly moved contents of c:\2 have the inherited permissions of c:\2.
First off, I’ve googled around on the Build A scenario and have found others having this result, as well as Microsoft addressing it as normal behavior (see http://support.microsoft.com/kb/310316). That said, why does my Build B act different?
The problem is that I’ve written documentation for our support groups on how to manage file shares and they are getting different results with regards to permissions depending on what desktop they’re using. A workaround to this is to edit the documentation and insist that files always be copied within the same volume then delete the source, but I’d like to know what exactly is going on.
If you’re wondering why I have and are using two different ISOs, it’s because we’re a large org with different support groups.
I put this in the server forum because despite my example above this issue is happening when files are moved within the same mapped drive (which is a windows server).
Thanks!