<?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: Non admin users running scheduled batch tasks</title>
	<atom:link href="http://www.jpuddy.net/2008/05/05/non-admin-users-and-scheduled-tasks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jpuddy.net/2008/05/05/non-admin-users-and-scheduled-tasks/</link>
	<description>Home of DJ and technophile Jonathan Puddle (aka DJ J Puddy)</description>
	<pubDate>Mon, 13 Oct 2008 02:44:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Non admin users running scheduled batch tasks</title>
		<link>http://www.jpuddy.net/2008/05/05/non-admin-users-and-scheduled-tasks/#comment-3793</link>
		<dc:creator>Non admin users running scheduled batch tasks</dc:creator>
		<pubDate>Mon, 05 May 2008 12:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.jpuddy.net/?p=564#comment-3793</guid>
		<description>[...] Ben Stone Online wrote an interesting post today onHere&#8217;s a quick excerpt I ran into a problem a few months back where I found non-admin users on Windows Server 2003 couldn’t run batch files in scheduled tasks. I just gave up then as it wasn’t important, but I had to find a solution for the same issue today. Didn’t have to look far, it turned out: SYMPTOMS When you run a batch job that runs under the context of a regular user account on a Microsoft Windows Server 2003-based computer, the script may not run. If you run the batch job by using the Scheduled Tasks feat [...]</description>
		<content:encoded><![CDATA[<p>[...] Ben Stone Online wrote an interesting post today onHere&#8217;s a quick excerpt I ran into a problem a few months back where I found non-admin users on Windows Server 2003 couldn’t run batch files in scheduled tasks. I just gave up then as it wasn’t important, but I had to find a solution for the same issue today. Didn’t have to look far, it turned out: SYMPTOMS When you run a batch job that runs under the context of a regular user account on a Microsoft Windows Server 2003-based computer, the script may not run. If you run the batch job by using the Scheduled Tasks feat [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
