Scheduled macro not running when logged off, using autologon

[shackjohn]

I am using the Eval Macro Scheduler v8.1e (installed using an administrator account; purchase order is "in the pipe") running on Windows Server 2003 Enterprise Edition, SP1, and am unable to run a scheduled macro when I am logged off. I am using an administrator account. Scheduling a macro to run while the administrator account is logged on works correctly.

I have tried the following AutoLogon scenarios:
1. Nothing checked.
2. "When Started...Run as User..." set to use the administrator account and "Unlock Computer..." UNchecked.
3. Checked "Unlock Computer..." and "When Started...Run as User..." checked.
4 Checked "Unlock Computer..." but with "When Started...Run as User..." UNchecked.

Logging is turned on but nothing is being generated. "Allow Scheduler Service to run this macro" is checked. The server is running in a secure environment, behind a firewall, so accessing it is not possible.

The most perplexing thing is that I am using the debug version of autologonsvc.exe but no 'c:\autologonsvc.log' file is being created.

Now, the machine contains an operating system from a disk predined by our customer, and, of course, includes their own Local Security settings, etc. So, one of my theories is that there is a conflict of some kind between Macro Scheduler and one or more of the policy settings.


'schedtest' Macro:

Code: Select all

Let>RP_WAIT=2
Wait>20
TimeStamp>C:\macschedtest_doesnothing.txt,schedtest starting...
Run Program>C:\macschedtest_doesnothing.bat
TimeStamp>C:\macschedtest_doesnothing.txt,schedtest finished.
Wait>60

'C:\macschedtest_doesnothing.bat' file:

Code: Select all

REM  This bat file is only for testing scheduling a Macro Scheduler macro.
echo Testing scheduling a Macro Scheduler in logoff mode.

Thanks for taking the time to read this,
John

[Marcus Tettmar]

Now, the machine contains an operating system from a disk predined by our customer, and, of course, includes their own Local Security settings, etc. So, one of my theories is that there is a conflict of some kind between Macro Scheduler and one or more of the policy settings.

That sounds the most likely explanation. Do you have another machine, with a regular, vanilla, OS install which you can test on?