Set the default Organisational Unit for New Computers in Windows Server

Once you have your domain and group policies set up, it can become frustrating to constantly have to remember to move a new computer into the correct OU.

Luckily in Windows 2003 and above, you can set a default OU:

<code>redircmp ou=ComputersOU,dc=mydomain,dc=com</code>

Remember to replace the path with your own domain’s OU path. Also, your domain has to be running in at least Windows Server 2003 native mode – otherwise you will receive an error:

Error, unable to modify the wellKnownObjects attribute. Verify that the domain functional level of the domain is at least Windows Server 2003:
Unwilling To Perform
Redirection was NOT successful.

To change this:

  • On the server go to Administrative Tools > Active Directory Domains and Trusts.
  • Right-click on your domain name, and click on Raise Domain Functional Level.
  • Set the domain level to at least 2003

Now you should be ready to go!

Active Directory Recovery Guide

I’ve been having numerous errors in the event log appearing on one of my servers from the ESENT service:

Event Type: Error
Event Source: ESENT
Event Category: Database Corruption
Event ID: 467
Date: 18/05/2007
Time: 09:33:06
User: N/A
Computer: SERVER123
ntfrs (5660) Index GChangeOrderGuid of table OUTLOGTable00002 is corrupted (0).

For more information, see Help and Support Center at

These errors are appearing regularly, and contain various tables with problems.

After scouring and the Microsoft support site – I eventually found a very useful Powerpoint presentation that outlines various methods of recovering poorly or corrupt active directory databases.

Although not a specific answer to the problem, it does provide useful guidelines in the best practices for repairing or reinstalling and domain controller, as well as some useful advice such as carrying out a metadata cleanup.

I’ll be following the guide to try and resolve the database errors on this server, and hopefully it will work out nicely.