Something seems to have gone horribly wrong in an untold number of IT departments on Wednesday after Microsoft installed a resource-hogging search application on machines company-wide, even though administrators had configured systems not to use the program.Meanwhile, the Fox Bidness Journal readers speak:
"The admins at my place were in a flap this morning because Windows Desktop Search 3.01 had suddenly started installing itself on desktops throughout the company," a Reg reader by the name of Rob informs us. "The trouble is that once installed, the indexer kicks in and slows the machines down."
The blogosphere is buzzing with similar reports, as evidenced by postings here (http://sadjadbp.spaces.live.com/blog/cns!21F12BB61B822DFA!263.entry), here (http://dblume.livejournal.com/78836.html) and here (http://www.davidarno.org/2007/10/24/microsoft-update-strikes-again/).
"I'm slighly pissed of [sic] at M$ right now," an admin in charge of 3,000 PCs wrote in a comment to the first aforementioned link. "All the clients have slowed to a crawl, and the file servers are having problems with the load."
According to Reg tipster Rob, Windows Server Update Services (http://technet.microsoft.com/en-us/wsus/default.aspx) (WSUS) forced Windows Desktop Services (WDS) 3.01 on the fleet of machines even though admins had configured their system to install updates only for existing programs and the search program wasn't installed on any machines (well, until then, anyway).
It's been a rough several weeks for managers running Microsoft's auto update services. Last month, bloggers disclosed the existence of a Windows patch that silently and automatically installed itself (http://www.theregister.com/2007/09/14/microsoft_dispels_stealth_update_rumors/) even on Machines configured not to install updates. Critics cried foul on the principle that users should have absolute control over their machines. They also argued that the stealth update could hamper compliance requirements.
The revelation that Microsoft is pushing yet more installations not explicitly agreed to by administrators is not likely to sit well with this same vocal contingent. Redmond may want to don the asbestos suits now.
Friday, October 26, 2007
Today's Micro$oft Bashing
From my beloved, The Register: