You might not be able to send email with an Outlook.com, Office 365, or Exchange account until you update to iOS 11.0.1.
If your email account is hosted by Microsoft on Outlook.com or Office 365, or an Exchange Server 2016 running on Windows Server 2016, you might see this error message when you try to send an email with iOS 11: “Cannot Send Mail. The message was rejected by the server.”
To fix the issue, update to iOS 11.0.1 or later.
On April 6 i was attending the Dutch Skype for Business user groups event at Microsoft Netherlands. Especially for those present in the Netherlands, we will explain the new telephony capabilities Netherlands in Office 365 (PSTN calling).
The agenda:
17: 30-18: 00 Registration
18:00 to 18:30 Skype for Business Online developments in the Netherlands (van Houttum, MVP)
18:30 to 18:45 Welcome and Key Note Session
18:45 to 19:10 Session 1 (Nordic)
Cloud PBX – Options (AA CQ CCE and more) (Lasse Nordvik Wedo, MVP), support from (Stale Hansen, MVP)
19:10 to 19:35 Session 2 (Germany)
Online Dial Pans with CloudPBX (Thomas Poett, MVP)
19: 35- 20:00 Session 3 (UK)
Trusted Server API SfB (Tom Morgen and Ben Lee, MVPs)
8:00 p.m. to 20:15 BREAK
20:15 to 20:40 Session 4 (Benelux)
Teams in O365 (Johan Delimon, MVP) with support from (van Houttum, MVP)
20:40 to 21:05 Session 5 (Italy)
Hybrid Skype4B Best Practice for Cloud PBX with PSTN Connectivity (Alessandro Appiani, MVP)
If you want to look the session back: https://join-emea.broadcast.skype.com/skype4b-ug.de/9dab4d2cc4074a25b7ab83ddbfe57821/nl-NL/
Status: Active
Action Required by: October 31, 2017 at 5:59 PM UTC
Details: On October 31st, 2017, Exchange Online mailboxes in Office 365 will require connections from Outlook for Windows use MAPI over HTTP, our new method of connectivity and transport between Outlook for Windows and Exchange. In May of 2014, Microsoft introduced MAPI over HTTP as a replacement for RPC over HTTP. RPC over HTTP was a legacy connection protocol that is being deprecated from Exchange Online. Beginning October 31, 2017, Outlook for Windows clients using RPC over HTTP will be unable to access their Exchange Online mailbox. The necessary action depends on the version of Outlook in use in your organization. If you are using Outlook 2007 or earlier, you need to upgrade. Outlook 2007 does not contain support for the MAPI/HTTP protocol. We encourage you to update to the Office 365 ProPlus subscription, or access Outlook via the web browser (which is included in your current subscription plan). Outlook 2010-2016 customers will need to ensure their version of Outlook for Windows is set up to support MAPI/HTTP. At a minimum, you should ensure you have installed the December 2015 update. Lastly, ensure your Outlook clients are not using a registry key to block MAPI/HTTP.
Message Center: MC85988 – Potential service disruption for Outlook for Windows users
Posted: November 16, 2016
Additional Information: KB3201590: RPC over HTTP deprecated in Office 365 on October 31, 2017
On ADFS page you get error: 00000000-0000-0000-0d00-0080000000e1
Event viewer: Event 364 Microsoft.IdentityServer.Web.IdPInitiatedSignonPageDisabledException: MSIS7012: An error occurred while processing the request.
Get-AdfsProperties | select EnableIdPInitiatedSignonPage
Set-AdfsProperties -EnableIdPInitiatedSignonPage $true
There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:
Configuration.xml
<Configuration>
<Add SourcePath=”d:\2016\” OfficeClientEdition=”32″ Branch=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
<Product ID=”VisioProRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
</Add>
<!– <Updates Enabled=”TRUE” Branch=”Current” /> –>
<Display Level=”Full” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
</Configuration>
Download
D:\2016\setup.exe /download d:\2016\configuration.xml
Install / Configure Office 365 (2016)
D:\2016\setup.exe /configure d:\2016\configuration.xml
Source: https://technet.microsoft.com/en-us/library/jj219424.aspx
Lync Basic 2013 provides all the basic functionality that’s available in the full version of Lync (Lync 2013). However, if you want to use any of the following features, you will need to upgrade to Lync 2013:
Download Skype for Business Basic
Microsoft Skype for Business Basic (64 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49440
Microsoft Skype for Business Basic (32 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49439
Office Lens trims, enhances and makes pictures of whiteboards and docs readable, and saves them to OneNote. You can use Office Lens to convert images to PDF, Word and PowerPoint files too. Office Lens is like having a scanner in your pocket. Like magic, it will digitalize notes on whiteboards or blackboards. Always find important documents or business cards. Sketch your ideas and snap a picture for later. Don’t lose receipts or stray sticky notes again!
What’s new:
– Now you can convert your pictures to PDF files with selectable text, in addition to Word and PowerPoint files, and save them to OneDrive.
Scenarios:
– Capture and crop a picture of a whiteboard or blackboard and share your meeting notes with co-workers.
– Make digital copies of your printed documents, business cards or posters and trim them precisely.
– Printed text will be automatically recognized (using OCR) so you can search for words in images and copy and edit them.
Features:
– With Whiteboard mode, Office Lens trims and cleans up glare and shadows.
– With Document mode, Office Lens trims and colors images perfectly.
– Pictures are saved to your camera roll and also directly into OneNote, so you can see the images across all your devices.
– Choose to convert images to PDF (.pdf), Word (.docx), or PowerPoint (.pptx) files that are automatically saved to OneDrive.
Note: Office Lens requires logging in with your Microsoft Account. Your Microsoft Account must be same as the one registered on your device.
Move Public Folder script from 2007/2010 to Office 365 Script created by Ward Vissers
www.wardvissers.nl
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER
Please Select the Choice You Want
Prepare for Migration (Legacy Exchange Server
00) Add the Office 365 Domain Name
01) Take a snapshot of the original source folder structure
02) Take a snapshot of public folder statistics such as item count, size, and owner.
03) Take a snapshot of the permissions
04) Locate public folders that have a backslash in the name
05) Rename Public Folder
06) Checks the public folder migration status.
07) Set PublicFolderMigrationComplete to False
Check Office 365
08) Get-PublicFolderMigrationRequest
09) Get-Mailbox -PublicFolder
10) Get-PublicFolder
Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server)
11) Export-PublicFolderStatistics PFSizeMap.csv
12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv
Create the public folder mailboxes on Exchange Online
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders
15) Export mail-enabled public folders from Active Directory
16) LegacyExchangeDN Administrator
17) LegacyExchangeDN Public Folder Server
18) External Name Outlook Anywhere
19) Set the XML file
20) Give the CSV file to start the Migration
21) Public Folder Migration Status
Lock down the public folders on the legacy Exchange server for final migration (downtime required)
22) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required)
23) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration
24) Add Public Folder to Test User
25) Unlock the public folders for all other users
26) Public Folder Migration Complete (Legacy Exchange Server)
27) Public Folders Enabled Local
Final Check
28) Take a snapshot of the original source folder structure.
29) Take a snapshot of the public folder statistics such as item count, size, and owner
30) Take a snapshot of the permissions
99) Exit 
Download: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Migratie-to-25bd50a0
After a customer migrated to Exchange Online some time ago.
They wanted not a hybrid situation. but they are using still DirSync!
After reading: Decommissioning your Exchange 2010 servers in a Hybrid Deployment a I read its not a real problem.
Changed DirSync & After that Uninstalling Exchange 2013 was very easy.
I had only to disable the Arbitration mailboxes: I did that with the following powershell command:
Get-Mailbox -Arbitration | disable-Mailbox -arbitration -RemoveLastArbitrationMailboxAllowed
I did not publish this article because i has still some doubts!!
I had still a question: Do want to remove the last Exchange Server? Have you a supported Environment without a local Exchange Server and still using DirSync??
Yes & No!!
After reading Concerning Trends Discovered During Several Critical Escalations
Microsoft Says:
You may remove the last Exchange Server locale when you move totally to Office 365/Exchange Online, but change Exchange Attribuuts trough ADSI is not supported.
If you don’t have a third party tool for that. The only way is trough ADSI and that is not supported.
My Conclusion:
You have a support issue when you dropped a Call at Microsoft and they investigate your environment.
Don’t remove the last Exchange Server even when all mailboxen exist in Office 365/Exchange Online and keep them up to date!
You can always install a Exchange Server but most of the times it will be always to late!
Microsoft recommends adopting a software update strategy that ensures all software follows N to N-1 policy, where N is a service pack, update rollup, cumulative update, maintenance release, or whatever terminology is used by the software vendor. Microsoft strongly recommend that our customers also adopt a similar strategy with respect to hardware firmware and drivers ensuring that network cards, BIOS, and storage controllers/interfaces are kept up to date.
Software patching is not simply an issue for Microsoft software. You must also ensure that all inter-dependent solutions (e.g., Blackberry Enterprise Server, backup software, etc.) are kept up-to-date for a specific release as this ensures optimal reliability and compatibility.
Customers must also follow the software vendor’s Software Lifecycle and appropriately plan on upgrading to a supported version in the event that support for a specific version is about to expire or is already out of support.
For Exchange 2010, this means having all servers deployed with Service Pack 3 and either Rollup 7 or Rollup 8 (at the time of this writing). For Exchange 2013, this means having all servers deployed with Cumulative Update 6 or Cumulative Update 7 (at the time of this writing).
For environments that have a hybrid configuration with Office 365, the servers participating in the hybrid configuration must be running the latest version (e.g., Exchange 2010 SP3 RU8 or Exchange 2013 CU7) or the prior version (e.g., Exchange 2010 SP3 RU7 or Exchange 2013 CU6) in order to maintain and ensure compatibility with Office 365. There are some required dependencies for hybrid deployments, so it’s even more critical you keep your software up to date if you choose to go hybrid.