<div>
You need to remove and re-create the DAG, however, I would suggest that the NLB name is not the best name to use for the File Share Witness.
</div>


You need to remove and re-create the DAG, however, I would suggest that the NLB name is not the best name to use for the File Share Witness.

<div>
Thx, initially i tried to use nlb name and it didnt work. then i used name of a member of nlb and its working fine now. should i use second member of my nlb as an alternate file witness share. Would it be ok? im little nervous about this as im not aware of the repurcussions. 
</div>


Thx, initially i tried to use nlb name and it didnt work. then i used name of a member of nlb and its working fine now. should i use second member of my nlb as an alternate file witness share. Would it be ok? im little nervous about this as im not aware of the repurcussions.

<div>
<div class="content wysiwyg-content">
Hi I have Exch 2010 Environment of 4 servers. 2 are MBX/HT and 2 are CAS. My DAG was working fine before i created CAS array. One member of my CAS array was File Witness server for the DAG. I dont see File witness share folder either. My CAS array is made up of Win 2008 NLB clustering. <br />
<br />
My question is, should i add 2 of my CAS array server as main and alternate file witness share servers on my DAG or shall i remove and reconfigure a new DAG?
</div>
</div>


Hi I have Exch 2010 Environment of 4 servers. 2 are MBX/HT and 2 are CAS. My DAG was working fine before i created CAS array. One member of my CAS array was File Witness server for the DAG. I dont see File witness share folder either. My CAS array is made up of Win 2008 NLB clustering. 

My question is, should i add 2 of my CAS array server as main and alternate file witness share servers on my DAG or shall i remove and reconfigure a new DAG?

DAG stopped working after creating CAS array.

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.