J
James Fabulous
I've done a good deal of reading today that has bolstered my understanding
of EFS and its uses and limitations. However a couple of questions are
still apparent when I use this knowledge.
Scenario:
FolderA is shared as FolderA with Domain Admins having Full Control both
Sharing and NTFS security
FolderB is under FolderA and has the same permissions for NTFS
FolderB (and susequent contents an excel spreadsheet) were encrypted by
UserA (a domain admin) on the server (Win2K3) using the GUI.
UserA's works from a Win2K SP4 workstation and visits FolderA via the
network share and browses into FolderB. Double clicks the spreadsheet to
open the file which executes Excel and produces the error "Cannot access
read-only file FileA.xls" promptly followed by "Cannot access FileA".
Is there a reason that an EFS encrypted file would not work under this
scenario? How do I resolve this?
In addition to the issue above even when using the details tab (apparent on
the Win2K3 server but not available on Win2K clients like UserA's
workstation) UserA adds certificates of another domain admin UserB. UserB
has an XPSP2 workstation but gets the same error when attempting to open the
file in the same fashion as stated above.
According to what I've read there should be no issue with that either - Any
ideas?
*SideNote - an EFS RA has been established and certificates exported to
offsite locations. When viewing the EFS properties for the file via the
Win2K3 server and the XP client the information shown is correct.
of EFS and its uses and limitations. However a couple of questions are
still apparent when I use this knowledge.
Scenario:
FolderA is shared as FolderA with Domain Admins having Full Control both
Sharing and NTFS security
FolderB is under FolderA and has the same permissions for NTFS
FolderB (and susequent contents an excel spreadsheet) were encrypted by
UserA (a domain admin) on the server (Win2K3) using the GUI.
UserA's works from a Win2K SP4 workstation and visits FolderA via the
network share and browses into FolderB. Double clicks the spreadsheet to
open the file which executes Excel and produces the error "Cannot access
read-only file FileA.xls" promptly followed by "Cannot access FileA".
Is there a reason that an EFS encrypted file would not work under this
scenario? How do I resolve this?
In addition to the issue above even when using the details tab (apparent on
the Win2K3 server but not available on Win2K clients like UserA's
workstation) UserA adds certificates of another domain admin UserB. UserB
has an XPSP2 workstation but gets the same error when attempting to open the
file in the same fashion as stated above.
According to what I've read there should be no issue with that either - Any
ideas?
*SideNote - an EFS RA has been established and certificates exported to
offsite locations. When viewing the EFS properties for the file via the
Win2K3 server and the XP client the information shown is correct.