Windows Vista Forums
Vista Forums Home Join Vista Forums Windows 7 Forum Vista Tutorials Tags
Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks.

Go Back   Vista Forums > Misc Newsgroups > PowerShell

Vista - Powershell 2.0 and remoting

Reply
 
Old 11-27-2007   #1 (permalink)
Nex6


 
 

Powershell 2.0 and remoting

what are the requirements on the 'remote' computer for remoting? eg: does
winRM or powershell have to be installed?



-Nex6


My System SpecsSystem Spec
Old 11-27-2007   #2 (permalink)
Jon


 
 

Re: Powershell 2.0 and remoting


"Nex6" <nex6@xxxxxx> wrote in message
news:um9tNlUMIHA.5224@xxxxxx
Quote:

> what are the requirements on the 'remote' computer for remoting? eg: does
> winRM or powershell have to be installed?
>
>
>
> -Nex6

This is lifted from the output from the command "Get-Help About_Remoting" ,
to which you can probably add the fact that it doesn't currently work with
Vista (unless you've installed SP1 beta)..........


"To work remotely, you must have permission to connect to the remote
computer, permission to run Windows PowerShell, and permission to access
data stores, like files and folders, and the registry on the remote
computer.

The remote computer must have Windows PowerShell, the .NET Framework
2.0, and WS-Management. Any files and other resources that are needed
to execute a particular command must be on the remote computer; the
remoting commands do not copy any resources.

When you work remotely, you use two copies of Windows PowerShell, one on
the local computer and one on the remote computer. As a result, your
work is affected by the Windows policies and permission on the remote
computer and the Windows PowerShell policies (such as the execution
policy) profiles, and preferences on the remote computer."


For more info

Get-Help About_Remoting #Requires version 2 CTP installed


--
Jon


My System SpecsSystem Spec
Old 11-27-2007   #3 (permalink)
IT Staff


 
 

Re: Powershell 2.0 and remoting

I've not work with Powershell 2.0 yet, so this means :

a) remote machine must have powershell 2.0 + .net framework 2.0 installed +
wm
b) make sure the remote machine allows for *unstricted* execution policy

Am i correct ?


"Jon" <Email_Address@xxxxxx> wrote in message
news:eiglDFVMIHA.5224@xxxxxx
Quote:

>
> "Nex6" <nex6@xxxxxx> wrote in message
> news:um9tNlUMIHA.5224@xxxxxx
Quote:

>> what are the requirements on the 'remote' computer for remoting? eg: does
>> winRM or powershell have to be installed?
>>
>>
>>
>> -Nex6
>
>
> This is lifted from the output from the command "Get-Help About_Remoting"
> , to which you can probably add the fact that it doesn't currently work
> with Vista (unless you've installed SP1 beta)..........
>
>
> "To work remotely, you must have permission to connect to the remote
> computer, permission to run Windows PowerShell, and permission to access
> data stores, like files and folders, and the registry on the remote
> computer.
>
> The remote computer must have Windows PowerShell, the .NET Framework
> 2.0, and WS-Management. Any files and other resources that are needed
> to execute a particular command must be on the remote computer; the
> remoting commands do not copy any resources.
>
> When you work remotely, you use two copies of Windows PowerShell, one on
> the local computer and one on the remote computer. As a result, your
> work is affected by the Windows policies and permission on the remote
> computer and the Windows PowerShell policies (such as the execution
> policy) profiles, and preferences on the remote computer."
>
>
> For more info
>
> Get-Help About_Remoting #Requires version 2 CTP installed
>
>
> --
> Jon
>
>

My System SpecsSystem Spec
Old 11-27-2007   #4 (permalink)
Jon


 
 

Re: Powershell 2.0 and remoting


"IT Staff" <jkklim@xxxxxx> wrote in message
news:uOO490VMIHA.2432@xxxxxx
Quote:

> I've not work with Powershell 2.0 yet, so this means :
>
> a) remote machine must have powershell 2.0 + .net framework 2.0 installed
> + wm
> b) make sure the remote machine allows for *unstricted* execution policy
>
> Am i correct ?
>
>

That's the way I'd interpret it. Might be some flexibility with (b), if
you're into signing your own scripts etc, but (a) would seem to be a basic
prerequisite.

--
Jon


My System SpecsSystem Spec
Old 11-27-2007   #5 (permalink)
Karl Prosser[MVP]


 
 

Re: Powershell 2.0 and remoting

IT Staff wrote:
Quote:

> I've not work with Powershell 2.0 yet, so this means :
>
> a) remote machine must have powershell 2.0 + .net framework 2.0 installed +
> wm
> b) make sure the remote machine allows for *unstricted* execution policy
>
> Am i correct ?
>

there are different ways to do remoting but the remote machine doesn't
have to have unrestricted execution policy.. as you are running at the
command prompt, if you sent a command to go run on a remote computer it
will, based on YOUR permissions on that machine.. So if you have the
rights to run commands on that machine, the ability for you to, will be
no different than if you were physically at that machine.

-Karl
My System SpecsSystem Spec
Old 11-30-2007   #6 (permalink)
RichS


 
 

Re: Powershell 2.0 and remoting

When using remoting PowerShell doesn't actually have to be running on the
remote system & you don't have to be logged on to the remote machine. As
stated you just need to have the credentials on the remote box to perform the
task. My recent testing shows that it works very nicely.

--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Karl Prosser[MVP]" wrote:
Quote:

> IT Staff wrote:
Quote:

> > I've not work with Powershell 2.0 yet, so this means :
> >
> > a) remote machine must have powershell 2.0 + .net framework 2.0 installed +
> > wm
> > b) make sure the remote machine allows for *unstricted* execution policy
> >
> > Am i correct ?
> >
>
>
> there are different ways to do remoting but the remote machine doesn't
> have to have unrestricted execution policy.. as you are running at the
> command prompt, if you sent a command to go run on a remote computer it
> will, based on YOUR permissions on that machine.. So if you have the
> rights to run commands on that machine, the ability for you to, will be
> no different than if you were physically at that machine.
>
> -Karl
>
My System SpecsSystem Spec
Reply

Thread Tools


Similar Threads
Thread Forum
Powershell Remoting in broken between CTP3 and RC1 PowerShell
PowerShell Remoting equivalent of SSH scp PowerShell
Widnow's Powershell Remoting PowerShell
Powershell v2 remoting not working? PowerShell
Powershell 2.0 with remoting : ok what is Remoting ? PowerShell


Vista Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows Vista", the Start Orb, and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46