No dice: access denied.
I try it with my own account. Access denied. I try it with the local admin account. Access denied.
But if I run the #script directly from #DOS: access granted.
So I figure: maybe the network user can't see the drive letter. So I run a #DosPrompt as that user. And yes! They can't see it.
That's weird, though. I can see it. The local admin can see it. The network user has full read and modify access - 2/4
What the heck are you doing, #Microsoft #Windows?
At my wit's end, I have an idea. Maybe I can have the #MSDosBatch script create the drive letter so it will be available during the #ScheduledTask session? Yes, I can! With the #NetUse command.
On first try: fail! Drive letter already is mapped - 3/4
Seriously, what the heck, #Microsoft #Windows? First you tell me you can't access the drive letter, and then when I map it you tell me it's there already? You suck at #accessPrivileges.
Final solution: unmap the drive letter, and then in the #MSDosBatch script first map it, then unmap it when done.
Holy moly, Gates et al, did you have to make your system contradict itself? - 4/4
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!