![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| 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. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | 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 Specs![]() |
| | #2 (permalink) |
| | 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 Specs![]() |
| | #3 (permalink) |
| | 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 Specs![]() |
| | #4 (permalink) |
| | 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 Specs![]() |
| | #5 (permalink) |
| | 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 Specs![]() |
| | #6 (permalink) |
| | 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 Specs![]() |
![]() |
| 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 | |||