W
Will Manley
Hi All,
Windows Server PRIOR to 2016 has been rock solid with a good method of providing updates and making it extremely serviceable. Bundling updates into one big patch is not the answer and can lead to long wait and resolution times. Microsoft need to go back to individual updates based on this issue I am now having as an example. Doing updates in smaller chunks and greater frequencies are more manageable than one bigger patch. Having to wait longer for a fix because it is in a bulk release of fixes provides a greater chance of other issues being created from the one patch. It can cause required fixes to have to be rolled back out because of the requirement to accept all fixes in that one patch or build.
I have just purchased 6 servers and have had my first exposure to Windows 2016 1607. With the latest build it is clear that this is an untested released product where the end-user is the tester for Microsoft. The company I work for has just spent $700K on hardware and licensees but we cannot deploy these due to Windows 2016 and the fact the all releases are far back as March 2018 that we have tested do not work.
The two issues which are of major concern are:-
And the numerous other fixes, such as the data sharing service you have to apply and other tweaks because they cannot be bothered sorting them out in the latest patches.
I am unable to isolate the fault to a particular fix now because I cannot simply uninstall one fix.
Come on Microsoft I've worked with your server line for many years and this is the worst I've ever seen it. Microsoft are treating this like a glorified desktop system that you just upgrade when you feel like it. There should only be 1607 and non of the other branches as it makes no sense for a server line.
It shows a clear misunderstanding of how servers are purchased and how they are allocated for use. They are not something enterprise re-purpose at a whim.
The server community need core issues fixing quickly and the bundled patching is just a joke.
I've raised this with Microsoft Support to get this fixed.
For the first time I am one unhappy Windows Server administrator and I've been doing this since NT 3.51
Continue reading...
Windows Server PRIOR to 2016 has been rock solid with a good method of providing updates and making it extremely serviceable. Bundling updates into one big patch is not the answer and can lead to long wait and resolution times. Microsoft need to go back to individual updates based on this issue I am now having as an example. Doing updates in smaller chunks and greater frequencies are more manageable than one bigger patch. Having to wait longer for a fix because it is in a bulk release of fixes provides a greater chance of other issues being created from the one patch. It can cause required fixes to have to be rolled back out because of the requirement to accept all fixes in that one patch or build.
I have just purchased 6 servers and have had my first exposure to Windows 2016 1607. With the latest build it is clear that this is an untested released product where the end-user is the tester for Microsoft. The company I work for has just spent $700K on hardware and licensees but we cannot deploy these due to Windows 2016 and the fact the all releases are far back as March 2018 that we have tested do not work.
The two issues which are of major concern are:-
- SFC /scannow never finishes with a successful message. The CBS log is full of issues and this is from a clean build of Windows and their latest patch KB4343887.
- Windows Server Backup does not work to a network drive anymore.
And the numerous other fixes, such as the data sharing service you have to apply and other tweaks because they cannot be bothered sorting them out in the latest patches.
I am unable to isolate the fault to a particular fix now because I cannot simply uninstall one fix.
Come on Microsoft I've worked with your server line for many years and this is the worst I've ever seen it. Microsoft are treating this like a glorified desktop system that you just upgrade when you feel like it. There should only be 1607 and non of the other branches as it makes no sense for a server line.
It shows a clear misunderstanding of how servers are purchased and how they are allocated for use. They are not something enterprise re-purpose at a whim.
The server community need core issues fixing quickly and the bundled patching is just a joke.
I've raised this with Microsoft Support to get this fixed.
For the first time I am one unhappy Windows Server administrator and I've been doing this since NT 3.51
Continue reading...