Exchange and SameSite Updates

Exchange and SameSite Updates

The Stable release of the Google Chrome web browser (build 80, scheduled for release on February 4, 2020) features a change in how cookies are handled. Although the change is intended to discourage malicious cookie tracking, it’s also expected to severely affect many applications and services that are based on open standards.

For more information, see SameSite Updates on the Chromium Projects website.

Microsoft is committed to addressing this change in behavior in its products and services before the February 4, 2020 rollout date to ensure our customers are minimally impacted.

Exchange Online has already rolled out changes necessary to support this change and we do not anticipate any issues.

Exchange Server’s March Cumulative Updates will contain changes necessary to support this change. We will issue CU’s for Exchange Server 2016 and 2019 and we recommend upgrading to these versions to ensure compatibility. We’re investigating solutions for earlier versions of Exchange Server.

Given the date of our scheduled CU’s comes after Google Chrome’s release date of February 4th there might be some issues experienced by users.

To avoid issues, we recommend users switch to an alternate browser, or configure the site/URL used by OWA users to be excluded from the SameSite enforcement behavior in Chrome by using the LegacySameSiteCookieBehaviorEnabledForDomainList setting.

Additional information can be found on this page.

The Exchange Team

Windows Server 2008/R2 and Windows Server 2012/R2 end of Support and Office 365 ProPlus

Plan For Change
Veröffentlicht am : 27. November 2019
Office 365 ProPlus delivers cloud-connected and always up-to-date versions of the Office desktop apps. To ensure that customers get the best value and experience from Office 365 ProPlus, we are sending this reminder as to the impact of upcoming changes to Windows support on Office 365 ProPlus.

How does this affect me?
As communicated in MC192504 (October 2019), we noted Windows 7 will go out of support after January 14, 2020. At this time, Windows Server 2008 will also go out of support. We understand Office 365 ProPlus customers may need more time in their migration to a supported operating system. Through January 2023, Microsoft will provide security updates for Office 365 ProPlus on Windows 7 and Windows Server 2008. But, during that time, as long as customers are still running one of these unsupported operating systems, Office 365 ProPlus won’t receive any new feature updates.

For Windows Server 2012/R2, we previously announced and stated in a support article, that Office 365 ProPlus will no longer be supported on Windows Server 2012 and 2012 R2. While Microsoft will not take any measures to block users with this configuration from connecting to Office 365 services, Office 365 ProPlus on Windows Server 2012/R2 will not be a supported configuration. While Microsoft does not anticipate any change to Office 365 ProPlus compatibility with Windows Server 2012/R2, customers may experience changes to performance or reliability issues. Microsoft Support will continue to accept calls from customers, however we may not be able to resolve issues that arise if those issues are determined to be unique to this configuration.

What do I need to do to prepare for this change?
For customers on Windows 7, we recommend that organizations migrate to Windows 10 or a supported operating system before the end of support date on January 14, 2020 in order to continue receiving new feature updates to Office 365 ProPlus. For more information, please refer to this article.

For customers on Windows Server 2008/R2 and Windows Server 2012/R2, we recommend migrating your applications to Azure. For those customers who need to stay on-premises, we recommend moving to Windows Server 2019.

Related Message Center Posts:

MC192504 (October 2019) – Retiring support for Windows 7 and impact on Office 365 ProPlus
MC190854 (September 2019) – Office 2013 Client Connectivity to Office 365 Services

Informationsblatt zum Lebenszyklus von Windows

Quelle: Link

In der Windows 10-Version sind die Daten zur Verfügbarkeit und zum Serviceende nach Edition gegliedert.

Windows 10-VersionsverlaufVeröffentlichungsdatumServiceende für die Editionen Home, Pro und Pro for WorkstationsServiceende für alle Enterprise- und Education-Editionen
Windows 10, Version 190321. Mai 20198. Dezember 20208. Dezember 2020
Windows 10, Version 180913. November 201812. Mai 202011. Mai 2021
Windows 10, Version 180330. April 201812. November 201910. November 2020
Windows 10, Version 170917. Oktober 20179. April 201914. April 2020
Windows 10, Version 17035. April 2017*9. Oktober 20188. Oktober 2019
Windows 10, Version 16072. August 201610. April 20189. April 2019
Windows 10, Version 151110. November 201510. Oktober 201710. Oktober 2017
Windows 10, veröffentlicht im Juli 2015 (Version 1507)29. Juli 20159. Mai 2017 9. Mai 2017
* Windows 10, Version 1703, für Enterprise-, Education- und IoT Enterprise-Editionen wurde am 11. April 2017 veröffentlicht. 
Hinweis: Nicht alle Features eines Updates funktionieren auf allen Geräten. Ein Gerät erhält möglicherweise keine Updates, wenn die Gerätehardware nicht kompatibel ist, aktuelle Treiber fehlen, nicht genügend Speicherplatz vorhanden oder der Support des Originalgeräteherstellers (Original Equipment Manufacturer, OEM) abgelaufen ist.  Weitere Informationen zur Kompatibilität finden Sie in den Windows 10-Systemanforderungen und den Windows-Prozessoranforderungen

Basic Authentication Retirement for legacy protocols in Exchange Online

Major update: Announcement started
Applied To: All customers
  Beginning October 13, 2020, we will retire Basic Authentication for EWS, EAS, IMAP, POP and RPS to access Exchange Online. Note: this change does not impact SMTP AUTH.

There are several actions that you and/or your users can take to avoid service disruptions on client applications, and we describe them below. If no action is taken, client applications using Basic Authentication for EWS will be retired on October 13, 2020.

Any application using OAuth 2.0 to connect to these protocols, will continue to work without change or interruption.

[What do I need to do to prepare for this change?]

You have several options on how to prepare for the retirement of Basic Authentication.   You can start updating the client applications your users are using to versions that support OAuth 2.0 today. For mobile device access, there are several email apps available that support Modern Authentication, but we recommend switching to the Outlook app for iOS and Android as we believe it provides the best overall experience for your M365 connected users. For desktop/laptop access, we encourage the use of the latest versions of Outlook for Windows and Outlook for Mac. All Outlook versions including, or newer than, Outlook 2013 fully support OAuth 2.0. If you have written your own code using these protocols, you will need to update your code to use OAuth 2.0 instead of Basic Authentication, you can reach out to us on stack overflow with the tag exchange-basicauth if you need some help.   If you or your users are using a 3rd party application, which uses these protocols, you will either need to   reach out to the 3rd party app developer who supplied this application to update it to support OAuth 2.0 authentication

-or- assist your users to switch to an application that’s built using OAuth 2.0.  
We are in the process of building reports that will help you identify any impacted users and client applications in your organization. We will make these reports available to you in the next few months and communicate their availability via a follow-up Message center post.

Please click Additional Information to learn more about this retirement.

Office 2013 Client Connectivity to Office 365 Services

Office 2013 Client Connectivity to Office 365 Services
Major update: Announcement started
Applied To: All customers
As previously announced via blog and MC175274 (March, 2019), Office 2013 clients’ connections to commercial Office 365 services will not be supported after October 13, 2020. After this date, ongoing investments in the Office 365 cloud services – including Exchange Online, SharePoint Online, and OneDrive for Business – will proceed based on post-Office 2013 requirements. We recommend that organizations with Office 2013 clients consider migrating to Office 365 ProPlus.

Support for Office 2016 and Office 2019 connections to Office 365 cloud services will continue until October 2023. Up to date information on current system requirements can be found under on the Office system requirements page, with related timelines available in the Office system requirements matrix.

[How does this affect me?]

Microsoft will not take any active measures to block older Office clients, such as Office 2013 and Office 2010, from connecting to Office 365 services. However, legacy clients attempting to connect to a modern, always up- to- date cloud service may experience performance and reliability issues. Customers will face an increased security risk, and may find themselves out of compliance depending on specific regional or industry requirements. Microsoft Help may not be able to resolve issues that arise due to unsupported service connections.

[What do I need to do to prepare for this change?]

In order for you to better understand whether and how your organization is affected by this change, and where you need to migrate users, there are two System Center Configuration Manager dashboards (updated as part of version 1902) that can help:

– the SCCM Product Lifecycle dashboard allows you to see which versions of Office are running on your desktops, to determine which will need updated Office apps to help ensure a seamless connection to Office 365 services
– the Office 365 ProPlus Upgrade Readiness report on the Office 365 client management dashboard helps to identify desktops in your organization that are ready to upgrade to Office 365 ProPlus with high confidence.

Use these dashboards to identify users on Office 2010 and Office 2013 clients, deploy Office365 ProPlus or a supported version of Office perpetual to those desktops, and ensure that they will have supported access to Office 365 services after October 13, 2020.

Windows 10, version 1903 and Windows Server, version 1903

Quelle: Link

Current status as of July 16, 2019:
We are initiating the Windows 10 May 2019 Update for customers with devices that are at or nearing end of service and have not yet updated their device. Keeping these devices both supported and receiving monthly updates is critical to device security and ecosystem health. Based on the large number of devices running the April 2018 Update, that will reach the end of 18 months of service on November 12, 2019, we are starting the update process now for Home and Pro editions to help ensure adequate time for a smooth update process.

Our update rollout process takes into consideration the scale and complexity of the Windows 10 ecosystem, with the many hardware, software, and app configuration options users have, to provide a seamless update experience for all users. We closely monitor update feedback to allow us to prioritize those devices likely to have a good update experience and quickly put safeguards on other devices while we address known issues. Windows 10 Home and Pro edition users will have the ability to pause the update for up to 35 days so they can choose a convenient time.

The Windows 10 May 2019 Update is available for any user who manually selects “Check for updates” via Windows Update on a device that does not have a safeguard hold for issues already detected. If you are not offered the update, please check below for any known issues that may affect your device.

We recommend commercial customers running earlier versions of Windows 10 begin targeted deployments of Windows 10, version 1903 to validate that the apps, devices, and infrastructure used by their organizations work as expected with the new release and features.

Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.

Windows 10 April 2018 Update approaching end of service

Quelle: Link

Windows 10 April 2018 Update approaching end of service
For Windows 10 devices that are at, or within several months of reaching, end of service, Windows Update will automatically initiate a feature update; keeping those devices supported and receiving the monthly updates that are critical to device security and ecosystem health. The Windows 10 April 2018 Update (Windows 10, version 1803) will reach end of service on November 12, 2019 for Home and Pro editions. Starting this June, we will begin updating devices running the April 2018 Update, and earlier versions of Windows 10, to ensure we can continue to service these devices and provide the latest updates, security updates and improvements. We are starting this machine learning (ML)-based rollout process several months in advance of the end of service date to provide adequate time for a smooth update process.

Quelle: Link

Datenblatt FUJITSU Support Pack Hardware

Quelle: Link

 On-site Services Der gemeldete Fehler wird von Fujitsu mittels telefonischem Support oder Fernzugriff analysiert. Nach Ermessen von Fujitsu wird ein Termin für einen Servicetechniker angesetzt, um vor Ort nach Bedarf eine weitere Diagnose vorzunehmen und eine Lösung für das diagnostizierte Problem zu finden. Bei einem Hardware-Ausfall wird die Betriebsbereitschaft wiederhergestellt, indem das defekte Teil am Installationsstandort ausgetauscht oder repariert wird. Für die On-site Services können verschiedene Servicelevel-Optionen einschließlich Antritts- oder Wiederherstellungszeit gewählt werden (siehe „Optionen“). Die Servicelevels gelten für Installationsorte innerhalb einer bestimmten Entfernung bis zu einer autorisierten Fujitsu Servicestelle (normalerweise 100 km). Geografische Beschränkungen Einzelheiten zum jeweiligen Land unter Für Installationsorte, welche die jeweiligen Beschränkungen nicht erfüllen, behält sich Fujitsu das Recht vor, die Antritts- bzw. Wiederherstellungszeit zu ändern bzw. die zusätzlichen Kosten in Rechnung zu stellen. Für verkehrstechnisch schwer zu erreichende Installationsorte (z. B. Inseln, Berge) müssen spezielle Servicelevels vereinbart werden.

NICHT IM VERTRAGSUMFANG ENTHALTENE SERVICES (AUSSCHLÜSSE) Die vertraglich vereinbarten Support Services beinhalten nicht die Sicherung oder Installation des Betriebssystems, der Anwendungssoftware sowie der Systemkonfiguration und Nutzerdaten. Die von Störungen unabhängige Bereitstellung und Installation von Updates/Upgrades von BIOSTreibern/Betriebssoftware oder Firmware liegt in der Verantwortung des Kunden. Entsprechende Informationen und Downloads finden Sie unter: Ausnahme: Bei Festplattenaustausch in Client-Computing-Geräten (Desktops, Notebooks) muss das vorinstallierte Betriebssystem neu installiert werden, sofern es durch den Benutzer zur Verfügung gestellt wird. Es liegt in der Verantwortung des Kunden, regelmäßig umfassende Backups vorzunehmen, darunter das Backup von Anwendungs- und Betriebssystemsoftware.

 Antrittszeit Die Antrittszeit bezeichnet den Zeitraum von der Call-Annahme bis zu dem Zeitpunkt, an dem ein Techniker normalerweise mit dem per Diagnose bestimmten Ersatzteil (falls erforderlich) am Kundenstandort eintrifft. Zeiträume, die außerhalb der vereinbarten Servicezeiten liegen, werden nicht auf die Antrittszeit angerechnet. Die Antrittszeit findet keine Anwendung, wenn ein Fehler per Fernzugriff behoben werden kann. Die Fehlerbehebung dauert an, bis die IT-Infrastruktur wieder einsatzbereit ist bzw. bis ein angemessener Fortschritt bei der Problemlösung erzielt wurde. Die Arbeit kann zeitweilig eingestellt werden, wenn zusätzliche Teile oder Ressourcen erforderlich sind, wird aber wieder aufgenommen, sobald diese verfügbar sind.

 Wiederherstellungszeit Die Wiederherstellungszeit bezeichnet den Zeitraum von der CallAnnahme bis zu dem Zeitpunkt, an dem ein Servicetechniker die Betriebsbereitschaft der fehlerhaften Hardware in der Regel wiederhergestellt hat. Zeiträume, die außerhalb der vereinbarten Servicezeiten liegen, werden nicht auf die Wiederherstellungszeit angerechnet. Zur Wiederherstellungszeit zählt auch nicht die Zeit, die auf die Wiederherstellung von Daten bzw. die Installation von Software/Betriebssystemen oder entsprechenden Updates und/oder die Wiederherstellung einer kundenspezifischen Konfiguration verwendet wird.