Ticking the checkboxes in Scheduled Tasks for "Log in as" or "Run only
when logged in" or "Use maximum permissions" made no difference.
Ideas? Is this a WinPro7 v. 2000 security "feature" I'm running into?
I have run into this. I THINK that I was able to overcome it by
promoting the user for whom the task must run to local administrator,
then creating the scheduled task with maximum permissions on every
related damn thing I could find, and then demoting the user.
Not scientific, I know. And this is a vague memory of a problem I
dealt with something like three years ago, so take it for what it's
worth. But I did solve the problem, because the task, to pop-up a
message in the middle of the day, persisted in annoying this user for
quite some time until we finally disabled it.
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/45.E4.16480.CC061C85@cdptpa-omsmta02
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
