We can successfully browse the EWS/Autodiscover URLs by typing the address in a web browser. I believe our Autodiscover and EWS URLs are all configured and working correctly. If you have feedback for TechNet Subscriber Support, Alice, Mark the replies as answers if they help. Sure that you completely understand the risk before retrieving any suggestions from the above link. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. The sites are not controlled by Microsoft. Note: Microsoft is providing this information as a convenience to you. Lync uses MAPI or EWS to communicate between itself and Outlook / Exchange, according to the error message, the issue may be caused by the EWS and MAPI status.ĭid you use SFB on premise in your environment?įor this issue, please try to deploy EWS with the following link, then test if there is the same issue Send email from anywhere else in the world and it is delivered to on premises Exchange.Ī) Fix Skype in some other way, without assigning a mailbox license?ī) Configure Exchange online to always send email to the MX for our domain, thus have email delivered on premises even if a cloud mailbox exists?Ĭalendar information coming from exchange via Exchange Web Service (EWS). This is a problem as staff will not monitor the cloud mailbox. To the cloud mailbox and not on premises Exchange. If a student with a cloud mailbox in our tenant sends email to another person with a cloud mailbox in our tenant, the mail is delivered Now we have some users with an on premises Exchange mailbox and Office 365 mailbox with the same SMTP address.
All seems to work fine with internal Exchange, but this leads to some email routing The EWS URLs within Skype display our on premises Autodiscover addresses. The conversation history is stored in our on premises Exchange mailboxes and not cloud mailboxes. The only way I have been able to get Skype for Business 2016 working properly is to assign the pilot users an Office 365 mailbox. I've tried several things to get this to work properly, but nothing has improved the situation. Internal and External EWS URLs are blank.
Skype shows 'MAPI Unavailable' and 'EWS not initialised' error messages. Within Skype for Business application, the conversation history, Calendar, Missed calls, notifications etc.
Small number of pilot users have a Skype for Business license only. Second domain (Faculty), no users have mailbox licenses.
One domain (students), all users have Office 365 mailbox licenses Azure and Office 365 tenant (both domains) Skype for Business 2016 - installed standalone from MSI Windows 7 Desktops with Office 2010 (inc Outlook) Single forest, two domain on premises Active Directory
0 kommentar(er)
