Scan Failure when using network drives with UNC path when profile is run with a schedule
This error can occur if
your Windows login username for the Scheduled Task is different from the
Windows login username you normally login with. If you use a UNC path
(\\server\share\folder), and no username and password is specified in
the profile's Network settings for that UNC path, then the current login username
Check your Scheduled Task settings to ensure the correct
username is being used, or try adding credentials to the Network settings page in the profile. Some users have reported that entering the exact-same credentials there as those in the Scheduled Task suddenly works, for no obvious reason except possibly some corruption of the security token issued when the Task 'logged on as a batch job' (whereby that token is then side-stepped by providing 'alternate' credentials using a different mechanism).