Re: Logon Script Not Running

Startup script runs in context equivalent to admin.
You should not enable limited users to schedule tasks
as it would allow them a route to elevate their status.

<v8killah03@xxxxxxxxx> wrote in message
news:1156766529.928005.198460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hmm, that could be it. They are a restricted user. Would this prevent
the running of scheduled tasks? If so, how could I work around this?
Would having a startup script instead of a logon script resolve this?

Thanks,
James



.

Relevant Pages

  • Re: Making Route Delete Persistent
    ... If you are able to run "route delete" on the machine to delete the route ... you may consider using a startup script to allow the machine run ... Refer to the following article to assign the bat file as ... run the bat file to delete the route entry. ...
    (microsoft.public.windows.server.networking)
  • Re: more networking setup
    ... > dug thru some books about setting ip_forwarding and the commands given did ... > as i looked at the startup script and some other docs i find some criteria ... > there is dhcp present then its automatically disabled. ... set a route, or just try setting a route to the interface with a ...
    (comp.unix.solaris)
  • in.routed - mystery route added
    ... It's not in any startup script, so I'm thinking pehaps that in.routed has ... default route is defined in an /etc/rc2.d/ startup script. ... How could I confirm that this is a RIP route and not a static route? ... sockaddrs: ...
    (SunManagers)
  • Re: Add user/group to local group via Group Policy
    ... loggon/loggoff script is the route i choose and it is working perffectly. ... Make it a startup script instead. ... If a non-administrator logs in, ...
    (microsoft.public.windows.group_policy)