RE: [scripting] Invoke-Command

Hi, yes the scripts is placed on d:\ where it is specified Thanks, Jason From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of christopher.catl...@us.sogeti.com Sent: Thursday, January 16, 2014 12:43 PM To: scripting@lists.myitforum.com Subject: RE: [scripti

RE: [scripting] Invoke-Command

Does that script exist on the D drive of the remote server? That's how your calling it in your script. And please, use something other than Comic Sans, it makes my eyes bleed. Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northw

RE: [scripting] Invoke-Command

This works from SERVERB directly. Invoke-Command -ComputerName ServerB -ScriptBlock { Get-Process} I tried it using with the credential argument and it also works Invoke-Command -ComputerName ServerB -ScriptBlock { Get-Process} -Credential $credential But with the DLS script it does not. Thank

RE: [scripting] Invoke-Command

Jason, Can you send a screenshot of the issue? Your font is rather challenging to read. Have you tried a simpler command, just for starters? When all else fails, take it back to the basics. Invoke-Command -ComputerName serverb -ScriptBlock { Get-Process; }; Cheers, Trevor Sullivan

[scripting] RE: Invoke-Command

I ran this yesterday PS C:\Users\jason> winrm quickconfig WinRM already is set up to receive requests on this machine. WinRM is not set up to allow remote access to this machine for management. The following changes must be made: Create a WinRM listener on HTTP://* to accept WS-Man requests to an

RE: [scripting] Invoke-Command

Here is the error we receive cmdlet Get-Credential at command pipeline position 1 Supply values for the following parameters: Credential An error occured trying to connect to SERVERB DEBUG: Attempting to execute the following command: Invoke-Command -ComputerName SERVERB -ScriptBlock {param() &

[scripting] RE: Invoke-Command

http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/16/enable-powershell-remoting-to-enable-running-commands.aspx You need to enable and configure Ps-Remoting Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Hig

RE: [scripting] Invoke-Command

Jason, What do you mean "does not work?" Are you getting an error? If so, what is the error? FYI, you have to enable Windows Remote Management (WinRM) to use Invoke-Command. Use Enable-PSRemoting -Force or Set-WsmanQuickConfig, or use Active Directory Group Policy to enable WinRM. Cheer

[scripting] RE: Invoke-Command

What error do you get? Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of jlos...@mpi.mb.ca Sent: Thursday, January 16, 2014 11:03 AM To: scripting@lists.myITforum.com Subject: [scripting] Invoke-Command Hi, we have a set of scripts that run

[scripting] Invoke-Command

Hi, we have a set of scripts that run on ServerA and they do not run on identical ServerB The Invoke-Command does not work locally or remotely on ServerB Any ideas? Thanks, Jason Loster Senior IT Analyst IT Security, Compliance and Risk Management Manitoba Public Insurance 708-234 Donald St. W