A customer requested to have a a quick and dirty script copied from d:\scripts to c:\temp and executed across a few hundred XP boxes ( not a cluster in this case ). Just in case you are looking to do this:
psexec @hostlist c:\temp\doit.bat
Virtualization, High Performance Computing, Enterprise Computing
You are currently browsing the monthly archive for July 2009.
A customer requested to have a a quick and dirty script copied from d:\scripts to c:\temp and executed across a few hundred XP boxes ( not a cluster in this case ). Just in case you are looking to do this:
I found that WinRM limits the number of concurrent shells while developing some PowerShell tools that connect around to a bunch servers in parallel. You may get an error like:
“Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. This user is allowed a maximum number of 4 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user.”
This is how to configure and override the default of 5:
PSH>winrm quickconfig
PSH>winrm get winrm/config
PSH>winrm set winrm/config/winrs `@`{MaxShellsPerUser=`”50`”`}
Tags: PowerShell
© 2006-2010 HiperLogic, LLC. | Serving the Ann Arbor, Southeast Michigan, and Ohio region | (888)-268-3930 |