<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/">  <title>WebJunction - Public Access Computing</title>  <link href="http://www.webjunction.org/public-access" />  <link rel="self" href="http://www.webjunction.org/public-access/resources/rss" />  <subtitle>Articles and Discussions</subtitle>  <id>http://www.webjunction.org/public-access</id>  <updated>2010-06-07T16:01:57Z</updated>  <dc:date>2010-06-07T16:01:57Z</dc:date>  <entry>    <title>Full circle - a PAC story</title>    <link rel="alternate" href="http://www.webjunction.org/public-access/-/articles/content/98846742" />    <author>      <name>Nate Erb</name>    </author>    <id>http://www.webjunction.org/public-access/-/articles/content/98846742</id>    <updated>2010-06-07T16:01:57Z</updated>    <summary type="html">Our village library&amp;#039;s journey in PAC, from desktops to thin&amp;#045;client and now to nettop computers.&lt;br&gt;&lt;p&gt;In&amp;nbsp;2007 I operated a Windows hosting business in Milwaukee, Wisconsin.&amp;nbsp; One day I got a call from one of our vendors who sold &amp;ldquo;thin clients&amp;rdquo;.&amp;nbsp; Thin clients are simple computers designed to lower maintenance costs, exposure to viruses, and lower power usage.&amp;nbsp; Waterford Public Library had bought about a dozen thin-client computers from them to use as public access terminals and were having problems with the implementation.&amp;nbsp; These machines were replacing an older network of traditional PC's.&lt;/p&gt;&lt;p&gt;It's widely known that public access computing is an entirely different game than standard home or business computing. &amp;nbsp;Frankly, it must be assumed that your users are going to cause problems on the machine; either by virus infection, changing a software option,&amp;nbsp;outright vandalism, or most likely - from lack of knowledge.&amp;nbsp; A public access machine must be locked down in a number of ways to protect the library from maintenance costs and downtime, but still be usable to the patron without encumbrances.&lt;/p&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;Slowly but surely we were able to make the thin clients work for public access. &amp;nbsp;We installed Internet Explorer as well as Firefox to give users a choice in web browsers.&amp;nbsp; Since the thin clients had limited on board storage, we installed Microsoft Office on a Windows Terminal Server and deployed it to the workstations remotely.&amp;nbsp; Users log in with a simple USB stick that is assigned to their workstation &amp;ndash; this prevents unauthorized access and makes sure users properly log off when finished in order to delete their surfing history and cookies.&amp;nbsp; Printing is handled at the Information Desk, with users paying for their print jobs at pickup.&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;&amp;nbsp;&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;For the past two years these thin clients have served&amp;nbsp;our patrons well, but we have learned quite a few things.&amp;nbsp; Thin clients, while good at stopping threats like viruses and vandalism, are really not that easy to maintain.&amp;nbsp; Software updates have to come from the manufacturer &amp;ndash; not from Microsoft &amp;ndash; due to the proprietary nature of a thin client.&amp;nbsp; Our thin clients used a Compact Flash based hard disk; these perform much slower than regular drives and deteriorate with age making them even slower.&amp;nbsp; We found as time went on, we were having more and more problems keeping the machines running and up to date, and users were also reporting poor performance.&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;&amp;nbsp;&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;The emergence of &amp;ldquo;net-top&amp;rdquo; computers (sub $350 laptops and desktops) over the past year has changed our course.&amp;nbsp; These computers have many of the benefits of a thin client such as a small footprint and lower power usage, but are standard PCs with a regular hard disk and a faster CPU. &amp;nbsp;They can be locked down just as a thin client with Windows SteadyState, a free Microsoft utility developed for libraries.&amp;nbsp; We designed an easy to use Windows Desktop with large icons and descriptions to assist users.&amp;nbsp; We also ported our USB login system over to this platform, and developed a remote maintenance system to administer it.&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;&amp;nbsp;&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;Like anything in technology, public access computing is always a challenge and a learning process.&amp;nbsp; From desktop PC's, to thin-clients, now returning to net-top PC's we have come full circle and so far, users are reporting good things about the&amp;nbsp;net-tops&amp;nbsp;and prefer it to our older thin client workstations.&amp;nbsp; With cost-effective hardware like net-tops, and well established administration software like Windows SteadyState, you can put together a powerful public access workstation for your users, with little hassle&amp;nbsp;for your staff.&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;&amp;nbsp;&lt;/div&gt;&lt;div align="left" style="text-align: left; text-indent: 0in; margin: 0in 0in 0pt;"&gt;Nate Erb&lt;br /&gt;owlsurf.com / Waterford Public Library volunteer&lt;/div&gt;</summary>    <dc:creator>Nate Erb</dc:creator>  </entry></feed>
