Remoting Using PowerShell V1

re: Remoting Using PowerShell V1

Andy Schneider — Sat, 01 Mar 2008 01:18:08 GMT

This is awesome!! I just pulled all the processes from my win2k8 box running V1 down to my vista machine. Schweet !!!

re: Remoting Using PowerShell V1

lrbell — Mon, 03 Mar 2008 07:35:39 GMT

We have a constant stream of AD environments coming into our IT dept. We cannot assimilate them (long story). I would like to [from ONE powershell box] access each domain in a manner not unlike an array of systems.

Yes, I have ten domains with 10 different user/pw credentials with NO trust (again, long story).

A sort of stand alone powershell mgmt system that can bridge the scenario of n untrusted ADs.

I know calling things 'within' an AD is easily done in PS, but my dilemma adds a step, as I am outside the AD.

(yes, I could put PS on one system per domain, but that defeats my desire to pull this off with zero footprint)

I have posted this elsewhere with no apparent luck; Jeffery, will you assist?

re: Remoting Using PowerShell V1

Abhishek Agrawal [MSFT] — Mon, 03 Mar 2008 12:41:07 GMT

Hi lrbell,

Thanks for describing your sceanrio. I have passed it along to the AD team. I will post back here once I hear from them.

Thanks,

Abhishek Agrawal[MSFT]

re: Remoting Using PowerShell V1

Dude85 — Wed, 05 Mar 2008 12:41:07 GMT

I have a similar problem as Irbell, I have to read informations from exchange management console outside the AD.

Scenario:

Machine A: Exchange 2007 in AD

Machine B: My Tool to overview Exchange performance

I'm not sure if it's possible. I would be happy if you can give me any hints ;)

@Dude85

marco.shaw — Wed, 05 Mar 2008 21:16:27 GMT

Dude85,

WMI support has been stripped out of Exchange 2007. That being said, you could possibly:

1. Use Exchange Web Services.

2. Use another local system to get the performance data, save it to a file, etc., and you can then fetch that file.

re: Remoting Using PowerShell V1

Dude85 — Thu, 06 Mar 2008 12:12:52 GMT

Marco,

thanks for your answer. The big goal for this problem is, only to have code on the workstation. You install the application and write the name of your exchange server and the tool should monitor the informations without any special configuration on the exchange server.

The part with web service could be a good solution, but I have to implement my own webservices on the exchange server, because you can't read performance informations with the implemented services.

Well, if there's no other way, I will implement the web service solution :P

thanks

re: Remoting Using PowerShell V1

stryqx — Sun, 09 Mar 2008 15:54:45 GMT

While I think Powershell is a step in the right direction, this sort of camel through the eye of a needle approach makes me wish that ssh/sshd got added as a role in Win2008...

re: Remoting Using PowerShell V1

ajax76 — Wed, 12 Mar 2008 05:46:41 GMT

PS C:\> Winrs "-r:localhost" PowerShell -NoProfile -NonInteractive start-psjob -command 'l

s -rec c:\'

Winrs error:Access denied. PS C:\> Winrs "-r:localhost" PowerShell -NoProfile -NonInt

eractive new-runspace

What's wrong?

All i need(winrm,firewall,policy) - install, config., and start.

re: Remoting Using PowerShell V1

Vadim Malashenko — Wed, 12 Mar 2008 21:27:00 GMT

Please, help to solve this problem (PSJob, WinRM):

http://groups.google.ch/group/microsoft.public.windows.powershell/browse_thread/thread/c50f2ed5c1f108b1

re: Remoting Using PowerShell V1

lrbell — Sat, 22 Mar 2008 02:29:35 GMT

Abhishek, any word, update, or status?

Hearing crickets is great for fishing, but not so much on blogs..

:-)

re: Remoting Using PowerShell V1

mario — Sun, 22 Jun 2008 05:03:07 GMT

another option is to use SSH

http://gotmvc.net/?p=3

re: Remoting Using PowerShell V1

EDF — Wed, 16 Jul 2008 00:13:22 GMT

That ssh server Mario mentions in his article won't due for an enterprise. Running the command with any flags/derivitives that I can think of):

ssh2 user@host "powershell -command script.ps1"

...doesn't work in Tectia SSH Server. It just hangs. It's disappointing that we have to battle/justify why admins will need WinRM/WinRS/WinMGMT in addition to SSH, just so we can use powershell on our DMZ systems. It'll take years for us to actually use WinRM because of the need to duplicate what we already have using ssh.

I appreciate the efforts of the powershell team, but without being able to exec powershell from ssh, powershell is a novelty for my org (fortune 500 - near the bottom of the stack). We'll still have to use vbs and bat files.

re: Remoting Using PowerShell V1

liral — Thu, 22 Jan 2009 09:21:33 GMT

HI ALL

i want more information for remote connection in power shell v2

Windows PowerShell Blog : Remoting Using PowerShell V1

It's my life... And I live it... — Wed, 18 Feb 2009 20:51:29 GMT

Just a reminder of how you can remote a script in PowerShell using the V1 capabilities and WinRS/WinRM

WinRS doesn't support -skipCNcheck

Doug Clutter — Wed, 03 Jun 2009 21:27:21 GMT

If you are running your WinRM connection through HTTPS you'll need a cert. When calling WinRM on a staging server, we use the -skipCNcheck because the server name in the cert doesn't match the staging server.

Unfortunately, WinRS doesn't support skipCNcheck. While more complicated, "WinRM Invoke Create Win32_Process" will do the trick.

re: Remoting Using PowerShell V1

Doug Clutter — Wed, 03 Jun 2009 23:41:45 GMT

Base64 sometimes uses the = sign for padding. When it does this, you cannot pass the encoded string on the command line because the CMD.exe uses the = character as a delimiter and it gets dropped.

As a work-around, I've created this function to create encoded strings:

Function global:Get-EncodedScript([string] $script) {

$encodedScript = [System.Convert]::ToBase64String([System.Text.Encoding]::UNICODE.GetBytes($script))

while ($encodedScript.Contains("=")) {

$script = $script + " "

$encodedScript = [System.Convert]::ToBase64String([System.Text.Encoding]::UNICODE.GetBytes($script))

}

return $encodedScript

}

Problem with EncodedCommand

Doug Clutter — Wed, 03 Jun 2009 23:42:42 GMT

Base64 sometimes uses the = sign for padding. When it does this, you cannot pass the encoded string on the command line because the CMD.exe uses the = character as a delimiter and it gets dropped.

As a work-around, I've created this function to create encoded strings:

Function global:Get-EncodedScript([string] $script) {

$encodedScript = [System.Convert]::ToBase64String([System.Text.Encoding]::UNICODE.GetBytes($script))

while ($encodedScript.Contains("=")) {

$script = $script + " "

$encodedScript = [System.Convert]::ToBase64String([System.Text.Encoding]::UNICODE.GetBytes($script))

}

return $encodedScript

}

re: Remoting Using PowerShell V1

ali — Thu, 03 Sep 2009 12:16:07 GMT

how can i check if a server really exists ?

i mean ... i'm connecting to a number of servers, and using the get-wmiobject..

if a servers doesn't exist, then the whole task gets stuck, with no error action... can u help