Exchange 2013 Office Web App integration removal

Good Day,

Have discovered the following error occurring in our Exchange Server event viewer:

There was a failure connecting to or otherwise retrieving Data from the Wac Discovery Service. We will fall back to stellent. Error retrieving wac discovery data from endpoint Exception was System.Net.WebException: The remote name could not be resolved: ''
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.Clients.Owa2.Server.Core.WacDiscoveryClient.FetchDiscoveryResults()

I learned this was referencing that our exchange server cannot find the office web app server that it is supposed to be integrated with. There is not a Office Web App server in our organization, so I need to remove this reference.

I am assuming the prior IT group had attempted to set this up (attempted to contact them in regards to how to fix this) and I am unfamiliar with how to remove the WACDiscoveryEndpoint reference on the Exchange Server. It appears it can only be done through command line. I have found plenty of postings showing how to set it, just none explaining how to remove the reference.

The WACDiscoveryEndpoint is currently set to

Any assistance will be greatly appreciated.


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason CrawfordTransport NinjaCommented:
I've never deployed OWAS, but after reading the really long Technet article on deployment you might be in a situation where the easier job is to push onward until it works.  Plus you'd have the added benefit of providing neat functionality to your client.

Two things jump out at me with the OWAS URL.  First it uses https which begs the question, "what is the status of the cert?"  Second, I know you stated there is no officewebapp server in your environment, but the URL you provided is in the .com TLD which most IT folks wouldn't use for their internal domain name unless it was with an extra sub-domain (ie  This seems to indicate the OWAS server *might* be hosted offsite somewhere.  Or maybe you just missed a CNAME in internal DNS.  Best practice published by Microsoft is to dedicate a server to OWAS, but how many times do you see Exchange installed on a Domain Controller in the wild.  Point is it may be installed alongside another server somewhere you haven't found yet.

In any case, it looks like OWAS settings are configured at the org level with Set-OrganizationConfig:

Maybe you can just:

Set-OrganizationConfig -WACDiscoveryEndPoint $null
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -WacViewingOnPrivateComputersEnabled $false
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -WacViewingOnPublicComputersEnabled $false

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BrockstedtAuthor Commented:
Keyser Soze

Will give this a try and update.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.