<?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: Print jobs sent from wrong user on Vista or Server 2008 computer</title>
	<atom:link href="http://neverblog.net/print-jobs-sent-from-wrong-user-on-vista-or-server-2008-computer/feed/" rel="self" type="application/rss+xml" />
	<link>http://neverblog.net/print-jobs-sent-from-wrong-user-on-vista-or-server-2008-computer/</link>
	<description>once more unto the breach...</description>
	<lastBuildDate>Tue, 24 Jan 2012 18:46:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rhett</title>
		<link>http://neverblog.net/print-jobs-sent-from-wrong-user-on-vista-or-server-2008-computer/comment-page-1/#comment-5772</link>
		<dc:creator>Rhett</dc:creator>
		<pubDate>Wed, 25 Feb 2009 12:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://neverblog.net/?p=572#comment-5772</guid>
		<description>Thanks for the post we are experiencing the same problem, and had yet to find the Microsoft page. Lucky we are in the testing phase of print accounting on our campus. We are implementing a scheduled task that will restart the spooler triggered by a user login on the Vista Workstations. Seems to working well in testing so far. </description>
		<content:encoded><![CDATA[<p>Thanks for the post we are experiencing the same problem, and had yet to find the Microsoft page. Lucky we are in the testing phase of print accounting on our campus. We are implementing a scheduled task that will restart the spooler triggered by a user login on the Vista Workstations. Seems to working well in testing so far.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
