Adding Other Boot's Computer Name to list of File Security Locations?

John - the way I see it (the OP's problem) is this ;

I am well aware that he does not want to dismiss the current "private"
status of the XP folders on a dual-boot system.

However, as far as I am aware, making folders "private" does [should] *not*
make those XP folders inaccessible to a user on the Win7 OS who is a member
of the Administrators group!

Members of the Administrators group, on any (previous) NT-based OS, have
access across dual-boot systems, to *any* files and folders on drives
belonging to their opposing OS.

The OP has made sure (partly on my advice) that the folders in question
have been granted Administrators-Group full-access while in the XP OS -
Then, still cannot access those same folders in an Administrator-level user
on the Win7 OS.

Can you explain this anomaly, or do you think this is normal?

==

Cheers, Tim Meddick, Peckham, London. :-)




"John John - MVP" wrote in message
...

Larry Lindstrom wrote:
On 6/8/2010 12:03 PM, Tim Meddick wrote:
Security "Groups" aren't assigned SIDs - only "Users" - that's why I
stressed adding the "Administrators" Group to the user-list and NOT the
(built-in) user named "Administrator"

Please note again the difference :

Administrators = YES
Administrator = NO

Thanks Again Tim:

Still no luck.

You can't have it both ways, Larry, private is private, either the files
are private or they are not. There is no "peeking" at private folders
and there are no varying levels of privacy, it's all or nothing. From
Windows 7 you would need to take ownership of the folder then grant
yourself adequate access rights to the objects within. I can only
suggest that you use standard NTFS permissions to control access to the
files or that you use encryption or a third party solution. Be sure that
you understand the risks of file loss if you decide to use NTFS
encryption!

John