junyap
asked on
Exchange 2013 Witness Server
What is version of domain controller ? Windows 2008 or Windows 2012?
If your domain controller is Windows 2008 then request you to refer below Technet article this will help you to resolve your issue:
http://social.technet.microsoft.com/Forums/exchange/en-US/f690af17-31f6-4abf-a6fa-d46fc655ad68/exchange-2013-dag-creation-issue?forum=exchangesvravailabilityandisasterrecovery
Regards,
Arjun
If your domain controller is Windows 2008 then request you to refer below Technet article this will help you to resolve your issue:
http://social.technet.microsoft.com/Forums/exchange/en-US/f690af17-31f6-4abf-a6fa-d46fc655ad68/exchange-2013-dag-creation-issue?forum=exchangesvravailabilityandisasterrecovery
Regards,
Arjun
ASKER
Hi Mojahid,
Yes, I already performed that. Actually I ave successfully configured my DAG but my witness server is Server 2012. I am trying to switch the witness server to my domain controller which is Server 2008 R2.
Thanks,
Yes, I already performed that. Actually I ave successfully configured my DAG but my witness server is Server 2012. I am trying to switch the witness server to my domain controller which is Server 2008 R2.
Thanks,
ASKER
Hi Arjun,
My server is Windows Server 2008 R2.
Thanks,
My server is Windows Server 2008 R2.
Thanks,
A witness server is a voter that is external to the DAG that participates in quorum by adding a tie-breaking voter to DAGs that have an even number of members.
You do not need a dedicated server for the FSWs(file share Witness) and typically it is recommended to use a hub transport server in the primary data center. This is usually a safe thing to do as the Exchange team also manages the hub transport servers and the Exchange Trusted Subsytem will already be a member of the local administrators group and have the necessary permissions to create the file share.
The requirements for the witness server are as follows:
The witness server can't be a member of the DAG.
The witness server must be in the same Active Directory forest as the DAG.
The witness server must be running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, or Windows Server 2003.
A single server can serve as a witness for multiple DAGs. However, each DAG requires its own witness directory.
Please refer below for more details:
http://technet.microsoft.com/en-us/library/dd298065.aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/521789ef-69cc-47a4-83d3-fb21331f4908/what-is-witness-server-used-for
You do not need a dedicated server for the FSWs(file share Witness) and typically it is recommended to use a hub transport server in the primary data center. This is usually a safe thing to do as the Exchange team also manages the hub transport servers and the Exchange Trusted Subsytem will already be a member of the local administrators group and have the necessary permissions to create the file share.
The requirements for the witness server are as follows:
The witness server can't be a member of the DAG.
The witness server must be in the same Active Directory forest as the DAG.
The witness server must be running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, or Windows Server 2003.
A single server can serve as a witness for multiple DAGs. However, each DAG requires its own witness directory.
Please refer below for more details:
http://technet.microsoft.com/en-us/library/dd298065.aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/521789ef-69cc-47a4-83d3-fb21331f4908/what-is-witness-server-used-for
ASKER
Hi Mojahid,
I have only two Exchange Server on 2013 versions both contains mixed roles. My only problem is that I can used any Server 2012 servers as witness server but when I switch to Server 2008 R2 error occurred.
Thanks,
I have only two Exchange Server on 2013 versions both contains mixed roles. My only problem is that I can used any Server 2012 servers as witness server but when I switch to Server 2008 R2 error occurred.
Thanks,
You have to create new DAG only.
Witness Server must have the Exchange Trusted Subsystem (ETS) group added to the local administrators group. If this is a Domain Controller, it needs to be added to Domain\Administrators. This is why you might want to not pick a domain controller. This gives the ETS administrative rights to the entire domain, not just that server. Granted ETS has crazy rights already, but putting the ETS in the Administrators group for the domain might make your security folks nervous.
Read this articles for more
http://jerridwills.com/2013/02/04/creating-a-two-node-exchange-2013-dag/
Witness Server must have the Exchange Trusted Subsystem (ETS) group added to the local administrators group. If this is a Domain Controller, it needs to be added to Domain\Administrators. This is why you might want to not pick a domain controller. This gives the ETS administrative rights to the entire domain, not just that server. Granted ETS has crazy rights already, but putting the ETS in the Administrators group for the domain might make your security folks nervous.
Read this articles for more
http://jerridwills.com/2013/02/04/creating-a-two-node-exchange-2013-dag/
ASKER
I already added the ETS on administrators, but still error occurred.
Thanks,
Thanks,
"I am trying to switch the witness server to my domain controller which is Server 2008 R2."
That isn't a recommended configuration.
Do you not have a member server that you can use?
Simon.
That isn't a recommended configuration.
Do you not have a member server that you can use?
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Resolve by my self
steps here : http://technet.microsoft.com/en-us/library/dd351172(v=exchg.150).aspx
- after prestaging CNO object should be disabled ? is it disabled ?
- if yes, the first node adding to the DAG should have appropriate permissionso n CNO object,
system account should have full permissionso on CNO object,
- paste the complete permissions of CNO object.
http://exchangeserverpro.com/installing-an-exchange-server-2013-database-availability-group/