Forum Discussion

PoorAdmin's avatar
PoorAdmin
Level 6
11 years ago
Solved

EV 11 Web App cannot connect external

Using the EV11 web app thorugh OWA 2013 dose not work externally. It works find when I am connected to our internal domain. Also it works fine with Outlook 2013 externally. When I try to run it from OWA external I get an error that says the app may not have loaded properly. If I hit ctrl and click the error msg then I get an error page that says the page cannot be display. the url that is listed is the internal domain name of the vault server. Is there anywher that I can change that value to use the external name of our EV server?

  •  

    Refer the following videos.

    If you have a TMG server refer  http://www.symantec.com/business/support/index?page=content&id=TECH199448

    $Mbx = get-mailbox "mailbox"
    New-App -mailbox $Mbx.LegacyExchangeDN -Url `
    ("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" +
    $Mbx.LegacyExchangeDN + "&BaseURL=https://published_server/EnterpriseVault")
    where:
    ■ mailbox is the name of a mailbox that is enabled for archiving, and that you
    want to enable for the Office Mail App.
    ■ EV_server is the name of any Enterprise Vault server in your site. This
    Enterprise Vault server is not necessarily the one thatis used to load the Office
    Mail App. The Enterprise Vault server that is used to load the Office Mail App
    is the server that is specified in the BaseURL parameter.
    ■ published_server is the name ofthe external server as published by the TMG.
    Since the SourceLocation in the manifest will be used to load the Office Mail App
    in Outlook or OWA regardless of the location of the client (internal or external),
    then a split DNS configuration has to be used. The DNS configuration must ensure
    that externally published_server will resolve to the TMG.
    Deploying the Office Mail App externally through TMG
    Deployment considerations
    8Internally, there are the following possibilities for how DNS can be configured:
    ■ Make TMG publish the server (published_server) on the internal network
    and make the internal DNS resolve published_server to the internal TMG
    interface.
    ■ Pick one Enterprise Vault server and make the internal DNS resolve
    published_server to that Enterprise Vault server. If Office Mail App use is
    high, it could affect the overall performance of that server.
    ■ Use round robin DNS to resolve published_server to any one ofthe Enterprise
    Vault servers in the site.

     

  •  

    Refer the following videos.

    If you have a TMG server refer  http://www.symantec.com/business/support/index?page=content&id=TECH199448

    $Mbx = get-mailbox "mailbox"
    New-App -mailbox $Mbx.LegacyExchangeDN -Url `
    ("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" +
    $Mbx.LegacyExchangeDN + "&BaseURL=https://published_server/EnterpriseVault")
    where:
    ■ mailbox is the name of a mailbox that is enabled for archiving, and that you
    want to enable for the Office Mail App.
    ■ EV_server is the name of any Enterprise Vault server in your site. This
    Enterprise Vault server is not necessarily the one thatis used to load the Office
    Mail App. The Enterprise Vault server that is used to load the Office Mail App
    is the server that is specified in the BaseURL parameter.
    ■ published_server is the name ofthe external server as published by the TMG.
    Since the SourceLocation in the manifest will be used to load the Office Mail App
    in Outlook or OWA regardless of the location of the client (internal or external),
    then a split DNS configuration has to be used. The DNS configuration must ensure
    that externally published_server will resolve to the TMG.
    Deploying the Office Mail App externally through TMG
    Deployment considerations
    8Internally, there are the following possibilities for how DNS can be configured:
    ■ Make TMG publish the server (published_server) on the internal network
    and make the internal DNS resolve published_server to the internal TMG
    interface.
    ■ Pick one Enterprise Vault server and make the internal DNS resolve
    published_server to that Enterprise Vault server. If Office Mail App use is
    high, it could affect the overall performance of that server.
    ■ Use round robin DNS to resolve published_server to any one ofthe Enterprise
    Vault servers in the site.

     

  • refer http://www.symantec.com/business/support/index?page=content&id=HOWTO97568#v81707423

    http://www.symantec.com/business/support/index?page=content&id=HOWTO97574