Is the issue that OOF messages aren't sent or that you can't configure it in Outlook? The latter is indicative of your Exchange Web Services URL being configured incorrectly.
Thanks, Brian Desmond w – 312.625.1438 | c – 312.731.3132 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joseph L. Casale Sent: Thursday, August 18, 2016 6:07 PM To: '[email protected]' <[email protected]> Subject: RE: [NTSysADM] RE: exchange OOF Well you said auto discovery is not working on the internal side (which operates differently than external clients). Have you verified all the dns entries that may be utilized? What does message tracking have to say it? jlc -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Darren Martin Sent: Thursday, August 18, 2016 4:45 PM To: [email protected] Subject: RE: [NTSysADM] RE: exchange OOF All the URLs have been updated, just wondering if changing the internal to the external URL used by OWA would fix the internal issue. All of the URLs have been updated. Everything works fine internally for the most part, just not the out of office reply. D IT Support North Sound Behavioral Health Organization, LLC 301 Valley Mall Way, Suite 110 Mount Vernon, WA 98273 [email protected] Office: 360.416.7013 x749 Direct: 360.419.5649 Fax: 360.416.7017 _____ CONFIDENTIALITY NOTE: This message is intended for use only by the individual or entity to which it is addressed, and may contain information which is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication or any attachments is strictly prohibited. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joseph L. Casale Sent: Thursday, August 18, 2016 3:26 PM To: '[email protected]' Subject: RE: [NTSysADM] RE: exchange OOF Sounds like you answered it right there, u have not updated all the url's... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Darren Martin Sent: Thursday, August 18, 2016 4:16 PM To: [email protected] Subject: RE: [NTSysADM] RE: exchange OOF We changed our SMTP domain name and installed an updated wildcard certificate, but not a UCC certificate with the old domain in it, as our organization name changed. Autodiscover is failing on the internal LAN with Outlook 2010, and trying to set out of office replies from Outlook fails with a server unavailable error. OWA works fine, which is the workaround I am having folks use In the meantime. Would this be as simple as changing the internal OOF URL to the external one used by OWA?? I hope this makes better sense... Any ideas? Thanks, D -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew S. Baker Sent: Thursday, August 18, 2016 3:01 PM To: [email protected] Subject: Re: [NTSysADM] RE: exchange OOF You may want to offer some more substantive details in this request... Regards, ASB http://XeeMe.com/AndrewBaker Providing Expert Technology Consulting Services for the SMB market… GPG: 1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A <https://track.mixmax.com/api/track/v2/ugIGdGKo8OIbesT49/gIt92YuwWah12ZAVmbvpnYzFmI/i02bj5Sb1J3bmRXa51mLzR3cpxGQtRWYzl3c05mI> On Thu, Aug 18, 2016 5:43 PM, Darren Martin [email protected] wrote: Does anyone have any Exchange out of office issues after installing an updated wildcard certificate and changing their SMTP address domain names? OWA works fine, just not on internal LAN. Thanks, D
