Well depending on how your smtp/exchange server is setup it requires domain
authentication. Instead of running as system through a schedule task set it
up to run as a domain user.

"tonyr" wrote:

> I have the following single line script running from a w2k3 server
> Send-SmtpMail -SmtpHost a.b.com -To dope@b.com -From dope@b.com
> -subject "tm down"
>
> if I run it as a user it works fine if I try to run it as a scheduled tasks
> as "system" nothing happens!
>
> any ideas?
> thanks
> tr
>

yea unfortuantely this particular smtp server does not require
authentication! So I'm still stumped..
thanks
tr


"J Ford" wrote:

> Well depending on how your smtp/exchange server is setup it requires domain
> authentication. Instead of running as system through a schedule task set it
> up to run as a domain user.
>
> "tonyr" wrote:
>
> > I have the following single line script running from a w2k3 server
> > Send-SmtpMail -SmtpHost a.b.com -To dope@b.com -From dope@b.com
> > -subject "tm down"
> >
> > if I run it as a user it works fine if I try to run it as a scheduled tasks
> > as "system" nothing happens!
> >
> > any ideas?
> > thanks
> > tr
> >

tonyr wrote:
> yea unfortuantely this particular smtp server does not require
> authentication! So I'm still stumped..
> thanks
> tr
>
>
> "J Ford" wrote:
>
>> Well depending on how your smtp/exchange server is setup it requires domain
>> authentication. Instead of running as system through a schedule task set it
>> up to run as a domain user.
>>
>> "tonyr" wrote:
>>
>>> I have the following single line script running from a w2k3 server
>>> Send-SmtpMail -SmtpHost a.b.com -To dope@b.com -From dope@b.com
>>> -subject "tm down"
>>>
>>> if I run it as a user it works fine if I try to run it as a scheduled tasks
>>> as "system" nothing happens!
>>>
>>> any ideas?
>>> thanks
>>> tr
>>>

Isn't the local system account restricted from accessing the network?

\\uSlacker

yep knew that forgot that thanks for reminding me again!!
tr

"uSlacker" wrote:

> tonyr wrote:
> > yea unfortuantely this particular smtp server does not require
> > authentication! So I'm still stumped..
> > thanks
> > tr
> >
> >
> > "J Ford" wrote:
> >
> >> Well depending on how your smtp/exchange server is setup it requires domain
> >> authentication. Instead of running as system through a schedule task set it
> >> up to run as a domain user.
> >>
> >> "tonyr" wrote:
> >>
> >>> I have the following single line script running from a w2k3 server
> >>> Send-SmtpMail -SmtpHost a.b.com -To dope@b.com -From dope@b.com
> >>> -subject "tm down"
> >>>
> >>> if I run it as a user it works fine if I try to run it as a scheduled tasks
> >>> as "system" nothing happens!
> >>>
> >>> any ideas?
> >>> thanks
> >>> tr
> >>>
>
> Isn't the local system account restricted from accessing the network?
>
> \\uSlacker
>

ah crap thought I new that, but i fixed the powershell issue and now the
command runs fine as "system".

"tonyr" wrote:

>
> yep knew that forgot that thanks for reminding me again!!
> tr
>
> "uSlacker" wrote:
>
> > tonyr wrote:
> > > yea unfortuantely this particular smtp server does not require
> > > authentication! So I'm still stumped..
> > > thanks
> > > tr
> > >
> > >
> > > "J Ford" wrote:
> > >
> > >> Well depending on how your smtp/exchange server is setup it requires domain
> > >> authentication. Instead of running as system through a schedule task set it
> > >> up to run as a domain user.
> > >>
> > >> "tonyr" wrote:
> > >>
> > >>> I have the following single line script running from a w2k3 server
> > >>> Send-SmtpMail -SmtpHost a.b.com -To dope@b.com -From dope@b.com
> > >>> -subject "tm down"
> > >>>
> > >>> if I run it as a user it works fine if I try to run it as a scheduled tasks
> > >>> as "system" nothing happens!
> > >>>
> > >>> any ideas?
> > >>> thanks
> > >>> tr
> > >>>
> >
> > Isn't the local system account restricted from accessing the network?
> >
> > \\uSlacker
> >