<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Please don&#8217;t install that</title>
	<atom:link href="http://ihatemyitguy.com/2008/04/29/please-dont-install-that/feed/" rel="self" type="application/rss+xml" />
	<link>http://ihatemyitguy.com/2008/04/29/please-dont-install-that/</link>
	<description>making IT more human</description>
	<pubDate>Tue, 06 Jan 2009 04:49:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Matt</title>
		<link>http://ihatemyitguy.com/2008/04/29/please-dont-install-that/#comment-17</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 09 May 2008 18:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://ihatemyitguy.com/?p=16#comment-17</guid>
		<description>Wading into this argument as an IT guy who was formerly responsible for deploying Microsoft's updates, I can say that I've only had 1 update "break" a machine.  And this was out of over 300 updates that we deployed while I was at this job.  That's a 99.6% success rate.  Most every time there was some problem on someone's machine though, the question came up "What update did you push out."  It generally took me about 5 minutes of troubleshooting to determine the actual cause of a problem, typically user error or software misconfiguration.  The bottom line is, the IT guy is right in this argument.  Typically software updates are deployed during the night, at a time that causes the LEAST amount of trouble for people.  What we can't do is keep 100% of users happy 100% of the time.  I'm sorry you had to reboot your computer to install a patch I deployed, but this is not only to protect your computer, it's to protect the REST of my entire network.  Now put on your big boy pants and deal.</description>
		<content:encoded><![CDATA[<p>Wading into this argument as an IT guy who was formerly responsible for deploying Microsoft&#8217;s updates, I can say that I&#8217;ve only had 1 update &#8220;break&#8221; a machine.  And this was out of over 300 updates that we deployed while I was at this job.  That&#8217;s a 99.6% success rate.  Most every time there was some problem on someone&#8217;s machine though, the question came up &#8220;What update did you push out.&#8221;  It generally took me about 5 minutes of troubleshooting to determine the actual cause of a problem, typically user error or software misconfiguration.  The bottom line is, the IT guy is right in this argument.  Typically software updates are deployed during the night, at a time that causes the LEAST amount of trouble for people.  What we can&#8217;t do is keep 100% of users happy 100% of the time.  I&#8217;m sorry you had to reboot your computer to install a patch I deployed, but this is not only to protect your computer, it&#8217;s to protect the REST of my entire network.  Now put on your big boy pants and deal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Ramirez</title>
		<link>http://ihatemyitguy.com/2008/04/29/please-dont-install-that/#comment-16</link>
		<dc:creator>Andy Ramirez</dc:creator>
		<pubDate>Wed, 30 Apr 2008 19:51:15 +0000</pubDate>
		<guid isPermaLink="false">http://ihatemyitguy.com/?p=16#comment-16</guid>
		<description>I'll start testing every update the day my users realize that company emails cannot be used for trolling personal websites, having virtual sex via dirty emails or that it's not o.k. to install Dora The Explora Six on their company laptops. 

I realize that no company system is going to be 100% for company use, I don't pretend to do that on my office computers (which by the way are just as much company property as the users') but for the love of Pete, just because the company buys you a laptop does not mean you can throw away the old clunker at home and hand your work computer off to your kids every time you come home.

And on that note I have one blanket statement: UNLESS YOU WORK FOR THE COMPANY THAT DEVELOPED LIMEWIRE THERE IS NEVER A REASON TO HAVE IT ON YOUR SYSTEM, I DON'T CARE IF YOU DO HAVE LIMEWIRE LIGHT.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll start testing every update the day my users realize that company emails cannot be used for trolling personal websites, having virtual sex via dirty emails or that it&#8217;s not o.k. to install Dora The Explora Six on their company laptops. </p>
<p>I realize that no company system is going to be 100% for company use, I don&#8217;t pretend to do that on my office computers (which by the way are just as much company property as the users&#8217;) but for the love of Pete, just because the company buys you a laptop does not mean you can throw away the old clunker at home and hand your work computer off to your kids every time you come home.</p>
<p>And on that note I have one blanket statement: UNLESS YOU WORK FOR THE COMPANY THAT DEVELOPED LIMEWIRE THERE IS NEVER A REASON TO HAVE IT ON YOUR SYSTEM, I DON&#8217;T CARE IF YOU DO HAVE LIMEWIRE LIGHT.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
