Always ON Availability Group (AAG) configuration on Cluster(Active/Passive) env servers and standalone servers

SQL Server 2012 or higher versions:  Always on Availability Group (AAG) can configure in 2 scenario's:
1.Cluster (Active/Passive)(Not supports Automatic failover)
2.Standalone Servers (Supports Automatic failover)

1.Cluster (Active/Passive) Env Servers:
 (This does not support automatic failover and it supports manual failover)
Pre-req:
1.Windows Server Faiover Cluster(WSFC) services need to install on both nodes (Windows Admin responsibility)
1.1 Then configure  the quorum ( add the nodes in quorum)
2.Make sure test the validation report for storage,cluster servers .....etc.
    If any issue then contact windows admin
3.IP addresses required for
    Node1 IP address
    Node2 IP address
    Windows Cluster IP
     SQL Server Virtual IP Address
    Listener Name and IP Address (for Always On configure)
    Optional :   MSDTC IP( if you use distributed transactions then it required)
   Note: If you use 3 rd server then submit for Node3 IP address
 4.Use AD group to install the SQL Server Instance(Best practice)
     or can use any Windows Admin group user to install
SQL Installation:
5. High level steps
   5.1 Install SQL Server on Node1
   5.2 Then add on Node2 to install SQL Server
   5.3 Reboot the both nodes
6.Configure Always On
    Create Availability group and add replicas.
    use Always On Listener Name/IP address

2.Standalone Servers: (This supports automatic failover(3rd node also required) and  manual failover(node1/node2 required) )
Pre-req:
1.Install basic Windows Server Failover Cluster(WSFC) services on both nodes (Windows Admin responsibility)
1.1 Then configure  the quorum(add the nodes in quorum)
2.Make sure test the validation report for storage,cluster servers .....etc.
    If any issue then contact windows admin
3.IP addresses required for
    Node1 IP address
    Node2 IP address
    Windows Cluster IP
    Listener Name/IP Address(for Always On configure)
    Optional :   MSDTC IP( if you use distributed transactions then it required)
     Note: If you use 3 rd server then submit for Node3 IP address for automatic failover
 4.Use AD group to install the SQL Server(Best practice)
     or can use any Windows Admin group user to install
SQL Installation:
5. High level steps
   5.1 Node1: Install SQL Server on Node1
   5.2 Node2: Install SQL Server on Node2
   5.3 Node3: This is required for automatic failover purpose. if you  use Node and File share or other options ...on Node3 then SQL Server installation not required.
Node3 is for just automatic failover purpose(voting purpose) only. If it manual failover then node2/node2 required.
Note:"Search in "quorum configuration" options(4 options and select any option to configure the quorum voting)
6. Reboot the all 3 nodes(node1/node2/node3)
7.Configure Always On
    Create Availability group and add replicas.
    use Always On Listener Name/IP address


Issues while create AlwaysON Availability Group:
Note: Before you create a Windows failover cluster, you have to check whether the domain user account that is running the Create Cluster Wizard has the "Create Computer Objects"permission.
Solution: http://support.microsoft.com/kb/2829783)
or
Check  "Steps for configuring the account for the person who installs the cluster" step below link.
http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx