This is because the scheduler service logs on as the local SYSTEM account, and
this account has no environment so any of your environment variable settings
(including PATH) will have no effect. One way around this is to change the
account which logs on the service to be something other than SYSTEM
(Administrator would be a good choice) that has the needed environment
variables defined. This can be done via the Services Control Panel applet
(under Services icon in the Control Panel folder) under Startup options for the
install ADSM scheduler service.  Another approach would be to make sure the
command which the scheduler executes is a fully qualified path and to also make
sure that it doesn't rely on any environment variables (I'm not sure it the
note agent does).

Hope this helps ....

Pete Tanenhaus
ADSM NT Client Development