Hi, the setting my colleague suggested you try can affect the type of session the Windows Task Scheduler runs our program in - that is to say, whether it runs it in session-0 or not (and it may help if the latter applies). But we cannot absolutely control what type of session Windows uses (all we can do is suggest a setting to you that might influence its decision)
Plus, in either 'session case', the fact remains that a Scheduled Task always 'logs on as a batch job' (separately), and the sad truth is that a 'batch job' environment does not (for itself) re-create drive mappings that a full console logon would. Sometimes it is the case that such a batch job logon can 'see' drive mappings (created by the console logon - if the console logon session is still ongoing, and both processes are using the same session type), but if it can't, it can't, sorry. There's no option in Windows to change that, and if Windows tells us it cannot see drive X in that batch-job context, there's no way for us to persuade it otherwise.
If you ran the profile c/o a shortcut (drag profile to desktop to create one), it's very likely it will work, because they're both in the same session (not just the same session-type, but the same actual console session). Such a shortcut will run Unattended (no Differences window, etc) but would need to be manually triggered. It's possibly something you could incorporate into your end-of-day routine...double-click shortcut then head on out, etc.
Plus, in either 'session case', the fact remains that a Scheduled Task always 'logs on as a batch job' (separately), and the sad truth is that a 'batch job' environment does not (for itself) re-create drive mappings that a full console logon would. Sometimes it is the case that such a batch job logon can 'see' drive mappings (created by the console logon - if the console logon session is still ongoing, and both processes are using the same session type), but if it can't, it can't, sorry. There's no option in Windows to change that, and if Windows tells us it cannot see drive X in that batch-job context, there's no way for us to persuade it otherwise.
If you ran the profile c/o a shortcut (drag profile to desktop to create one), it's very likely it will work, because they're both in the same session (not just the same session-type, but the same actual console session). Such a shortcut will run Unattended (no Differences window, etc) but would need to be manually triggered. It's possibly something you could incorporate into your end-of-day routine...double-click shortcut then head on out, etc.