After my download solution annoyed me a few times, I outsourced the download. The new home for the downloads is GitHub. This also makes it easier for me to maintain and update.
Microsoft is changing its product life cycle for the Long Term Servicing Channel (LTSC) for Office and Windows. Some will still know the LTSC version as LTSB. Previously, this Windows 10 version, which was not intended for office environments, had a life cycle of 10 years. Microsoft Office LTSC, also known as Microsoft Office 2016 and Microsoft Office 2019) also had 10 years at the beginning, but this has already been reduced to 7 years with MS Office 2019
Often the question arises during a rollout: Is our Microsoft Office version still supported with Microsoft Windows 10? The first glance should always be at the current lifecycle of Microsoft Office. You can also find a nice overview in my article “Product Lifecycles – The Forgotten Being“. Depending on the remaining time of the life cycle of the Office program, a migration with Windows 10 can also be useful.
I am often asked about the right strategy for “Windows as a Service”. But is there the right way? The short answer is no. It depends as so often on the circumstances, the requirements of the customer and the other customer-specific circumstances. In this article, I would like to point out different ways to the subject of Windows as a Service (WaaS). You will also get tips on what to consider when searching for your way.
What is important is that Windows as a Service is not a project, it is a process. And the challenge is to develop the process for your company in such a way that it works performant but covers all contingencies. This doesn’t just include the question if you want to skip releases.