New
#100
I'm all for more screwups from MSFT like yesterdays![]()
Yesterday of average admin:
- 50+ calls and mails of affected users from early morning
- investigating what is going on
- testing in VM
- searching the web for further info
- communicating with management
- composing apologetic message to all employees
- replying to questions when it will be ok
- trying & waiting for resolution
All done for reason of incompetence of someone else.... Nobody expects the final statement instantly but short official explanation & apology is needed in this situation.
Little explanation: once activated Win10 system remains in this state at least six months after activation (for example, if it has no access to activation servers). So the problem was wrong function of activation servers, not their inaccessibility. Under these circumstances, the first thing necessary to do is disabling malfunctioning service which harms other systems. But MS continued to de-activate PCs of customers all the day... Unbelievable.
Within a couple of hours an emerging issue statement was issued. It was middle of night, Redmond time! Your expectations are rather unrealistic. The issue was fixed before they probably had time to issue a formal statement. Corporate inertia is always pretty slow in any large organisation. It takes time to get statements approved. Best we get usually is vague twitter responses.
I've been looking at this along the same line...
This has not been a server reliability issue, it's been a server configuration issue that had not been properly tested prior to rolling it out to production.
This just shows that the Q&A, or lack of, doesn't only impact Windows feature updates. The very same lackadaisical Q&A process is in place for the internal MS servers as well.
My faith in MS has been shakened lately. It's like they have students working on programming for Windows 10.