Folks, I have recent run into an issue that I think will be best to crowdsource to seek out resolution. In 2008/R2 Microsoft has broken Task Scheduler when used in conjuction with the security setting, "Network access: Do not allow storage of credentials or .NET Passports for network authentication". Some of you might have already battled this issue during your own roleouts of 2008 and I wanted to rekindle the conversation. With this security setting Enabled, Scheduled Tasks basically cannot function in all scenerios, more specificly without user intervention of any kind. This is fairly short sited of Microsoft obviously, but I wanted to ask the question. Has anyone found a work around for this in any manner? Powershell script, registry change, etc? I'm basically looking to maintain the GPO and security structure in my enterprise and continue to use Task Scheduler the way I was accustomed too. Thanks in advance, Jordan

Update on this issue. There is no work around, this is how Task Scheduler will work going forward. We ended up modifying the GPO globally to maintain functionality and SOP.