Ahhhhh, that explains it. My problem is solved.
There are two places that you set the Interactive token: the TaskDefinition.Principal.LoginType and in the RegisterTaskDefinition call.
Might I recommend that the error message be slightly altered to reflect what you just said. As it stands now, the message tells you nothing helpful about what specifically needs to be done to correct the problem.
'Task Scheduler 2.0 (1.2) does not support setting this property. You must use an InteractiveToken in order to have the task run in the current user session.'
To something like:
'Task Scheduler 2.0 (1.2) does not support setting this property. You must specify using an InteractiveToken in the RegisterTaskDefinition in order to have the task run in the current user session.'
Thanks for the help, I will update my SO question to assist others.
There are two places that you set the Interactive token: the TaskDefinition.Principal.LoginType and in the RegisterTaskDefinition call.
Might I recommend that the error message be slightly altered to reflect what you just said. As it stands now, the message tells you nothing helpful about what specifically needs to be done to correct the problem.
'Task Scheduler 2.0 (1.2) does not support setting this property. You must use an InteractiveToken in order to have the task run in the current user session.'
To something like:
'Task Scheduler 2.0 (1.2) does not support setting this property. You must specify using an InteractiveToken in the RegisterTaskDefinition in order to have the task run in the current user session.'
Thanks for the help, I will update my SO question to assist others.
