Choosing the right edition of Windows 10 can sometimes be harder than you think for companies. For most companies, the cost versus functionality is a consideration. But which versions are there? More than one actually thinks:
Unattended software installation is standard in many environments. But how does it work? With an MSI it’s easy, but not everything is available as an MSI package. But many applications bring their own methods. Since I often need this, here is a small collection for the more important programs.
Some questions now, if I was already using the Microsoft Deployment Toolkit (MDT), why should I run Autopilot afterwards? There are several reasons why it can be useful, here are some examples:
Microsoft uses GUIDs in the error messages for the GPO Client Side Extension (CSE). If you have to analyze group policies regularly and find the errors, you might want to have a list. Since it works the same way for me, I started to collect. Here is my current status, I hope it helps you.
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.
There are many strategies, approaches and opinions about Windows as a Service. Today I would like to take a closer look at the possibilities. There is the classical and the modern approach, which one can go. But sometimes you still have to use parts of the classical methods.
Let’s take a look at how an operating system migration was carried out in the past. For us, the most important thing is the successful creation of the client build, not the subsequent deployment.
Microsoft is changing its upgrade strategy, this change affects the semi-annual feature upgrades. The first steps in this direction have already been a bit earlier, in 2018 Microsoft has announced the fall release to provide 30 months of support. This also makes sense under the new strategy.
Along with the further step, elimination of the “Semi-Annual Channel-Targeted (SAC-T)”. The “Semi-Annual Channel (SAC)” and the “Semi-Annual Channel-Targeted (SAC-T)” had inherited the two branches “Current Branch (CB)” and the “Current Branch for Business (CCB)” and were their replacements.