How to: Restore a Deleted Active Directory Object
How to: Restore a Deleted Active Directory Object
Obtained from: http://technet.microsoft.com/en-us/library/dd379509(v=ws.10).aspx
Step 1: Enable Active Directory Recycle Bin
Updated: February 28, 2011
Applies To: Windows Server 2008 R2
This step provides instructions for the following tasks:
You can enable Active Directory Recycle Bin only if the forest functional level of your environment is set to Windows Server 2008 R2. You can raise the forest functional level by using the following methods:
- Set-ADForestMode Active Directory module cmdlet
Note The Active Directory module for Windows PowerShell in Windows Server 2008 R2 is a Windows PowerShell™ module (named Active Directory) that consolidates a group of cmdlets. You can use these cmdlets to manage your Active Directory domains, Active Directory Lightweight Directory Services (AD LDS) configuration sets, and Active Directory Database Mounting Tool instances in a single, self-contained package. For more information, see What’s New in AD DS: Active Directory Module for Windows PowerShell (http://go.microsoft.com/fwlink/?LinkID=140056). - Ldp.exe
Membership in Enterprise Admins, or equivalent, is the minimum required to complete these procedures. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
- Click Start, click Administrative Tools, right-click Active Directory Module for Windows PowerShell, and then click Run as administrator.
- At the
Active Directory module for Windows PowerShell
command prompt, type the following command, and then press ENTER:Set-ADForestMode [-Identity] <ADForest> [-ForestMode] <ADForestMode>
To set the forest functional level to Windows Server 2008 R2, type
Windows2008R2Forest
for<ADForestMode>
.For example, to set the forest functional level of contoso.com to Windows Server 2008 R2, type the following command, and then press ENTER:
Set-ADForestMode –Identity contoso.com -ForestMode Windows2008R2Forest
For more information about the Set-ADForestMode cmdlet, at the Active Directory module for Windows PowerShell
command prompt, type Get-Help Set-ADForestMode
, and then press ENTER.
Note |
---|
You can use the Set-ADObject cmdlet to raise the functional level of an AD LDS configuration set. For example, to raise the functional level of an AD LDS configuration set on a local AD LDS server, where the distinguished name of the AD LDS configuration directory partition is CN=Configuration,CN={32E430E4-42D3-4663-BCA7-5F5DFDC898}, use the following cmdlet:
|
- To open Ldp.exe, click Start, click Run, and then type ldp.exe.
- To connect and bind to the server that hosts the forest root domain of your AD DS environment, under Connection, click Connect, and then click Bind.
- Click View, and then click Tree. In BaseDN, select the configuration directory partition, and then click OK.
- In the console tree, double-click the distinguished name (also known as DN) of the configuration directory partition, and then navigate to the CN=Partitions container.
- Right-click the CN=Partitions container’s distinguished name, and then click Modify.
- In the Modify dialog box, in Edit Entry Attribute, type msDS-Behavior-Version.
- In the Modify dialog box, in Values, type 4 (the value of the Windows Server 2008 R2 forest functional level).
- In the Modify dialog box, under Operation click Replace, click Enter, and then click Run.
After the forest functional level of your environment is set to Windows Server 2008 R2, you can enable Active Directory Recycle Bin by using the following methods:
- Enable-ADOptionalFeature Active Directory module cmdlet (This is the recommended method.)
- Ldp.exe
Note |
---|
In this release of Windows Server 2008 R2, the process of enabling Active Directory Recycle Bin is irreversible. After you enable Active Directory Recycle Bin in your environment, it cannot be disabled. |
Membership in Enterprise Admins, or equivalent, is the minimum required to complete these procedures. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
- Click Start, click Administrative Tools, right-click Active Directory Module for Windows PowerShell, and then click Run as administrator.
Warning If you do not use the Active Directory Module for Windows PowerShell to run the following commands, you will see errors. If you would prefer to run the following commands from Windows PowerShell directly, then first import the Active Directory cmdlet by running the following command import-module activedirectory
- At the
Active Directory module for Windows PowerShell
command prompt, type the following command, and then press ENTER:Enable-ADOptionalFeature -Identity <ADOptionalFeature> -Scope <ADOptionalFeatureScope> -Target <ADEntity>
Note The distinguished name (also known as DN) of Active Directory Recycle Bin is CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=<mydomain>,DC=<com>, where <mydomain> and <com> represent the appropriate forest root domain name of your Active Directory Domain Services (AD DS) environment. For example, to enable Active Directory Recycle Bin for contoso.com, type the following command, and then press ENTER:
Enable-ADOptionalFeature –Identity ‘CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=contoso,DC=com’ –Scope ForestOrConfigurationSet –Target ‘contoso.com’
Note |
---|
You can also use the Enable-ADOptionalFeature cmdlet to enable Active Directory Recycle Bin in an AD LDS environment. For example, to enable Active Directory Recycle Bin on a local AD LDS server, where the distinguished name of the AD LDS configuration directory partition is CN=Configuration,CN={372A5A3F-6ABE-4AFD-82DE-4A84D2A10E81}, use the following cmdlet:
|
For more information about the Enable-ADOptionalFeature cmdlet, at the Active Directory module for Windows PowerShell
command prompt, type Get-Help Enable-ADOptionalFeature
, and then press ENTER.
- To open Ldp.exe, click Start, click Run, and then type ldp.exe.
- To connect and bind to the server that hosts the forest root domain of your AD DS environment, under Connection, click Connect, and then click Bind.
- Click View, click Tree, in BaseDN, select the configuration directory partition, and then click OK.
- In the console tree, double-click the distinguished name of the configuration directory partition, and then navigate to the CN=Partitions container.
- Right-click the CN=Partitions container’s distinguished name, and then click Modify.
- In the Modify dialog box, make sure that the DN box is empty.
- In the Modify dialog box, in Edit Entry Attribute, type enableOptionalFeature.
- In the Modify dialog box, in Values, type CN=Partitions,CN=Configuration,DC=mydomain,DC=com:766ddcd8-acd0-445e-f3b9-a7f9b6744f2a. Replace mydomain and com with the appropriate forest root domain name of your AD DS environment.
Note 766ddcd8-acd0-445e-f3b9-a7f9b6744f2a is the Active Directory Recycle Bin globally unique identifier (GUID). To verify the Active Directory Recycle Bin GUID, navigate to the CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration, DC=mydomain,DC=com container (replace mydomain and comwith the appropriate forest root domain name of your AD DS environment), and in the details pane, locate the value of the msDS-OptionalFeatureGUID attribute.
- In the Modify dialog box, under Operation click Add, click Enter, and then click Run.
- To verify that Active Directory Recycle Bin is enabled, navigate to the CN=Partitions container. In the details pane, locate the msDS-EnabledFeature attribute, and confirm that its value is set to CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration, DC=mydomain,DC=com, where mydomain and com represent the appropriate forest root domain name of your AD DS environment.
Step 2: Restore a Deleted Active Directory Object
Updated: October 27, 2010
Applies To: Windows Server 2008 R2
This step provides instructions for completing the following tasks with Active Directory Recycle Bin:
- Displaying the Deleted Objects container
- Restoring a deleted Active Directory object using Ldp.exe
- Restoring a deleted Active Directory object using the Get-ADObject and Restore-ADObject cmdlets
- Restoring multiple, deleted Active Directory objects
When Active Directory objects are deleted, they are placed in the Deleted Objects container. By default, the CN=Deleted Objects container is not displayed. You can use the Ldp.exe administration tool in Active Directory Domain Services (AD DS) to display the Deleted Objects container.
Membership in Domain Admins, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
- To open Ldp.exe, click Start, click Run, and then type ldp.exe.
- On the Options menu, click Controls.
- In the Controls dialog box, expand the Load Predefined pull-down menu, click Return deleted objects, and then click OK.
- To verify that the Deleted Objects container is displayed:
- To connect and bind to the server that hosts the forest root domain of your AD DS environment, under Connections, click Connect, and then Bind.
- Click View, click Tree, and in BaseDN, type DC=<mydomain>,DC=<com>, where <mydomain> and <com> represent the appropriate forest root domain name of your AD DS environment.
- In the console tree, double-click the root distinguished name (also known as DN) and locate the CN=Deleted Objects, DC=<mydomain>,DC=<com> container, where <mydomain> and <com> represent the appropriate forest root domain name of your AD DS environment.
You can use Ldp.exe to restore a single, deleted Active Directory object.
Important |
---|
You have to run Ldp.exe from an elevated command prompt to restore a deleted object. |
Membership in Domain Admins, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
- Open Ldp.exe from an elevated command prompt. Open a command prompt (Cmd.exe) as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-clickCommand Prompt, and then click Run as administrator. If the User Account Control dialog box appears, enter the appropriate credentials (if requested), confirm that the action it displays is what you want, and then click Continue.
- To connect and bind to the server that hosts the forest root domain of your AD DS environment, under Connections, click Connect, and then click Bind.
- On the Options menu, click Controls.
- In the Controls dialog box, expand the Load Predefined drop-down list, click Return Deleted Objects, and then click OK.
- In the console tree, navigate to the CN=Deleted Objects container.
- Locate and right-click the deleted Active Directory object that you want to restore, and then click Modify.
- In the Modify dialog box:
- In Edit Entry Attribute, type isDeleted.
- Leave the Values box empty.
- Under Operation, click Delete, and then click Enter.
- In Edit Entry Attribute, type distinguishedName.
- In Values, type the original distinguished name (also known as DN) of this Active Directory object.
- Under Operation, click Replace.
- Make sure that the Extended check box is selected, click Enter, and then click Run.
Note |
---|
When you delete or recover an Active Directory object with link-valued attributes, AD DS must process the object’s link value table to maintain referential integrity on the linked attribute’s values. Because deleting or recovering an Active Directory object results in modifications to the object’s link value table, if you attempt to delete or recover an object during its ongoing link-value-table processing time, the operation will be blocked. For example, if you use the Active Directory Recycle Bin to recover a deleted object with a large number of link-valued attributes (for example, a group object with 10 million users) immediately after it was deleted (or anytime throughout the duration of its link-value-table processing), the object recovery will be blocked. (If you are using Ldp.exe to perform the recovery, you might see the following error message: “Error 0x2093 The operation cannot continue because the object is in the process of being removed.”) |
You can also restore a deleted Active Directory object by using the Get-ADObject and Restore-ADObject Active Directory module for Windows PowerShell cmdlets. The recommended approach is to use the Get-ADObject cmdlet to retrieve the deleted object and then pass that object through the pipeline to the Restore-ADObject cmdlet.
- Click Start, click Administrative Tools, right-click Active Directory Module for Windows PowerShell, and then click Run as administrator.
- At the
Active Directory module for Windows PowerShell
command prompt, type the following command, and then press ENTER:Get-ADObject -Filter {String} -IncludeDeletedObjects | Restore-ADObject
For example, if you want to restore an accidentally deleted user object with the display name Mary, type the following command, and then press ENTER:
Get-ADObject -Filter {displayName -eq "Mary"} -IncludeDeletedObjects | Restore-ADObject
For more information about the Get-ADObject and Restore-ADObject cmdlets, at the Active Directory module for Windows PowerShell
command prompt, type Get-Help Get-ADObject or Get-Help Restore-ADObject, and then press ENTER.
Consider the following scenario: An administrator at Contoso.com accidentally deletes a nested organizational unit (OU) called Finance_Department, which contains user accounts for employees in the Finance department. The administrator deletes another OU called Admins, which contains user accounts for administrative assistants that work for the Finance department. Brian and Mary are user accounts in the Finance_Department OU. Tom is a user account in the Admins OU. The following illustration shows the Finance_Department OU.
When the Finance_Department OU is deleted, all its objects (a total of five objects) are moved to the Deleted Objects container, with their distinguished names mangled. The Deleted Objects container displays all logically deleted objects in a flat hierarchy as its direct children. The recommended approach to restoring a nested OU to its original state is to use the Get-ADObject Active Directory module cmdlet to retrieve the deleted objects one hierarchy level at a time and then to pass those objects through the pipeline to theRestore-ADObject cmdlet. If the administrator is not familiar with the original hierarchy of the Finance_Department OU, the administrator must first use the Get-ADOBject cmdlet to perform several investigation steps:
- For example, the administrator decides to search for the user account Mary with the Get-ADOBject cmdlet, using the msDS-lastKnownRDN attribute in the ldapFilter parameter and constructing the command so that the lastKnownParent attribute of Mary is returned, as follows:
Get-ADObject -SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -ldapFilter:"(msDs-lastKnownRDN=Mary)" –IncludeDeletedObjects –Properties lastKnownParent
In the output that the Get-ADObject cmdlet returns, the administrator notices that the value for lastKnownParent of Mary is Finance_Department. The administrator also notices that the distinguished name of the Finance_Department OU is mangled, which indicates that the Finance_Department OU object itself is deleted. (An example of a mangled distinguished name is OU=Finance_DepartmentADEL:e954edda-db8c-41be-bbbd-599bef5a5f2a,CN=Deleted Objects,DC=contoso,DC=com.)
- The administrator then decides to search for all the objects in the Deleted Objects container whose lastKnownParent value is Finance_Department, using the following command:
Get-ADObject –SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -Filter {lastKnownParent -eq 'OU=Finance_DepartmentADEL:e954edda-db8c-41be-bbbd-599bef5a5f2a,CN=Deleted Objects,DC=contoso,DC=com'} -IncludeDeletedObjects -Properties lastKnownParent | ft
Note Make sure that you escape the slash () in the mangled distinguished name that is used in the Get-ADObject cmdlet with another slash. In the output that the Get-ADObject cmdlet returns, the administrator notices that Admins is an OU itself.
- The administer further searches for all the deleted objects with a lastKnownParent attribute equal to Admins, using the following command:
Get-ADObject –SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -Filter {lastKnownParent -eq 'OU=AdminsADEL:6b405c87-027c-4135-95af-36c31002be5a,CN=Deleted Objects,DC=contoso,DC=com'} -IncludeDeletedObjects -Properties lastKnownParent | ft
Note Make sure that you escape the slash () in the mangled distinguished name that is used in the Get-ADObject cmdlet with another slash. In the output that the Get-ADObject cmdlet returns, the administrator finds the user account Tom.
- In Windows Server 2008 R2, deleted nested objects must be restored from the highest level of their hierarchy to a live parent. Therefore, the Finance_Department OU object must be restored first. Because all previous investigation steps were performed using the lastKnownParent attribute, which points to the direct parent of the object and does not indicate whether the next parent object is also deleted, as a check the administrator can verify that the value of lastKnownParent for Finance_Department is indeed a live OU by running the following command:
Get-ADObject -SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -ldapFilter:"(msDs-lastKnownRDN=Finance_Department)" –IncludeDeletedObjects –Properties lastKnownParent
This concludes the investigation and the administrator is ready to restore the Finance_Department OU to its original hierarchy and state.
Important |
---|
It is critical to begin restoring objects from the highest level of the hierarchy because deleted objects must be restored to a live parent. |
To restore the Finance_Department OU, the administrator can perform the following procedure.
- Click Start, click Administrative Tools, right-click Active Directory Module for Windows PowerShell, and then click Run as administrator.
- Restore the Finance_Department OU by running the following command at the Active Directory Module for Windows PowerShell prompt:
Get-ADObject -ldapFilter:"(msDS-LastKnownRDN=Finance_Department)" –IncludeDeletedObjects | Restore-ADObject
- Restore the user accounts Brian and Mary and the Admins OU (the direct children of the Finance_Department OU whose distinguished name was restored to OU=Finance_Department,DC=contoso,DC=com in the previous step) by running the following command at the Active Directory Module for Windows PowerShell prompt:
Get-ADObject -SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -Filter {lastKnownParent -eq "OU=Finance_Department,DC=contoso,DC=com"} -IncludeDeletedObjects | Restore-ADObject
- Restore the user account Tom (the direct child of the Admins OU whose distinguished name was restored to OU=Admins,OU=Finance_Department,DC=contoso,DC=com in the previous step) by running the following command at the Active Directory Module for Windows PowerShell prompt:
Get-ADObject -SearchBase "CN=Deleted Objects,DC=contoso,DC=com" -Filter {lastKnownParent -eq "OU=Admins,OU=Finance_Department,DC=contoso,DC=com"} -IncludeDeletedObjects | Restore-ADObject
For more information about the Get-ADObject and Restore-ADObject cmdlets, at the Active Directory Module for Windows PowerShell command prompt, type Get-Help Get-ADObject or Get-Help Restore-ADObject.
For a sample Windows PowerShell script that you can use to restore a deleted tree of Active Directory objects, see Appendix B: Restore Multiple, Deleted Active Directory Objects (Sample Script).
Love
Can we use Let's Encrypt, the free and open certificate authority?
Hola! gracias por la info, me sirvió el comando sacandole el nombre del server. En mi caso, fue una migración…
Yes 3rd option helped me too. I removed the WC key Values from config file then started working.
I know this is from 2014. But really, thank you!