LackOfAName

~Bump~ We still have this issue with no correlation among the ones that are failing. If I re-evaluate several times, the affected clients will eventually execute the script quickly enough to complete.

(Reposting this in the correct place - sorry I am a noob.) I have a simple PS script running in a configuration item in our environment. On approximately 4% of our machines are throwing a timeout error. I am seeing similar failures for PowerShell detection for an Application. What is the timeout period for these, and is there anything I can do to modify it? I've dug through everything I could find and have not come up with an answer.

One way around is to deploy a task sequence with a single 'Run Command Line' step. This TS step allows you to specify a domain account. If the users who will be installing this have rights, you could test installing with user rights also. There may be things on the PowerShell side that may work as well. I would start here: http://blogs.technet.com/b/benshy/archive/2012/06/04/using-a-powershell-script-to-run-as-a-different-user-amp-elevate-the-process.aspx

Posting this in the right forum.

I have a simple PS script running in a configuration item in our environment. On approximately 4% of our machines are throwing a timeout error. I am seeing similar failures for PowerShell detection for an Application. What is the timeout period for these, and is there anything I can do to modify it? I've dug through everything I could find and have not come up with an answer.