Skip to main content

Recover an Object from the Active Directory Recycle Bin if its Parent OU has Also Been Deleted

By

Here is a good scenario.  What if you want to recover an object from the AD Recycle Bin, but its parent OU has been deleted also?  Here is a blog article that I wrote a few years ago to help simplify all the PowerShell code that you would have to use.  In short, you would have to discover the parent object and restore it before you restore the object that you want.

In the image below, you can see that we are looking at the Active Directory Administrative Center. This domain has the AD Recycle Bin turned on and we have 4 objects in the Deleted Objects area.  OU1 was the parent with OU2 and its child.  OU2 had OU3 as its child.  John Doe’s user object was stored in OU3.

We will start off by right clicking John Doe and selecting Restore. The result is an error.

image

This is because the parent Object of the John Doe object do not exists in Active Directory.  They have also been deleted.  We can find the parent of john do using PowerShell

image

Well isn't this a mess?  If you look carefully at the LastKnownParent property, you can see the object that needs to be restored first, OU3.

In the AD Administrative Center, you simply need to right click the object that gave you the warning and click Locate Parent.

image

The Parent object will get the focus.

image

We could continue to do this until we reach the parent.  Once you attempt to locate the parent of OU1, the Focus on the left pane switches to the Domain, which is the parent of OU1.  Now you can restore the objects in the following order; OU1, OU2, OU3, John Doe.  Not very efficient and what if I wanted to restore just the one object and not 4?  Right click on John Doe again and notice the option to Restore To.

Now I can choose where to restore this object to.  In this case I selected Users and clicked OK.

image

Your object is now restored.

In the case of multiple objects that need to be restored, just select them and click Restore or Restore to.

image

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more