<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A 123 to Securing PC&#8217;s</title>
	<atom:link href="http://churchtechmatters.com/2009/02/26/a-123-to-securing-pcs/feed/" rel="self" type="application/rss+xml" />
	<link>http://churchtechmatters.com/2009/02/26/a-123-to-securing-pcs/</link>
	<description></description>
	<lastBuildDate>Mon, 07 Nov 2011 22:44:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Stuart</title>
		<link>http://churchtechmatters.com/2009/02/26/a-123-to-securing-pcs/#comment-1209</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Sat, 21 Mar 2009 06:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1160#comment-1209</guid>
		<description>Thanks Emilio - the whether to let the user be an administrator or not argument is one that will continue to rage until MS sorts out their base security.

There is always going to be a balance for those of us not employed by the Church in how much lassitude we allow - after all, they aren&#039;t our computers and we are just serving!</description>
		<content:encoded><![CDATA[<p>Thanks Emilio &#8211; the whether to let the user be an administrator or not argument is one that will continue to rage until MS sorts out their base security.</p>
<p>There is always going to be a balance for those of us not employed by the Church in how much lassitude we allow &#8211; after all, they aren&#8217;t our computers and we are just serving!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A 123 to Securing PC’s &#124; Church Techy</title>
		<link>http://churchtechmatters.com/2009/02/26/a-123-to-securing-pcs/#comment-1208</link>
		<dc:creator>A 123 to Securing PC’s &#124; Church Techy</dc:creator>
		<pubDate>Sat, 21 Mar 2009 00:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1160#comment-1208</guid>
		<description>[...] first published this article over at ChurchTechMatters.com where I&#8217;m a guest writer in a fledgling enterprise to get a bunch of Christian Tech Heads [...] </description>
		<content:encoded><![CDATA[<p>[...] first published this article over at ChurchTechMatters.com where I&#8217;m a guest writer in a fledgling enterprise to get a bunch of Christian Tech Heads [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emilio Silvas</title>
		<link>http://churchtechmatters.com/2009/02/26/a-123-to-securing-pcs/#comment-1207</link>
		<dc:creator>Emilio Silvas</dc:creator>
		<pubDate>Wed, 18 Mar 2009 20:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1160#comment-1207</guid>
		<description>I have found that the biggest problem is that often the people who work in the church office are unaware of what it takes to secure their machine.  It is altogether too easy for them to download and install.  Sure, I could prevent them from logging in as an administrator, but that means I have to stop by and install it for them.  For churches that do not have a tech person on staff, the balancing act can be difficult.</description>
		<content:encoded><![CDATA[<p>I have found that the biggest problem is that often the people who work in the church office are unaware of what it takes to secure their machine.  It is altogether too easy for them to download and install.  Sure, I could prevent them from logging in as an administrator, but that means I have to stop by and install it for them.  For churches that do not have a tech person on staff, the balancing act can be difficult.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

