We are using windows AT jobs to schedule execution of scripts on client systems. These execute as the SYSTEM account. Our goal right now is to try to get the Filer to confirm to the behavior of a Windows file server, while avoiding changing the client's method.
Kevin M. Parker wrote:
Why use the Windows "system" account? If it's a script/process, make it run as an A.D. service account and give permissions on the storage system to that service account. Then you won't have to worry about null user support.
Your co-worker needs to be subscribed to the alias (toasters.mathworks.com/toasters/Explanation.html) and also send emails to the alias as "from" that subscribed user. At least that "could" be the issue.
Kevin Parker 919.521.8413 http://theparkerz.com-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Adam McDougall Sent: Wednesday, November 19, 2008 2:08 PM To: Toasters Subject: [Fwd: Re: Windows SYSTEM account paired with DNS alias results in NULL user authentication attempts.]
Forwarding on behalf of a co-worker who can't seem to post.