Malcolm Greene wrote: > +1. I have the same thing happen to me. EXTREMELY frustrating.
If you want to get around vendor maliciousness or incompetence like this, here's what you do: 1) Get your system updated to the service pack/patch level you are comfortable with. Only update to the latest *if you've tested it* in your environment. 2) Turn automatic updates off 3) Disable the security center so users don't get nagged uselessly. Now (and this is critical). Never update that system again, unless it becomes necessary to do so. Once the system is in a known good state, don't EVER update it again until it is time to, say, upgrade the hardware. Simple. You have a known system setup, and you aren't going to be woken up at 4am when that early employee calls you because something Windows Update did screwed up something the user needs to do. Put the system behind a smart firewall, turn windows firewall on if you like, and virus/spyware scan the system at off-hours (don't run this stuff in the background: it isn't very effective and it hogs valuable system resources). There. Multiple problems with Windows OS solved. Translates to happy users, translates to you keeping your job as sysadmin. Oh, and for testing updates/patches before rolling them out: use a virtual machine that can take a snapshot and roll back to prior save points. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
