Hi dahall,
Thank you for your effort, is there any progress with this issue ?
I think that you are right, I suspect that the issue is caused by the underlying Task Scheduler COM library, I fear that this scenario is not supported.
Can we find some workaround for this limitation ?
Windows 8 is able to talk to Windows 7/2008’s Task Scheduler - just the other way around is not working today.
This is very surprising. my expectation would be that the ITaskService::Connect function negotiates the protocol that is used to talk between Windows 7/2008 and 8 - similar to what SMB does. (E.g. if one endpoint “speaks” Task Scheduler 1.3 and the other 1.4, then they should fall back to version 1.3)
Thanks,
Yossi
Thank you for your effort, is there any progress with this issue ?
I think that you are right, I suspect that the issue is caused by the underlying Task Scheduler COM library, I fear that this scenario is not supported.
Can we find some workaround for this limitation ?
Windows 8 is able to talk to Windows 7/2008’s Task Scheduler - just the other way around is not working today.
This is very surprising. my expectation would be that the ITaskService::Connect function negotiates the protocol that is used to talk between Windows 7/2008 and 8 - similar to what SMB does. (E.g. if one endpoint “speaks” Task Scheduler 1.3 and the other 1.4, then they should fall back to version 1.3)
Thanks,
Yossi