Active Directory Recycle Bin in Windows Server 2012

  1. Go AD administrative center  right click the domain Enable Recycle Bin


To Enable Recycle bin your Forest and domain fuctional level should be Windows 2008R2

2.Once you enabled recycle bin you cannot disable the feature.


3.Replication needs to happen all the domain controllers


4. You can see one more container as Deleted objects in the AD Administrative center


5.Now delete a user object


6. You can view the deleted object in the deleted objects folder and when it’s deleted, OU path.


If you right click the object you will get the option to restore it back to original location or restore to new location

7. If you click the deleted user properties you can see the deleted view with GUID


8. You can add criteria to search the deleted objects container.


If you deleted entire OU you can see the below view in deleted objects container


If you click the restore from user object you will get the below error since the parent OU is not available.


You can restore to different OU by selecting restore to option


9. In 2008R2 you have to use ldp.exe to view the deleted objects container

Connection->connect your domainàbindàDC=domain,DC=com

Options-> controls-> Loadpredefined-> Return deletedobjects


10.View->Treeà Deleted objects folder and all deleted objects


  • · Locate and right-click the deleted Active Directory object that you want to restore, and then click Modify.
  • · In the Modify dialog box:
  1. In Edit Entry Attribute, type isDeleted.
  2. Leave the Values box empty.
  3. Under Operation, click Delete, and then click Enter.
  4. In Edit Entry Attribute, type distinguishedName.
  5. In Values, type the original distinguished name (also known as DN) of this Active Directory object.
  6. Under Operation, click Replace.
  7. Make sure that the Extended check box is selected, click Enter, and then click Run.



Windows Clustering

Clustering Types:

  •  Server Cluster
  • Network Loadbalancing

Server Cluster: A Server Cluster is a collection of independent servers that together provide a single highly available platform for hosting application.
Network Load Balancing:

  • With load balancing, a single device (a network client) sends traffic to any available node in the load-balanced group of nodes.
  • Load balancing uses heartbeat traffic as well but, in this case, when a node comes offline, the “load” is recalculated among the remaining nodes in the group.

Cluster requirements:

  1. Two Servers with Same configuration
  2. Two network cards in each server
  3. SAN storage
  4. SAN Switch
  5. Windows server 2003 Enterprise or Data center edition OS

Clustering in Windows:

  • Windows NT 4.0 Enterprise Edition supported 2 Node cluster
  • Windows 2000 Data canter Server supported up to 4 Node cluster
  • In Windows 2003 Enterprise & Data center editions supports up to 8 node Clustering.
  • In Windows 2003 Enterprise & Data center editions Supports up to 32 node in Network balancing.
  • In Windows 2008 Enterprise & Data center editions supports up to 16 node Clustering.

Benifits of Clustering:


Quorum Types:

Standard Quorum :
Each member connects to the shared storage via some type of interconnect (e.g. SCSI or Fiber Channel).

Majority Node Set Quorum: A MNS quorum is a single quorum resource from an Server cluster perspective. The data is actually stored by default on the system disk of each member of the cluster.

Failover & Failback:

  1. Failover is the act of another server in the cluster group taking over where the failed server left off.
  2. Failback is the capability of the failed server to come back online and take the load back from the node the original server failed over to

Server Clustering Types:

  • Active/Active
          Two nodes providing services to the network clients. That’s 100 percent of served resources. If one server fails, then the clients will only have one server in which to access and that would cut the percentage to 50 percent
  • Active/Passive
          Active/Passive is defined as a cluster group where one server is handling the entire load and, in case of failure and disaster, a Passive node is standing by waiting for failover.