Also, under the "Configure for:" window, I've tried every available setting Can anyone shed some light on this? Am I not setting something up right?ĮDIT: I have the tasks set to run whether the user is logged in or not (password is stored), and the "Run with highest privileges" option is checked. The scripts are stored in the same location on each computer as well. The only difference is in the path to the destination referenced in the script (UNC naming is used in each case),Īnd the script name is customized per the individual computer. I've used the same script on numerous Windows 7 computers with no problems, and worded the scheduled task the same (all have Win 7 Pro 64-bit). Microsoft-Windows-TaskScheduler/Operational Task Scheduler successfully finished "" instance of the "\Copy Email Archives-Week 1" task for user "XXXX\TIM". Log Name: Microsoft-Windows-TaskScheduler/Operational Here's the history output from one of the scheduled tasks (domain name altered): Powershell.exe -NoProfile -NoLogo -NonInteractive -ExecutionPolicy Bypass -File “C:\scripts\PowerShellScript-Copy-email-USER-W1.ps1” This is what I use for the scheduled task under the "Action" section: Prior research for this code is scant, but indicates some sort of permission problem. Tasks, I get a 0XFFFD0000 result each time. When I run the scripts in PowerShell, they work fine. The user has full control of the folder where the scripts are housed, as well as the target network location. The scripts differ only in where the archives are copied to (to keep The computer in question runs Windows 10 Pro 64-bit. I have a set of PowerShell scripts that are designed to copy email archives from a user's hard drive to a network location.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |