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.

FUJITSU Aktionsmodelle auf einen Blick – 2019-09

Fujitsu Value4you Productfinder
Fujitsu Aktionsmodelle – Auf einen Blick

Übersichtskarte – Fujitsu Lifebook – Notebooks

Übersichtskarte – Fujitsu Stylistic und Lifebook – Tablets

Übersichtskarte – Fujitsu Esprimo – Desktops

Übersichtskarte – Fujitsu Celsius – Workstations

Übersichtskarte – Fujitsu Display – Monitore

Übersichtskarte – Fujitsu Server PRIMERGY Systeme

Übersicht – Fujitsu Support Pack Hardware

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.

2019 SHA-2 Code Signing Support requirement for Windows and WSUS

Quelle: Link


To protect your security, Windows operating system updates are dual-signed using both the SHA-1 and SHA-2 hash algorithms to authenticate that updates come directly from Microsoft and were not tampered with during delivery. Due to weaknesses in the SHA-1 algorithm and to align to industry standards Microsoft will only sign Windows updates using the more secure SHA-2 algorithm exclusively.

Customers running legacy OS versions (Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2) will be required to have SHA-2 code signing support installed on their devices by July 2019. Any devices without SHA-2 support will not be offered Windows updates after July 2019. To help prepare you for this change, we will release support for SHA-2 signing in 2019. Some older versions of Windows Server Update Services (WSUS) will also receive SHA-2 support to properly deliver SHA-2 signed updates. Refer to the Product Updates section for the migration timeline.

Background details

The Secure Hash Algorithm 1 (SHA-1) was developed as an irreversible hashing function and is widely used as a part of code-signing. Unfortunately, the security of the SHA-1 hash algorithm has become less secure over time due to weaknesses found in the algorithm, increased processor performance, and the advent of cloud computing. Stronger alternatives such as the Secure Hash Algorithm 2 (SHA-2) are now strongly preferred as they do not suffer from the same issues. For more information about of the deprecation of SHA-1, see Hash and Signature Algorithms.

Product updates

Starting in early 2019, the migration process to SHA-2 support will occur in stages, and support will be delivered in standalone updates. Microsoft is targeting the following schedule to offer SHA-2 support. Please note that the timeline below is subject to change. We will update this page as the process begins and as needed.

Target DateEventApplies To
March 12, 2019Stand Alone updates that introduce SHA-2 code sign support will be released as security updates.Windows 7 SP1,
Windows Server 2008 R2 SP1.
March 12, 2019Stand Alone update will be delivered to WSUS 3.0 SP2 that will support delivering SHA-2 signed updates. For those customers using WSUS 3.0 SP2, this update should be installed no later than June 18, 2019.WSUS 3.0 SP2
April 9, 2019Stand Alone updates that introduce SHA-2 code sign support will be released as security updates.Windows Server 2008 SP2.
June 18, 2019Windows 10 updates signatures changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone.
Windows 10 1709,
Windows 10 1803,
Windows 10 1809,
Windows Server 2019
June 18, 2019Required: For those customers using WSUS 3.0 SP2, the updates should installed by this date.WSUS 3.0 SP2
July 16, 2019Required: Updates for legacy Windows versions will require that SHA-2 code signing support be installed. The support released in March and April will be required in order to continue to receive updates on these versions of Windows.Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2.
July 16, 2019Windows 10 updates signatures changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone.Windows 10 1507,
Windows 10 1607,
Windows 10 1703
August 13, 2019Contents of updates for legacy Windows versions will be SHA2 signed (embed signed binaries and catalogs). No customer action is expected for this milestone.
Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2.
September 16, 2019Legacy Windows updates signatures  changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone.Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2,
Windows Server 2012,
Windows 8.1,
Windows Server 2012 R2

WSUS 3.0 SP2

For customers using WSUS 3.0 SP2, we recommend that you update your servers with the SHA2 updates for WSUS 3.0 SP2 by June 18th, 2019 to ensure that SHA2 signed updates can be delivered to your enterprise.

Der Support für Windows 7 endet am 14. Januar 2020

Supportlebenszyklus für Windows 7

Microsoft hat sich verpflichtet, 10 Jahre Produktsupport für Windows 7 bereitzustellen, das am 22. Oktober 2009 veröffentlicht wurde. Nach Ablauf dieser 10 Jahre wird Microsoft den Support für Windows 7 einstellen, sodass wir unsere Investitionen auf die Unterstützung neuerer Technologien und großartiger neuer Erfahrungen konzentrieren können. Der Support für Windows 7 endet am 14. Januar 2020. Anschließend sind weder technische Unterstützung noch automatische Updates zum Schutz des PCs verfügbar. Microsoft empfiehlt dringend, vor Januar 2020 zu Windows 10 wechseln, um Situationen zu vermeiden, in denen Sie Service oder Support benötigen, der nicht mehr verfügbar ist.

Quelle: Link