I read the threads somewheere the Powershell 2.0 comes with remoting.

Now i m not a developer, what does Remoting means ?

To me, i thought i can use GWMI to access remote computer from my machine.

Is that my definition of Remoting ?

Thanks

yes and no.
GWMI, and also powershells WMI cmdlets have the ability to do remote
WMI. and various other cmdlets can act against remote machines , but
this behaviour is build inside each cmdlet itself, not part of the
powershell engine.

with powershell remoting in 2.0, you can do a few things

1) connect to a remote machine, and run commands, either as a script, or
interactive as if you were sitting there
2) write a script that sends out powershell code to many different
machines, to run that code on each of those machines, and return the
results to you
3) as a server, where many different users can connect from their local
machines and run script against you.

I know i didn't explain it entirely accurately, but it should be enough
to give you a general picture.

-Karl

IT Staff wrote:

> I read the threads somewheere the Powershell 2.0 comes with remoting.
>
> Now i m not a developer, what does Remoting means ?
>
> To me, i thought i can use GWMI to access remote computer from my machine.
>
> Is that my definition of Remoting ?
>
> Thanks
>
>

"IT Staff" <jkklim@xxxxxx> wrote in message
news:O$KmA%238NIHA.3852@xxxxxx

>I read the threads somewheere the Powershell 2.0 comes with remoting.
>
> Now i m not a developer, what does Remoting means ?
>
> To me, i thought i can use GWMI to access remote computer from my machine.
>
> Is that my definition of Remoting ?
>
> Thanks
>

It effectively means that you can sit at one computer, and open up
powershell session on another computer, and run whatever commands you like -
not just retrieving wmi info.

eg Here's an example of a session connecting from an XP machine to a Vista
machine. 'RunV' is a local script here on the XP machine that runs any
commands I type on a connected Vista machine. You could similarly run
automated scripts on a connected machine ........


PS (1) > [environment]::OSVersion | fl


Platform : Win32NT
ServicePack : Service Pack 2
Version : 5.1.2600.131072
VersionString : Microsoft Windows NT 5.1.2600 Service Pack 2



PS (2) > runv
Running commmands on Vista computer ......
PS REMOTE>[environment]::OSVersion | fl


Platform : Win32NT
ServicePack :
Version : 6.0.6000.0
VersionString : Microsoft Windows NT 6.0.6000.0



PS REMOTE>exit
PS (3) >


[NB I used 'winrs' to connect, in this particular case, rather than
invoke-expression, since the CTP doesn't currently support Vista machines,
but it's effectively the same end result ]


--
Jon

Thanks guys i understand now.

The reason i ask is this when i did imaging for desktop, the engineer ask me
why i want to put .net framework on every machine, winrm , powershell ver xx
etc

I bluff at the superficial level, that i need to run powershell codes.

Now u have given me a good reasons to support my justifications :-)




"Jon" <Email_Address@xxxxxx> wrote in message
news:O339ZS9NIHA.5524@xxxxxx

> "IT Staff" <jkklim@xxxxxx> wrote in message
> news:O$KmA%238NIHA.3852@xxxxxx

>>I read the threads somewheere the Powershell 2.0 comes with remoting.
>>
>> Now i m not a developer, what does Remoting means ?
>>
>> To me, i thought i can use GWMI to access remote computer from my
>> machine.
>>
>> Is that my definition of Remoting ?
>>
>> Thanks
>>

>
>
>
> It effectively means that you can sit at one computer, and open up
> powershell session on another computer, and run whatever commands you
> like - not just retrieving wmi info.
>
> eg Here's an example of a session connecting from an XP machine to a Vista
> machine. 'RunV' is a local script here on the XP machine that runs any
> commands I type on a connected Vista machine. You could similarly run
> automated scripts on a connected machine ........
>
>
> PS (1) > [environment]::OSVersion | fl
>
>
> Platform : Win32NT
> ServicePack : Service Pack 2
> Version : 5.1.2600.131072
> VersionString : Microsoft Windows NT 5.1.2600 Service Pack 2
>
>
>
> PS (2) > runv
> Running commmands on Vista computer ......
> PS REMOTE>[environment]::OSVersion | fl
>
>
> Platform : Win32NT
> ServicePack :
> Version : 6.0.6000.0
> VersionString : Microsoft Windows NT 6.0.6000.0
>
>
>
> PS REMOTE>exit
> PS (3) >
>
>
> [NB I used 'winrs' to connect, in this particular case, rather than
> invoke-expression, since the CTP doesn't currently support Vista machines,
> but it's effectively the same end result ]
>
>
> --
> Jon
>
>
>

well thats for powershell version 2.0, which there is only an early CTP
for, which isn't licensed to be installed in a production environment,
nor recommended.

-Karl