As you may or may not know, the handling of Scheduled Tasks in Windows 7 (and server 2008/R2, if that’s your thing) is vastly different from that of Windows XP (and Server 2003). For example, wheras in Windows XP if you needed to move tasks from one machine to another, you could simply copy the appropriate .job file from C:\Windows\Tasks on one machine to another (and of course verify all paths were still correct), you cannot actually copy the .job file from Windows XP to Windows 7.
That said, that’s not the issue that we’re having. We’re in the process (finally!) of validating TDP Automations under Windows 7. The scripts work just fine when run manually from within TDP, but we’re having some issues getting them to run on unattended user sessions with our NT Service Account.
The first task I tried worked just fine - a simple “Select to File and then Email” task - but only so long as the NT Service Account was logged in to the host machine. Even with the option of “Run whether user is logged on or not”, the task will not execute if the NT Service Account isn’t logged in locally (Error message from the Windows Event Viewer: “Task Scheduler did not launch task “” because user “DOMAIN\SERVICE ACCT” was not logged on when the launching conditions were met. User Action: Ensure user is logged on or change the task definition to allow launching when user is logged off.”) - it’s not really surprising that Windows contradicts itself here.
Most Google searches to various items related to this return information about scheduled tasks that were created with Group Policies (not applicable here), the user in question not having the permission to “Log on as Batch Job” (Local Windows Administrators group has this right by default; NT Service Account is in the Local Admin Group via a Domain Group, and has the permission explicitly defined - no dice). I’ve reviewed a bunch of items and I’m not getting anywhere.
So, has anyone else encountered this issue? If so, were you able to work around the problem?
We don’t have a choice on going to Windows 7 - Windows XP has reach EOL even with Enterprise Support Agreements, so we’re basically being forced. We have some time, but not much.