Contact Info

Crumbtrail

ActiveXperts.com » Administration » Powershell » Powershell 3.0 » Disable-PSRemoting

Disable-PSRemoting - Powershell 3.0 CmdLet

ActiveXperts Network Monitor ships with integrated Powershell scripts to monitor complex network. The scripts run out of the box
Download the ActiveXperts Network Monitor FREE version now »

Disable-PSRemoting

Short description
Prevents remote users from running commands on the local computer.

Syntax
Disable-PSRemoting [-Force] [-Confirm] [-WhatIf] [<CommonParameters>]





Description
The Disable-PSRemoting cmdlet prevents users on other computers from running commands on the local computer.


Disable-PSRemoting blocks remote access to all session configurations on the local computer. This prevents remote users
 from creating temporary or persistent sessions to the local computer. Disable-PSRemoting does not prevent users of the
 local computer from creating sessions ("PSSessions") on the local computer or remote computers.


To re-enable remote access to all session configurations, use the Enable-PSRemoting cmdlet. To enable remote access to 
selected session configurations, use the AccessMode parameter of the Set-PSSessionConfiguration cmdlet. You can also us
e the Enable-PSSessionConfiguration and Disable-PSSessionConfiguration cmdlets to enable and disable session configurat
ions for all users. For more information about session configurations, see about_Session_Configurations (http://go.micr
osoft.com/fwlink/?LinkID=145152).


In Windows PowerShell 2.0, Disable-PSRemoting prevents all users from creating user-managed sessions ("PSSessions") to 
the local computer. In Windows PowerShell 3.0, Disable-PSRemoting prevents users on other computers from creating user-
managed sessions on the local computer, but allows users of the local computer to create user-managed "loopback" sessio
ns.


To run this cmdlet, start Windows PowerShell with the "Run as administrator" option.


CAUTION: On systems that have both Windows PowerShell 3.0 and the Windows PowerShell 2.0 engine, do not use Windows Pow
erShell 2.0 to run the Enable-PSRemoting and Disable-PSRemoting cmdlets. The commands might appear to succeed, but the 
remoting is not configured correctly. Remote commands, and later attempts to enable and disable remoting, are likely to
 fail.