Exchange 2013 DAG with VMWare Clustering

Hi team,
I'm looking at a scenario where there are 3 Hosts with a SAN for storage and is
Clustered for failover with so many other server/applications. The requirement is to have a High Available environment with Exchange 2013. Now I want to know the possibility of having 2xCAS (WNLB) and 2xMailbox Servers with DAG.
1) Want to know if this is a supported scenario, where DAG is implemented in a VMWare cluster.
2) The DAG on cluster is to ensure that even if no host failure occurs i have VM level failover. and if Host Level failover occurs I have cluster based failover.
Any guidance is much appreciated.
Thank you.
Cheers!

Hello,
It is not supported configuration that combining VMware HA solution with the Exchange application-aware high availability solution.
Here are some articles for your reference.
http://blogs.technet.com/b/keithmayer/archive/2012/08/28/best-practices-for-virtualizing-microsoft-exchange-2010-msexchange-itpro-hyperv-vmware.aspx#.Uxfd2P7xuM8
http://exchangeserverpro.com/microsoft-vs-vmware-on-exchange-virtualization-and-ha-best-practices/ (
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.)
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Similar Messages

  • Exchange 2013 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

    Hi,
    I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
    load balancer for the exchange servers.
    When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in  his OWA session is no more
    able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
    The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
    2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
    (rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database  last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
    Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
    -> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
    The CAS try to access the mailbox on the other server, but without success.
    Someone have idea how to solve?
    Thanks

    Hi Hinte, sorry for the answer delay.
    I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
    [PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
    Name                                                        ServerName
    HealthMailbox7021deb6ae104dadbf52feedfa7fa68b               exch1
    HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f               exch1
    HealthMailboxb1c32037890b43fbb2af2efe7c36ba00               exch1
    HealthMailbox8d174269b494458daf9ade5099e22845               exch1
    HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a               exch1
    HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65               exch1
    HealthMailboxc6ff1d36ba154c5db5411b44718edcbd               exch1
    HealthMailbox75dc7caa7e8c4a3b812a01b607536d48               exch1
    HealthMailbox16c86e512f454e7890b80c180ce19c00               exch1
    HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927               exch1
    HealthMailbox40fa5a3f2abc4accae6286cd98abc90a               exch1
    HealthMailbox2712b9544bad4e7b8b671be2cda8cfde               exch2
    HealthMailboxe2559124da20499386bf8103dcb21e9b               exch2
    HealthMailbox3264c6078dad45d4a78c56a3afe81df1               exch1
    HealthMailboxacacc51eb8bc4717b295ddf0adccf77e               exch2
    HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1               exch1
    HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb               exch2
    HealthMailbox465d2a69de93430e84b4d699a88cb0c3               exch1
    HealthMailbox97b578e57cd44204820fffa416b25633               exch2
    HealthMailboxb411059771db4647bb775c665ec29440               exch1
    HealthMailboxf981dde6f4134f839bf41eb0000434e4               exch2
    HealthMailboxc33801c7c3b1474f8aa6065249bb4fca               exch1
    HealthMailbox2282128ed8d14937998212edd15adf20               exch2
    HealthMailboxe3d12b756cf545239b38be4607904ae1               exch2
    [PS] C:\Windows\system32> 
    Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
    Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
    Regards

  • Exchange 2013 CU6 with DAG - ECP Delete does not go to soft-delete state, retention policy ignored

    I am not sure if this is a BUG or this is as intended.  Typically if a mailbox is 'deleted' from the EAC or ECP console the user account is disabled and the mailbox is marked for removal (soft-delete) until the retention policy expires the item (default
    30 days). However we deleted a mailbox and the mailbox was purged immediately as well as the user was moved to the hidden recycle bin in Active Directory.
    We replicated this issue twice in a DAG environment, we do not have this issue in a non-DAG environment.
    Question:  Other than restoring from the backup, is there a way to recover the mailbox?
    Thank You,
    -Jake
    Jacob Evans Jake of All Trades

    Hi,
    I tested in my lab, Exchange 2013 CU1 with DAG deployed, if I deleted a mailbox from EAC, then it would be a disconnected mailbox and the associated Active Directory user account was also deleted. I could find it under the Disconnected Mailbox.
    Was the mailbox logged ever?
    If you delete a mailbox that you never log in, it won't show as disconnected mailbox.
    And for the question :"Question:  Other than restoring from the backup, is there a way to recover the mailbox?", I'm afraid you have to recover from backup.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles

    Dears,
    I try to planning and installation two hosts ( Data center 2012 servers) then install Hyper-V role on both this server, then create VM on each Data center server to be install Exchange 2013 on them.
    After that I want to configure DAG between Exchanges servers, so what are the prerequisite to do that ?
    Note: I use external IBM storage that will be located all VMs and DAG
    Many thanks 

    Hi Moon,
    In addition to Gulab's suggestion, I would like to clarify the following things:
    1. Yes, we can use Standard or Datacenter version of the Windows Server 2012 operating system to configure Exchange 2013 DAG.
    2. Each member of the DAG should be running the same operating system.
    3. The DAG with an even number of members should have a witness server. A witness server is a server outside a DAG that's used to achieve and maintain quorum when the DAG has an even number of members.
    What's more, here are some helpful articles for your reference.
    Planning for High Availability and Site Resilience
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#HR
    High Availability and Site Resilience
    http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • How to configure Exchange 2013 OWA with Single Sign On

    Hi All ,
    How to configure Exchange 2013 OWA with Single Sign On ?
    Thanks .

    Hi,
    From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
    Exchange 2013 OWA Single Sign on with Exchange 2010
    https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
    If that is not your case, please feel free to tell me.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Moving witness server to CAS server two Exchange 2013 servers with a DAG

    Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too.  In addition there is relays, email and service accts that need to be moved to Exchange
    2013.  
    Presently  there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2...  We wish to add another node to the DAG, and move the witness to another server.
    Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
    Can this server also act as the Witness?
    What would be the best practices for this senario. All of these machines are VM's.

    Inherited a situation where there is one Exchange 2007 Build 83.6 server running on Win2008R2, acting as witness, and hub transport and yes is a file server too.  In addition there is relays, email and service accts that need to be moved to Exchange
    2013.  
    Presently  there are two Exchange 2013 cu3 servers that are part of a DAG that also run on Win 2008r2...  We wish to add another node to the DAG, and move the witness to another server.
    Do I need to also add a CAS Exchange 2013 server to replace the Ex 2007 server?
    Can this server also act as the Witness?
    What would be the best practices for this senario. All of these machines are VM's.
    With an odd number of nodes, the File Share Witness will not be used, but you can still define it.
    Any server ( any including any non-Exchange server) can serve as the FSW as long as its not a mailbox server n the DAG and it has the Exchange Trusted SubSystem group in the local admin group on that server.
    Since you are using VMs, ensure the FSW isn't on the same host as a MBX DAG member.
    Not sure what you mean by adding a CAS Exchange 2013 server. Do you mean you have not installed the CAS role yet for 2013? If so, then absolutetly you need one.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • How do you delete specific message from users in Exchange 2013 DAG database?

    Our network has been inundated with spam from INTUIT.COM with the SUBJECT: PAYMENT OVERDUE and contains a link to download a form from a Dropbox. Obviously, very suspicious and clearly spam. We're using Postini as our Edge Transport/ Spam filter but messages
    are still getting in. I've enable anti-spam on all my mailbox servers, set the SCL values but that hasn't worked.
    I understand that Exchange Edge Transport role has the more aggressive spam fighting features but Microsoft also recommends an online spam filter. 
    Needless to say, we've taken steps to quarantine those messages based on subject and sender in Postini but now would like to delete those messages from the users in went to. My users are two different DAG mailbox databases. I found this article http://www.techieshelp.com/delete-mail-from-multiple-mailboxes/ but
    the command didn't work. I'm thinking its because I have DAG and a couple of databases. I even tried "get-mailbox -database "databasename" | search-mailbox -searchquery subject: "Payment Overdue"" and that didn't work. 
    I'm running Exchange 2013 SP1 DAG across two sites comprised of four 2013 SP1 mailbox servers.

    Check this out
    http://technet.microsoft.com/en-us/library/ff459253%28v=exchg.150%29.aspx and specifically look at the section titled  "Search messages and log the search results"
    Or you can use this
    http://technet.microsoft.com/en-us/library/aa996371%28v=exchg.150%29.aspx with the WHATIF parameter
    Alternatively if you are open the 3rd party solutions check out Lucid8's DigiScope
    http://www.lucid8.com/product/digiscope.asp
    which would allow you to see the search results and then delete OR if desired you can set the On FIND action to Export to PST and then Delete so that you can preserve and then remove messages on the fly as the search system finds
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Exchange 2013 DLP with Exchange 2010 mailboxes

    Ive got an Exchange 2007/2010 environment. I've been looking at Exchange 2013 and am interested in the DLP funtionality.
    There are no plans to move mailboxes to Exchange 2013 but would it be possible to install an Exchange 2013 CAS/Mailbox server in my environment and route email through it to make use of the DLP ?
    Current environment consists of Exchange 2010 DAG, Casarray and hub transport servers, and Exchange 2007 mailbox servers, CAS and hub transports. Mail to the internet is sent to a smarthost.
    Thank you.

    Hi Maria,
    DLP Policies are actually a specific transport rule. Since the transport rules with Exchange 2010 didn’t provide such feature to monitor and check the e-mail
    content, I am afraid, in theory, it’s not possible.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Test-ReplicationHealth Database Redundandacy and Database Avaliability *FAILED* Exchange 2013 DAG setup

    Trying to setup DAG between 2 exchange 2013 servers - one of them being in the remote location with physical point to point line. We have no firewall rules between 2 locations
    EX01 ( on site)                                          
    EX02 (remote)
    ETH01 10.11.1.2/24 - MAPI                       ETH01 10.11.13.15/24
    ETH02 10.0.0.1/30 - REPLICATIOn            ETH02 10.0.0.2/30 - REPLICATION
    Witness server is in 3rd remote location
    These are the test results I get from Test-ReplicationHealth and Cluster Network Validation
    I also run a Nmap command to make sure udp port 3343 is open on both sides
    alex serdyukov

    Hi,
    The error message said that current Redundancy Count was 1 but expected Redundancy Count was 2. Therefore, Database 'IT2013' does not have enough copies configured to meet the validation criteria.
    Please replicate that database to another server at least. We can refer to Hinte's suggestion to
    add another copy for the database 'IT2013' in the DAG then check whether the issue persists.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 coexistence with 2010

    Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:
    Autodiscover would fail for 2010 users but fine for 2013 users:
    HTTP Response Headers:
    request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
    X-CasErrorCode: ServerNotFound
    Persistent-Auth: true
    X-FEServer: CPC8000-CAS01
    Content-Length: 0
    Cache-Control: private
    Date: Sun, 01 Jun 2014 01:22:50 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 153 ms
    and
    Created a new user on 2010 and login to OWA does this:
    Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
    I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:
    Checked AD Replication and it was fine
    Exchange 2013 was at SP1
    Exchange 2010 was at SP3 Rollup 6
    Exchange 2010 was a single server with CAS/HUB/Mailbox
    Exchange 2010 was not using a CAS Array
    Exchange 2013 had two mailbox servers in a DAG and one CAS server
    I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
    https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
    I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added
    Would really love some input to see what I did wrong. Thank you!

    Thanks for responding!
    The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all. 
    Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server
    The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was
    fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:
    HTTP Response Headers:
    request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
    X-CasErrorCode: ServerNotFound
    Persistent-Auth: true
    X-FEServer: CPC8000-CAS01
    Content-Length: 0
    Cache-Control: private
    Date: Sun, 01 Jun 2014 01:22:50 GMT
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 153 ms

  • Exchange 2013 DAG / client access

    Hello
    I'm in the planning of a new Exchange 2013 infrastructure. The infrastructure will be located in a datacenter and should host about 1000 mailboxes. I have read many whitepapers and tutorials, but some things are still unclear to me.
    - Microsoft suggests multi-role servers for this amount of users because client access is no more than a reverse proxy in EX2013. Is this correct? I've read that one users with 200 mails/day needs 8.5 MCycles with only DB and 10.63 MCycles with DB and CAS
    on the same server. So I plan to start with 2 multi-role servers in a DAG. What's your oppinion on this?
    - Client connections: I assume the clients connect to the cluster IP of the DAG. How do they get directed to the server on which their database is online? Does each server need to have the cluster IP and a public IP to which the clients connect?
    - SMTP: As I understand the documentation, mails are sent from the server which the user is active on. (Which makes sense for high availability.) What is best practice regarding the protocol logs? Do the support employees need to search in the files on 2
    servers?
    Thank you very much for your input!

    Hi
    I would use the firewall for load balancing unless there is a technical reason why this is not possible.  NLB is not recommended as it is not service aware - you cannot configure a probe to test OWA is working for example - so if you already have something
    better that would be my choice.
    In the choice between IIS ARR and NLB or CAS and NLB I would go for IIS ARR as this reduces you license costs, but neither of these is better than the appliance/firewall option.
    I've never used NLB for load balancing other than on TMGs so I cannot say what the performance is like behind a firewall, in theory your assumption would be correct.
    The load balancer doesn't make this decision it just spreads the load between the active servers, the CAS role connects the use session to the correct mailbox server:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Steve

  • OWA problem Exchange 2013 coexistence with 2010

    Hi all,
    I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
    successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
    to access OWA with a mailbox that is still on 2010 it fails with the following error:
    something went wrong
    A problem occurred while you were trying to use your mailbox.
    X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
    X-OWA-Version: 15.0.913.21
    X-FEServer: <name of 2013 server>
    X-BEServer: <name of 2013 server>
    Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
    Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
    This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
    Any help is greatly appreciated!
    Best regards
    Daniel

    Hi,
    How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
    Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
    According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
     for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 redundancy with edge transparent

    Hello
    we have one exchange 2010 and I am trying to upgrade to 2013 with failover.
    we have about 300 users.
    I have done research and this is what I think right way to do but to confirm.
    I want to install CAS and mailbox on the same box and edge transparent in DMZ for OWA access.
    everything will be dual. 
    1. install win 2012 R2 with exchange 2013 with CAS and mailbox roles on two boxes
    2. install edge transparent role on two separate boxes which will be in DMZ
    my questions are, 
    is there any other option than using hardware load balancer for CAS/mailbox failover?
    is it recommended to use DAG or I have to use DAG, even if I use hardware load balancer?
    for edge transparent failover, what is recommended direction i should go?
    Thanks

    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Niko Cheng
    TechNet Community Support

  • Exchange 2013: Problem with Default Global Address List after migration

    I just completed a migration from Exchange 2007 to Exchange 2013.  The 2007 box has been decommissioned just last week.  I have been seeing weird issues with our offline addressbook and global address list, since the migration, but always thought
    it was related to Ex2007.  Well the issues still exist and here's what i've found so far:
    1.  If any user goes to Schedule Appointment in Outlook, and they click the Rooms button (on the Scheduling Assistant page), we get a LONG wait (about 5 mins or more) and then an error that says:  "The operation could not be completed because
    an offline address book is not available.  Download a copy of the offline address book."  When i click OK, the address book is up, with the "All Rooms" list showing blank (we have 3 rooms in Exchange currently).
    2.  Now if I go to the Address Book in Outlook it opens to the GAL and it's up to date...  I can also force an update to the offline address book after adding a new group or entry, so i know offline address books are being updated properly and
    working.  HOWEVER, if i go to any of the other address lists (besides Contacts and GAL) under All Address Lists (All Contacts, All Groups, All Rooms, All Users and Public Folders) I get the same error given above:  "The operation could not be
    completed because an offline address book is not available.  Download a copy of the offline address book." 
    3.  I went to the Exchange 2013 EAC and went to Organization -> Address Lists.  Everything under here said 'NO' under the Up-to-Date column.  When i looked at the properties on each list, and clicked save, I had to update to the new version.
     After doing this, the Up-to-Date column said 'YES'.  I could do all lists EXCEPT for the GAL.  It still says 'NO'
    4.  The last thing i did was set my Outlook to NOT be in cached mode.  This should give me a direct connection to the GAL and all lists, if I'm not mistaken...  So when i do this, I cannot even open see the GAL.  The ONLY option in the
    Address Book that comes up is Contacts (which are my personal ones).
    5.  I just now ran Get-GlobalAddressList | fl  in powershell on the Ex2013 server.  I see some things that make me wonder...   First; nothing in the RecipientFilter field, however, there is something in the LdapRecipientFilter field.
     Second; the RecipientFilterType field says "Legacy".  and Third; the RecipientFilterApplied field says "False".
    Didn't know what these should all be, but it appears maybe this is the cause of all my issues??  Can someone help me out here.. even if i have to recreate a new GAL, i'm fine with that, I just don't know all the steps to do so.  I just need it
    to work!
    Thanks
    Jeff
    -Jeff

    Hi,
    In my opinion, it is better to confirm whether the GAL is good, first.
    How about the GAL working in OWA?
    If GAL working well in OWA, it seems the issue on the Outlook Client or Connectivity side.
    Please trying to run Outlook on the safe mode to avoid some AVs, add-ins and firewall for testing.
    Please follow the steps as below to narrow down the OAB issue.
    Following are the locations that .lzx files in CAS server and BMX server:
    CAS:
    C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB
    MBX:
    C:\Program Files\Micorosft\Exchange Server\V15\ExchangeOAB
    Please verify whether the .lzx files update to the latest.
    1. If the .lzx files in MBX server not update to the latest.
    It should be an issue on the OAB generation side.
    2. If the .lzx files in MBX server is latest, but CAS server not.
    It should be a distribution issue.
     1) Please run Get-OabVirtualDirectory command in EMS to verify whether at least one OAB VD exist in the org. If not, please create a new one.
     2) Please make sure whether any setup for Web Distribution. Selecting the “Enabling an Offline Address Book for Web Distribution” checkbox.
     3) Please force restart File Distribution services to distribute OAB files manually.
    3. If the .lzx files in MBX server and CAS server are all update to the latest.
    It should be the connectivity between CAS server and Client issue.
     1)Please verify the network.
     2)Please check DNS, MX, etc. configuration.
     3)Please run “Test E-mail AutoConfiguration” to check the AutoDiscover details.
       Please make sure the OAB URLs are correct.
       If the OAB URLs are incorrect, please using following command to re-set them:
       Set-OABVirtualDirectory -Identity "ServerFQDN\OAB (Default Web Site)" -ExternalUrl
    https://www.contoso.com/OAB -InternalUrl
    https://mail.contoso.com/OAB
     4)Please checking the App log and finding solutions from Microsoft Technet articles or KB, according to the Event ID.
     5)If it still not working after performing the methods above unfortunately, please trying to re-build OAB Virtual Directory.
       Article for reference:
       Remove, Re-Create, and Reconnect an Offline Address Book Virtual Directory
    http://technet.microsoft.com/en-us/library/bb123595(v=exchg.141).aspx 
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Proper way to install windows update on Exchange 2010 DAG with one mailbox server in Head Office and 1 mailbox server in DR site both are members of 1 DAG

    Hi Guyz,
    I have this setup in my exchange environment.
    1 DAG with 2 members
    - One member is located in Head Office and the other member is located in DR site. All of the mailbox databases are located only in HO (Plan to add additional second member in HO soon). Now what is the proper way to install windows patches on the
    member in HO? I don't want to move the databases to DR site as much as possible.
    Appreciate your feedback and Many thanks in advance guyz..
    More power to all!
    Regards,

    Hi,
    To update the DAG members with new patches, the update process should be managed to prevent all of the DAG members from being offline at the same time.
    To do this, I recommend you move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
    For detailed steps, here is an article for your reference.
    How to Install Updates on Exchange Server 2010 Database Availability Groups
    http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
    Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for