Search Results:
×An offboarding script hits the wrong filter. A clean-up removes computers that were still in use. Someone deletes a group that three applications depend on. In Active Directory Users and Computers, the delete is instant and the confirmation is a single dialog.
Getting it back by hand takes knowledge you may not have to hand. You need to know where the object used to live, find it in the Deleted Objects container and undelete it with PowerShell. If the AD Recycle Bin was never enabled, a deleted object is a tombstone that keeps only a few attributes, so the rest has to be rebuilt.
miniOrange Deleted Object Recovery lists AD objects that were deleted and captured in backup snapshots, shows where each object used to live, restores it by whichever path is available, and tells you which path it used.
The same flow for a single user or a clean-up gone wrong.
Open Deleted Objects. Search for the user or account by name or distinguished name, filter by object type and sort by deletion time.
Select the object and click Restore. The console checks whether the AD Recycle Bin is enabled for the domain.
With the Recycle Bin, the object is undeleted in place and keeps its GUID and SID. Without it, the object is recreated at its original location from its last known snapshot state.
The result names the method used and the object's location. Review the object, and restore related groups from a backup if you need their members back.
Built for the moment someone says "I think I deleted the wrong thing."
Users, groups, organizational units, computers and contacts appear in one list, each tagged with its type.
Search deleted users, groups, OUs, computers and contacts by name or distinguished name, filter by object type and sort by deletion time.
Each row shows the distinguished name the object had, so you know what you are restoring before you click.
When the AD Recycle Bin is on, the object is undeleted and moved straight back to its original location in a single operation.
The object is recreated at its original location from its last known snapshot state. Users and computers come back disabled for review.
Viewing deleted objects and restoring them are separate permissions, and every restore, success or failure, is written to the audit log.
If the AD Recycle Bin is enabled for the domain and the object is still in the Deleted Objects container, miniOrange undeletes it in place. Nothing is rebuilt, so it is the same object it was before.
If the Recycle Bin is off, or the undelete does not go through, miniOrange recreates the object at its original location from its last known snapshot state. It creates the object first, then applies the remaining attributes.
Membership is stored on the group. To add a recreated user back to its groups, restore those groups from the same backup.
An object that has left the Deleted Objects container can still be restored if it was in a backup. Open the snapshot, pick the object and restore it. The object is recreated at its original distinguished name from the attributes stored in the backup.
Restores, including failed ones, are written to the audit log with the admin, the object GUID and the domain. Viewing the Deleted Objects list needs backup view access. Restoring needs restore access.
Three ways deleted objects usually happen, and how recovery goes.
A helpdesk admin deleted a current employee instead of the leaver with the same name.
A stale-computer clean-up removed machines that had been offline for the holidays.
A security group used by three applications was deleted during a tidy-up.
The console picks the first path that applies and tells you which one it used.
Situation
What happens
What you get
The object is undeleted in place and moved back to its original location.
The same GUID and SID, with the attributes the Recycle Bin preserved.
The object is recreated at its original location from its last known snapshot state.
A new object with a new GUID and SID. Users and computers start disabled.
Restore it from the snapshot. It is recreated at its original distinguished name.
The attributes stored in that backup. Users and computers start disabled.
The OU and the objects inside it are separate objects.
Restore the OU first, then the users, groups and computers that were in it.
Open Deleted Objects and click Restore. As long as the deleted user account was captured in a backup, miniOrange recreates it at its original location from its last known snapshot state. The recreated user is a new object with a new SID and starts disabled. You can also restore it from any snapshot you pick.
The Recycle Bin path undeletes the original object, so its GUID and SID stay the same. Recreating builds a new object with the same name and location, but a new GUID and SID.
While the Recycle Bin is on, AD preserves a deleted object's attributes, including its group memberships, and the undelete brings them back. Membership is stored on the group, so if a user was recreated instead, restore its groups from a backup snapshot to add it back.
Users, groups, organizational units, computers and contacts.
The Recycle Bin path works while AD keeps the object in the Deleted Objects container, a period set by your forest that is 180 days by default. The snapshot path works for as long as the object is in a backup you retain.
Viewing the list and restoring are separate permissions, so helpdesk can browse deleted objects without being able to restore them. Every restore, including failed ones, is written to the audit log.