tag:blogger.com,1999:blog-9192990822837132182.post7393897953558672477..comments2023-11-03T05:50:06.709-07:00Comments on \>Get-CsJosh -Blog: Lync 2013 and OWA Integration TroublesGetCsJoshhttp://www.blogger.com/profile/16478660853228117950noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9192990822837132182.post-42176229241285296412016-02-26T14:53:13.102-08:002016-02-26T14:53:13.102-08:00Hello Onkel, and thanks for the question! Good que...Hello Onkel, and thanks for the question! Good question, and I had to chase this down. While I knew this was set by an admin in earlier steps to set up OWA integration (https://lyncdude.com/2013/06/26/integrate-lync-2013-with-exchange-2013-step-by-step-part-2/), I didn't know if you had to use 'outlookwebaccess' specifically or not. From all the various articles I have researched, it does not appear that you have to call the TrustedPartnerApplication 'outlookwebaccess' in particular. I have seen some articles where they uses 'outlookwebapp' with success. Unless you have a really good reason to deviate from the norm, though, I would still recommend using what is found in most How-To articles to make future support a little easier on everyone, should it be needed. Good luck!GetCsJoshhttps://www.blogger.com/profile/16478660853228117950noreply@blogger.comtag:blogger.com,1999:blog-9192990822837132182.post-34162977391701519142016-02-26T07:01:22.073-08:002016-02-26T07:01:22.073-08:00Question: Does it have to be "urn:application...Question: Does it have to be "urn:application:outlookwebaccess" or can it also be "urn:application:exowa"? I mean... is the name fixed by the system, or is this just a name that has been assigned by the sysadmin in a previous step? Onkel Stonyhttps://www.blogger.com/profile/06791483449274818936noreply@blogger.com