M
MartinKimzey
The 1803 update required a time consuming and expensive recovery effort for many clients. Support from Microsoft was in the form of a Hodge-podge of articles and support forum suggestions of different things to try. There is no solid and reliable info coming from Microsoft (or anyone).
Defensive posts touting the high level of expertise of Microsoft Engineers do not provide useful answers.
This update has seriously shaken confidence in Microsoft. It has people asking questions such as:
Will Microsoft blow this off or make real changes? I must tell you, from the responses I have seen, I believe Microsoft will blow this off.
Organizations and individuals run their lives on Windows. Some ethical oversight is badly needed.
Continue reading...
Defensive posts touting the high level of expertise of Microsoft Engineers do not provide useful answers.
This update has seriously shaken confidence in Microsoft. It has people asking questions such as:
- What would it take to move to iOS and Linux?
- How many hours did each employee spend recovering from 1803?
- What are the impacts and delays on each project?
- If this is the way Microsoft operates, what can we do to lessen the impact of the next update?
- How long will it take IT to disable Windows Updates on each and every PC in our organization?
- How many FTEs are required to vet updates from Microsoft?
- We need a new process to determine if future updates are safe or not.
- We will need some PCs running our gold image - sufficiently fire-walled from our working network to evaluate Microsoft updates.
Will Microsoft blow this off or make real changes? I must tell you, from the responses I have seen, I believe Microsoft will blow this off.
Organizations and individuals run their lives on Windows. Some ethical oversight is badly needed.
Continue reading...