Re: Ownsership and Rights
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 Apr 2007 14:16:15 -0400
Vern <Vern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have Everyone, Full Controll set up for bothe the NTFS and for the
share.
Youch. Well, that sounds excessive for the NTFS stuff. I like Administrators
+ System = Full control - and then whatever user group(s) I wish get Modify.
Also, when I am logged into the server as Administrator, and I check
the properties of a file created in the share I'm having trouble in,
I get
"you do not have permission to view or edit the current permission
settings for {filename}, but you can take ownership or change
auditing settings."
Why as administrator can I not check the rights of a file? Advanced,
Effective Permissions does not work as well.
Take ownership of the folder as the Administrators group (better than
Administrator) and then re-set the NTFS permissions appropriately - then in
the advanced settings, 'push' inheritence down the subfolder tree.
-vern-
"Lanwench [MVP - Exchange]" wrote:
Vern <Vern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks for engaging...
I have a partition thatis set up for all of the shares... and the
shares are set up to reflect the original Novell Server. The share
That I'm working on has share rights of Everyone, Full control...
obviously not a long term solution, but for now I just want it to
work.
Everyone = full control is fine, for the share. A lot of people
leave their share permissions wide open that way. They will be
trumped/superseded by the NTFS permissions.
There are a number of other rights set up on this folder, but
currently Everyone, Full Control is specifically set, and rights are
inheritable in the folder.
For NTFS, or for the share? The latter is what really matters.
-vern-
"Lanwench [MVP - Exchange]" wrote:
Vern <Vern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I've implemented a SBS 2003 in a small Land Surveying company... I
migrated their data via backup over from Novell, and the entire
server seems to work well.
The problem is a rights problem. I have defines a Security Group
that all the drafts people are part of, and sharing files works
fine, except when a person makes a new file. They are the owner
by default, and no one can access the file on the share until I
force ownership to Administrator or to one of the other users.
Once I've forced ownership, the shared file works fine. Even
when I browse to the file on the server to check ownership, I am
forced to take ownership before I can do anything with the file.
Obviously this is not a workable scenario... I can't tell the
users... "OK, here's how it works, make a new file, then call the
Network Admin and have him change the rights on the file, and
voila, it'll be sharable." I'm a tad frustrated.
Why does this happen? Is there a default policy somewhere that
precludes others from seeing the file? I can accept that the
ID10T problem is sitting in my chair, but I simply can't seem to
find resolution.
Ownership shouldn't make a lick of difference here.
Where's the folder? What're the share permissions, and what are the
NTFS permissions explicitly set and/or inherited from the parent?
.
- References:
- Re: Ownsership and Rights
- From: Lanwench [MVP - Exchange]
- Re: Ownsership and Rights
- From: Lanwench [MVP - Exchange]
- Re: Ownsership and Rights
- From: Vern
- Re: Ownsership and Rights
- Prev by Date: Re: External Hard Drives Used For Backup - Be Aware...
- Next by Date: Re: Branch server IP change after reboot
- Previous by thread: Re: Ownsership and Rights
- Next by thread: Re: Fax Modem that Supports Caller ID
- Index(es):
Relevant Pages
|