As part of a new project, we are migrating our Toad automations from Windows 7 desktops to Windows Server 2012 R2 VMs.
With that, however, comes an issue where the service account that runs the Toad automations isn’t allowed to remain logged in on the Windows Server 2012 desktop for more than 48 hours - this is a corporation-wide GPO setting and cannot be changed.
Where we’re having a problem is that the TDP Scheduled Task will appear to execute, but no output is produced, and the log is not updated.
If I leave the service account logged in, and simply ‘lock’ my session, everything works as expected - just like our Windows 7 machines - but in 48 hours, the account is automatically logged out, and we’re back to either having to login, or getting no output.
From my research, it appears that starting with Windows Vista (yeah, I know…), Microsoft implemented Session 0 Isolation, meaning all interactive logins start at Session 1 and up, and Session 0 is reserved for system and service use only, including Scheduled Tasks configured with the option of ‘Run whether user is logged on or not’. The problem is that Session 0 does not have an interactive desktop, so any processes that are expecting a UI response, or even the ability to create a UI, seem to fail, which would appear to include Toad.
That said, I’ve read in various threads on here and around the net that folks have gotten this to work correctly, but so far - after several weeks - I haven’t been able to figure it out, and I’m hoping one of you kind folks will be able to point me in the right direction.