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

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog