If you upgrade a 2003 domain to a 2008 domain, are OUs protected from deletion?

OU deletion protection allows you to prevent the deletion of accidental move of an OU. This is a particular problem with using a laptop with a tiny mouse pad for administration. It is easy to accidently move an OU into another OU. With Group Policy, this can easily create problems. In Windows Server 2008, All OUs are created with the new OU Deletion Protection turned on by default. The question is, are OUs created on a Windows 2003 Domain protected after an upgrade to a Windows 2008 domain?

The answer is no.

I tested using a Windows 2003 domain created in a Hyper-V environment. I creaed an empty OU and another one with both a user account and a group. OU protection was not on by default for both of them after the upgrade. Also the objects inside the did not have deletion protection. To activate Deletion protection:

· Open AD Users and Computers

· Click View and select Advanced Features.

· Right click the OU and click Properties

· In the Object tab check Protect object from accidental deletion.

You will have to also do this for each object inside the OU that you want to protect.

Comments

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.

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