The Automation Edition includes an NT service module that allows critical system functions to be performed even when no one is logged on, ideal for such things as unattended backups.
If tasks execute correctly when started from the List of Scheduled Tasks windows but fail when started as scheduled from the service, this usually indicates that the service does not have the same access rights as the user interacting with the UI.
By default, the NT service is logged on using the local system account. This is very secure, and allows launched applications to be interactive, but one limitation of this account is that it does not have access to network resources. If you need to run programs that require network resources, and cannot connect to those resources by themselves, you should change the service logon information (Windows NT Control Panel->Services, select Schedule Wizard), use a script action to specify a user/password combination for an application being run, or use the ExecuteAs utility (see below). If you use a users account for the service rather than a local system account, however, be warned that Windows NT does not allow the service or launched applications to interact with the desktop. This means you will not see messages, or launched applications. Consult your Windows NT Administrator or documentation for more information on changing the service logon settings.
What is the ExecuteAs utility?
By default, applications launched by the Schedule Wizard service module will inherit the security settings of the service module. The ExecuteAs utility has been included so that you may start an application with the privileges of a particular user.
Ive changed the account, and my CMD file still does not work what else could be wrong?
You may need to add a statement to the start of your CMD file similar to:
net use g: \myserver\files
Im connecting to a Novell server what else could be wrong?
Joe M. gave us the following solution:
I am using Schedule Wizard Automation Edition (with the NT Service module activated) to copy files from an NT server to a Novell server. I had a drive mapped to the Novell server and created a batch file to copy the files every night.
SW would work fine when I used Execute/Test but not when I scheduled it. I visited your site and made the changes to the SW Service that were recommended. After several days of frustration, I suspected that it could be that the SW service was not authorized access to the Novell server even though the service was using the Administrator ID used for both servers. To test the wizard, I tried setting SW to copy files from one folder on the NT server to another folder on the NT server and that worked fine.
What I finally ended up doing was setting up Netware Gateway Services on the NT server. It was either that or setting up a Novell client for NT.
Now that everything is working fine, I'd like to compliment your product on its simplicity. It does what I need it to do and that will save me many hours of work.