Q: When I run Windows PowerShell Invoke-Command on more than 32 remote servers, the command runs only on the first 32 servers and queues the others. How can I change this?

A: The queuing of commands is by design, done to control the amount of concurrent remote command executions. However, you can change the concurrent limit by using the -ThrottleLimit <value> parameter for Invoke-Command to increase it. Here's an example of how to use it:

<code>Invoke-Command -ThrottleLimit 64 -ComputerName a,b,c -ScriptBlock {command}</code>

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.