Skip to main content

How to audit changes in AD Objects


Windows Server 2008 offeres the ability to record changes to AD objects. Both what the value of the object was, and what it is now. It also records who did it. Below is the procedure to set it up.
- Open Group Policy Manager
- Expand you forest until you get to the Default Domain Policy.
- Right click the Default Domain Policy and click Edit.
- Expand Computer Configuration --> Windows Settings -->Security Settings --> Local Policies and click Audit Policy.
- Set Audit directory services access to log both success and failures.
- Close Group Policy Manager.
- Open a command prompt.
- Type auditpol /set /subcategory:"directory service changes" /success:enable
You can verify the current settigns by using the following command: auditpol /get /category:"DS Access"
In the lab, the next step was to create and modify user account. What the lab did not do is tell us to enable auditing for the account being used.
- Open Active Directory Users and Computers.
- Click View and click Advanced Features.
- Right click the OU containing the objects that you want to audit and click Properties.
- Click the Security tab.
- Click Advanced.
- Click Auditing tab.
- Now you need to add the user or group that you want to audit directory changes for inside this OU.
To Audit for Account creation (Event 5137) or movement (Event 5139) of an object into this OU, audit for success on: Create User Objects
-To audit for modification (Event 5136) you will want to audit for sucess on: Write All Properties. In practice two events 5136 will appear. The first is the old setting. The second is the new setting.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...