<?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: The Next Wave in Personal meeting Business Computing</title>
	<atom:link href="http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/feed/" rel="self" type="application/rss+xml" />
	<link>http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/</link>
	<description>The essence of getting it right</description>
	<lastBuildDate>Sun, 08 Aug 2010 06:10:57 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Justin Davies</title>
		<link>http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/comment-page-1/#comment-671</link>
		<dc:creator>Justin Davies</dc:creator>
		<pubDate>Thu, 04 Oct 2007 07:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/#comment-671</guid>
		<description>Thanks Todd, great response. 

One of the things that we find often in our consulting projects is that supplier provides - or that the personal machine just doesn&#039;t connect to the network physically - ie there is internet access only.

With so many devices able to hold a lot of data, USB  and other data take off devices are another whole area of challenge to be reconciled....

More fun to come!

Justin</description>
		<content:encoded><![CDATA[<p>Thanks Todd, great response. </p>
<p>One of the things that we find often in our consulting projects is that supplier provides &#8211; or that the personal machine just doesn&#8217;t connect to the network physically &#8211; ie there is internet access only.</p>
<p>With so many devices able to hold a lot of data, USB  and other data take off devices are another whole area of challenge to be reconciled&#8230;.</p>
<p>More fun to come!</p>
<p>Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Davies</title>
		<link>http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/comment-page-1/#comment-654</link>
		<dc:creator>Todd Davies</dc:creator>
		<pubDate>Wed, 03 Oct 2007 03:32:44 +0000</pubDate>
		<guid isPermaLink="false">http://justindavies.com.au/2007/08/28/the-next-wave-in-personal-meeting-business-computing/#comment-654</guid>
		<description>The big issue in my experience is not with technical solutions, but with employee expectations and clear definition of responsibilities between the employer and the employee.  

Let&#039;s take the assumption that an enterprise security environment is only as strong as it&#039;s weakest link, then you end up with wanting to install a minimum security baseline.  This then leads you down the path of SOE, standard security settings, virus software, O/S, security and software updates etc.

This is where the greyness starts - if the employer insists on a MSB, then who pays for the licenses? who monitors compliance with license terms?  Who monitors that the MSB is actually in place?  What if their machine is out of date and can&#039;t handle the SOE?  Who maintains and pays for the internet connection?  If it&#039;s the company&#039;s connection does this mean that the user&#039;s kids can&#039;t play on the machine for fear of breaching the company&#039;s acceptable use policy?  What happens with P2P if it&#039;s on a work connection? 

These issues are all very real and in practice, the simplest solution seems to be not to go there, which is possibly okay in the short term, but in an interconnected world this is not going to be a practical or cost-effective solution in the medium term and hence things will need to move forward.

My guess is that starting with an appropriate agreement which combines employment law and SLA-speak would be the starting point, combined with some thorough risk and technical analysis of what&#039;s possible, and what downside needs to be managed.</description>
		<content:encoded><![CDATA[<p>The big issue in my experience is not with technical solutions, but with employee expectations and clear definition of responsibilities between the employer and the employee.  </p>
<p>Let&#8217;s take the assumption that an enterprise security environment is only as strong as it&#8217;s weakest link, then you end up with wanting to install a minimum security baseline.  This then leads you down the path of SOE, standard security settings, virus software, O/S, security and software updates etc.</p>
<p>This is where the greyness starts &#8211; if the employer insists on a MSB, then who pays for the licenses? who monitors compliance with license terms?  Who monitors that the MSB is actually in place?  What if their machine is out of date and can&#8217;t handle the SOE?  Who maintains and pays for the internet connection?  If it&#8217;s the company&#8217;s connection does this mean that the user&#8217;s kids can&#8217;t play on the machine for fear of breaching the company&#8217;s acceptable use policy?  What happens with P2P if it&#8217;s on a work connection? </p>
<p>These issues are all very real and in practice, the simplest solution seems to be not to go there, which is possibly okay in the short term, but in an interconnected world this is not going to be a practical or cost-effective solution in the medium term and hence things will need to move forward.</p>
<p>My guess is that starting with an appropriate agreement which combines employment law and SLA-speak would be the starting point, combined with some thorough risk and technical analysis of what&#8217;s possible, and what downside needs to be managed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
