cmdown
asked on
Auditing Permissions - Server 2003
I have a problem with one server on a domain of 11 Windows 2003 servers. Since this was migrated from a smaller HP box to the current 'box users have experienced very slow access to files, access denied faults requiring permissions to be reset, folders disappearing, system freezing for > 60sec on attempting to reset permissions. Random users are affected by all these faults.
I've found a question posted back in 2004 ( See Q_21233866 ) with someone having a similar problem and I've also referred to this issue in my open question ( Q_24382549 ) which is about wiping and resetting the folder share permissions and the NTFS security.
Having reviewed various TechNet pages, I am unclear if turning on NTFS auditing will affect existing permissions. Please can someone clarify:
1. the steps required to enable NTFS auditing so that I can track which accounts (if any) are triggering these changes to permissions, deleting folders etc.
2. Which actions should be audited for success / failure
3. Confirm that setting the auditing does not change any of the existing granted user share permissions or NTFS security.
Server is Dell PowerEdge 2950, dual quad core cpu, 16GB ram, 2 x 146GB mirrored SAS for system partitiion, 4 x 1 TB Sata Raid 5 data partition, dual teamed 1GB NICs, Windows Server 2003 SP2
I've found a question posted back in 2004 ( See Q_21233866 ) with someone having a similar problem and I've also referred to this issue in my open question ( Q_24382549 ) which is about wiping and resetting the folder share permissions and the NTFS security.
Having reviewed various TechNet pages, I am unclear if turning on NTFS auditing will affect existing permissions. Please can someone clarify:
1. the steps required to enable NTFS auditing so that I can track which accounts (if any) are triggering these changes to permissions, deleting folders etc.
2. Which actions should be audited for success / failure
3. Confirm that setting the auditing does not change any of the existing granted user share permissions or NTFS security.
Server is Dell PowerEdge 2950, dual quad core cpu, 16GB ram, 2 x 146GB mirrored SAS for system partitiion, 4 x 1 TB Sata Raid 5 data partition, dual teamed 1GB NICs, Windows Server 2003 SP2
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DTAHARLEV
auditing won't change anything.
ASKER
Hi Tony
Thankyou for your reply. This server is not a DC and I can't find the local policy snapin. How & where can I set a policy that applies only to this server and not all the others in the domain ?
Thankyou for your reply. This server is not a DC and I can't find the local policy snapin. How & where can I set a policy that applies only to this server and not all the others in the domain ?
ASKER
found it !
You can get the local policy snap-in by typing gpedit.msc in the Run box.
Either that, or create a group policy, apply it to the OU holding the server, but then use security filtering (Scope tab in the GPMC) to only allow that one server to apply the policy (see the screenshot below of the GPMC). Remove 'Authenticated Users' and add just the computer account for the server (you'll have to tick 'Computer' in Object Types when selecting the computer account.
Probably simpler to apply locally if you can though! Bear in mind that local policy will be overruled by any conflicting group policies applied to the server.
Snap2.jpg
Either that, or create a group policy, apply it to the OU holding the server, but then use security filtering (Scope tab in the GPMC) to only allow that one server to apply the policy (see the screenshot below of the GPMC). Remove 'Authenticated Users' and add just the computer account for the server (you'll have to tick 'Computer' in Object Types when selecting the computer account.
Probably simpler to apply locally if you can though! Bear in mind that local policy will be overruled by any conflicting group policies applied to the server.
Snap2.jpg
ASKER
Thanks Tony. Have saved and cleared existing log. Expanded max log size to 128Mb (!) (1,400 users !!) and set logging for change permissions as well as delete files and folders for the drive.
Wise move! It always pay to be careful when applying auditing to ensure that your log files don't get jammed with events.
Glad you got it sorted (or at least on the way to getting it sorted!)
Glad you got it sorted (or at least on the way to getting it sorted!)