OnePass Mail Archiving for Exchange - OWA proxy enabler

Last post 04-20-2016, 12:50 PM by tcottrell. 4 replies.
Sort Posts: Previous Next
  • OnePass Mail Archiving for Exchange - OWA proxy enabler
    Posted: 05-12-2015, 5:11 PM

    can someone please explain how the OWA Proxy Enabler is used in Simpana v10 SP10+ using onepass archiving for exchange mailbox? Is it still required to be installed on every Exchange (2010 in this case) server with the CAS role? Documentation has not much references to OWA proxy enabler these days, but lists this component in de system requirements of the onepass agent.

    I'm also looking on information regarding communication of the different components (like the OWA proxy enabler) in a onepass for exchange environment when restoring stubs using OWA or Outlook Addin. Which components talk to each other during such a process?

    Enironment details:

    Exchange 2010 DAG with 2 servers
    Off-host onepass agent
    CommServe installed with Web Server and Web console.

    thanks.

  • Re: OnePass Mail Archiving for Exchange - OWA proxy enabler
    Posted: 06-12-2015, 5:06 PM

    I have been asking myself the same question, anyone?

  • Re: OnePass Mail Archiving for Exchange - OWA proxy enabler
    Posted: 04-12-2016, 3:13 PM

    bump...

  • Re: OnePass Mail Archiving for Exchange - OWA proxy enabler
    Posted: 04-20-2016, 12:41 PM
    • isle is not online. Last active: 06-04-2019, 3:28 PM isle
    • Top 25 Contributor
    • Joined on 08-21-2012
    • NJ
    • Adept
    • Points 308

    I will get someone to update this bump :)

  • Re: OnePass Mail Archiving for Exchange - OWA proxy enabler
    Posted: 04-20-2016, 12:50 PM

    Sorry for the delayed response!  Missed this question and just had it brought to my attention!

    For the most part it is not needed unless:

    1) You have legacy Outlook Addins (V9) in the environment. Those wlil still leverage the OWA proxy enabler to redirect recall requests to a server with the Exchange Mailbox Archiver agent installed (yes MB archiver NOT MB!)

    2) Double click OWA recalls.  Only valid for Exchange 2010 or 2003 though.  Exchange 2013 does not support double click recalls for OWA.  Instead either implement the office app that is available or make sure stubbing is done with a recall link.

    As far as communication is concerned, depends on the type of recalls.  Since you asked about OWA Proxy Enabler here lets start with 'legacy' recalls:

    Recall request starts at the OWA Proxy enabler (most likely a CAS server for Exchange 2010, directly to the MB role server on Exchange 2007 -- this is determined by where the OL profile is pointed **NOTE if you are running Exchange 2013 since the Exchange server is listed as a GUID a registry key needs to be implemented to point recalls directly to the OWA proxy enabler or the mailbox archiver agent).

    The OWA proxy enabler , by default, will take communication from the client over port 8402 (evmgrc).  The request is then redirected to the server specified on that server under advanced 'exchange proxy'.  That communication is also over port 8402 (evmgrc).  From there the recall should be at the Mailbox archiver agent which will facilitate the rest of the recall which basically entails connecting to Exchnage via an Outlook profile and restoring the mail item directly there.  The communication chain is than passed back to the requesting client over the same channels (8402-evmgrc) to notify the client that the recall is done and a refresh has to occur to view the item.

    The process in V10 is completely different.  All recall requests go through the web console regardless of its a recall link (quick look) that was embedded into the message, OWA double click, or Outlook addin.  The web console receives that request and passes it along to the web server which facilitates the restore of the item.  The Web server communicates to the commserve/media agent to determine the proper media to restore from and restore it!  The item does NOT have to go back to Exchange!  Instead it is rendered or passed back to the requestor via the web console as an HTML or as a MSG file.  All communication from the Web Console to the requestor is via HTTP/HTTPS.  All communication from the Web Console to the Web Server is also via HTTP.

     

    Please let me know if this answers your question.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy