I checked the results of the localsch /tasks and both the working and non-working PC's are the same.
My LocalSch.log files differ only in that the log file from the PC that isn't working does not have any entries in it for LDIScn32.exe whereas the other log file does.
From the LDIScan log file, I did see a difference where the system that is not working was having problems connecting to the LD server. So that is something that I can see that might be causing problems. However, the odd thing is that the log file does not show any entries after April 18th. It's as if the process just gave up. And it did scan once successfully before the 18th.
Below is a snippet from the logs (LDISCAN) from both a working and non-working PC:
From working PC -
Sun, 04 May 2008 04:38:20 Firewall is enabled
Sun, 04 May 2008 04:38:30 open key Software\Utimaco\SGEasy with flags 0x20019 returns handle 0, status 2
Mon, 05 May 2008 05:12:03 Performing TCP connection with a timeout of 2500 milliseconds
Mon, 05 May 2008 05:12:06 Download information for HTTP://SERVERNAME/LDLOGON/LDAPPL3.PAZ : 89,785 bytes in 0:00:00.094 seconds, bandwidth 932.7730 kb/s
From non-working PC -
Wed, 16 Apr 2008 11:25:55 open key Software\Utimaco\SGEasy with flags 0x20019 returns handle 0, status 2
Fri, 18 Apr 2008 04:56:02 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.INI' was not a successful http request (503)
Fri, 18 Apr 2008 04:56:02 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.BAZ' was not a successful http request (503)
Fri, 18 Apr 2008 04:56:03 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.BAZ' was not a successful http request (503)
Fri, 18 Apr 2008 04:56:03 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.PAZ' was not a successful http request (503)
Fri, 18 Apr 2008 04:56:03 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.PAZ' was not a successful http request (503)
Fri, 18 Apr 2008 04:56:05 Response for 'HTTP://SERVERNAME/LDLOGON/LDAPPL3.INI' was not a successful http request (503)