Ok, so I removed the OnLogin triggers from the profiles, put them in a group and added the OnLogin trigger to this group. Task scheduler then shows 2 tasks, the 'start with windows' task and the group task. Doing a re-logon or a restart yields the same result: the 'start with windows' task exits immediately and the group task performs like it should.
Then I tried the following: in task scheduler, I exported the 'start with windows' task to XML, deleted the task, navigated in task scheduler from the TaskSchudulerLibrary\2BrightSparks\SyncBackPro\pcname-username folder (where the syncback tasks reside) to the 'root' of the task scheduler, being TaskSchudulerLibrary. There I imported my exported task. So now the 'start with windows' task is in a different folder (context) in the taskmanager. The result is that at logon or restart both tasks run properly![:)]( "Smile")
So there is a work around to this problem, but it remains strange that when both tasks are in the same scheduler context they influence each other so one of them exits. Seems to me the 'start with windows' task checks for running instances of itself and recognizes the 'on login' task as such and then exits. As the scheduler does start the task and runs the 'start with windows' process (which then exits with 0), it seems the check is not done by the task scheduler but by syncbackpro itself. This is confirmed by setting the tasks setting 'If the task is already running, then the following rule applies:' to 'Run a new instance'.
Then I tried the following: in task scheduler, I exported the 'start with windows' task to XML, deleted the task, navigated in task scheduler from the TaskSchudulerLibrary\2BrightSparks\SyncBackPro\pcname-username folder (where the syncback tasks reside) to the 'root' of the task scheduler, being TaskSchudulerLibrary. There I imported my exported task. So now the 'start with windows' task is in a different folder (context) in the taskmanager. The result is that at logon or restart both tasks run properly
So there is a work around to this problem, but it remains strange that when both tasks are in the same scheduler context they influence each other so one of them exits. Seems to me the 'start with windows' task checks for running instances of itself and recognizes the 'on login' task as such and then exits. As the scheduler does start the task and runs the 'start with windows' process (which then exits with 0), it seems the check is not done by the task scheduler but by syncbackpro itself. This is confirmed by setting the tasks setting 'If the task is already running, then the following rule applies:' to 'Run a new instance'.