OK, I think what I'm about to say is right, but you may want to check it. When you run a job as a login that's a member of sysadmin, it runs in the context of the SQL Server Agent service account. When you run a job as a login that isn't sysadmin, it runs in the context of whatever you're logged in as. That must be why it's scanning the drives you have mapped when you're not sysadmin, but not doing so when you are. You'll need to find a way to provided a list of UNC locations for the job to scan.