Support for Office 365 ProPlus on Windows 8.1 and Windows Server 2016
Office 365 ProPlus delivers cloud-connected and always up-to-date versions of the Office desktop apps. To support customers already on Office 365 ProPlus through their operating system transitions, we are updating the Windows system requirements for Office 365 ProPlus and revising some announcements that were made in February. We are pleased to announce the following updates to our Office 365 ProPlus system requirements:
- Office 365 ProPlus will continue to be supported on Windows 8.1 through January 2023, which is the end of support date for Windows 8.1.
- Office 365 ProPlus will also continue to be supported on Windows Server 2016 until October 2025.
Office 2016 connectivity support for Office 365 services
In addition, we are modifying the Office 365 services system requirements related to service connectivity. In February, we announced that starting October 13, 2020, customers will need Office 365 ProPlus or Office 2019 clients in mainstream support to connect to Office 365 services.
To give you more time to transition fully to the cloud, we are now modifying that policy and will continue to support Office 2016 connections with the Office 365 services through October 2023.
Servicing and support flexibility
Longer Windows 10 servicing for enterprises and educational institutions
In April 2017, we aligned the Windows 10 and Office 365 ProPlus update cadence to a predictable semi-annual schedule, targeting September and March. While many customers—including Mars and Accenture—have shifted to a modern desktop and are using the semi-annual channel to take updates regularly with great success, we’ve also heard feedback from some of you that you need more time and flexibility in the Windows 10 update cycle.
Based on that feedback, we’re announcing four changes:
- All currently supported feature updates of Windows 10 Enterprise and Education editions (versions 1607, 1703, 1709, and 1803) will be supported for 30 months from their original release date. This will give customers on those versions more time for change management as they move to a faster update cycle.
- All future feature updates of Windows 10 Enterprise and Education editions with a targeted release month of September (starting with 1809) will be supported for 30 months from their release date. This will give customers with longer deployment cycles the time they need to plan, test, and deploy.
- All future feature updates of Windows 10 Enterprise and Education editions with a targeted release month of March (starting with 1903) will continue to be supported for 18 months from their release date. This maintains the semi-annual update cadence as our north star and retains the option for customers that want to update twice a year.
- All feature releases of Windows 10 Home, Windows 10 Pro, and Office 365 ProPlus will continue to be supported for 18 months (this applies to feature updates targeting both March and September).
In summary, our new modern desktop support policies—starting in September 2018—are:
Published: February 1, 2018
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 from ProPlus and Windows 10 together, we are making the following updates to the ProPlus system requirements for Windows:
- To clarify our current support practices for ProPlus running on Windows 10, ProPlus will not be supported on Windows 10 Semi-Annual Channel (SAC) versions that are no longer being serviced per the Windows 10 lifecycle. Office ProPlus will be supported on Windows 10 versions in active servicing and in servicing extensions as outlined here.
- Effective January 14, 2020, ProPlus will no longer be supported on the following versions of Windows and Windows Server—this will help customers get the best experience by receiving regular updates to both Windows and Office:
- Any Windows 10 Long-Term Servicing Channel (LTSC/LTSB) release
- Windows Server 2012, 2012 R2, and 2016
- Windows 8.1
Delivering Office 365 ProPlus remotely via Remote Desktop and Virtual Desktop Infrastructure (VDI) continues to be a key scenario for our customers. Microsoft is committed to enabling Office 365 Pro Plus in this scenario along with key Windows 10 experiences like Microsoft Edge, Store for Business, and Cortana. Later this year we will deliver these capabilities within the Semi-Annual Channel release cadence of Office, Windows 10, and Windows Server. Join the Windows Server Insider Program to get early access to these capabilities.
Go here to learn more.
We are moving to TLS 1.2 for encryption
Plan For Change
Veröffentlicht am : 10. Februar 2018
Aktion erforderlich von 31. Oktober 2018
As previously communicated in MC126199 in December of 2017, to provide best-in-class encryption, and to ensure our service is more secure by default, we are moving all of our online services to Transport Layer Security (TLS) 1.2+. In the two communications referenced above, we had indicated that we would be removing support for TLS versions less than 1.2 from our online services, beginning March 1, 2018. After receiving valuable feedback from administrators like you, we have decided to extend the deadline for upgrading to TLS 1.2 or later to October 31, 2018.
How does this affect me?
As of October 31, 2018, Microsoft Office 365 will no longer support TLS 1.0 and 1.1. By October 31, 2018, all client-server and browser-server combinations should use TLS version 1.2 (or a later version) to ensure connection without issues to Office 365 services. This may require updates to certain client-server and browser-server combinations. If you do not update to TLS version 1.2 (or later) by October 31, 2018, you may experience issues when connecting to Office 365. If you experience an issue related to the use of an old TLS version after October 31, 2018, you will be required to update to TLS 1.2 as part of the resolution.
What do I need to do to prepare for this change?
We recommend you proactively address weak TLS usage by removing TLS 1.0/1.1 dependencies in your environments and disabling TLS 1.0/1.1 at the operating system level where possible. Begin planning your migration to TLS 1.2+, today. Please click Additional Information to learn more.
Exchange Server TLS guidance, part 1: Getting Ready for TLS 1.2
Das Zertifikat zu meiner Ausbildung und Prüfung:
Fujitsu Advisory note: Intel vulnerabilities affecting selected PRIMERGY, PRIMEQUEST and Client Computing Devices
Intel has identified and made public today a new vulnerability affecting modern processor architectures. This new vulnerability is a derivative of the side-channel methods previously disclosed in January.
Please be aware that selected FUJITSU Server PRIMERGY/ PRIMEQUEST systems and CCD Products are affected by these vulnerabilities.
Fujitsu is working closely with Intel to address the issue through the release of software patches for all affected products that are currently supported. Older systems that are no longer supported will not be patched.
Fujitsu has published an advisory note on its support website which:
– Describes the vulnerability and the recommended steps as advised by Fujitsu to patch affected product lines
– Provides a list of affected systems and products here and patch availability. Fujitsu will update this list regularly.
Please advise customers with affected systems to follow these recommendations.
TPM Firmware Update Tool: https://sp.ts.fujitsu.com/dmsp/Publications/public/Infineon_TPM_Vulnerability_product-list.pdf
|Technical Background Information:
|The following TPM products in combination with the Firmware are affected:
|TPM1.2 – FW133.32, FW149.32 (SLB9645)
TPM1.2 – FW4.00 up to FW4.33 (SLB9655/9656)
TPM1.2 – FW4.40 up to FW4.42 (SLB9660)
TPM1.2 – FW6.00 up to FW6.42 (SLB9670)
TPM2.0 – FW 5.00 up to FW5.61 (SLB9665)
TPM2.0 – FW7.00 up to FW7.61 (SLB9670)
|How can I find out which TPM I am using?
|Fujitsu recommends using the Windows based tool (as mentioned above).:
|Alternatively, identify the TPM version by using the Trusted Platform Module Management on Local Computer (TPM Management Console).
|Access it by
- Clicking Start
- typing tpm.msc in the Search box
- then pressing “Enter
This displays the TPM manufacturer information.