Professional Documents
Culture Documents
About Remote Troubleshooting - Help
About Remote Troubleshooting - Help
about_Remote_Troubleshooting
SHORT DESCRIPTION
Describes how to troubleshoot remote operations in Windows PowerShell.
LONG DESCRIPTION
This section describes some of the problems that you might encounter when
using the remoting features of Windows PowerShell that are based on
WS-Management technology and it suggests solutions to these problems.
Before using Windows PowerShell remoting, see about_Remote and
about_Remote_Requirements for guidance on configuration and basic use Also,
the Help topics for each of the remoting cmdlets, particularly the parameter
descriptions, have useful information that is designed to help you avoid
problems.
Updated versions of this topic, and other Windows PowerShell help topics,
can be found online in the Microsoft TechNet Library. To see the online
version of this help topic, paste the following URL in your Internet
browser:
http://go.microsoft.com/fwlink/?LinkID=135188
NOTE: On Windows Vista, Windows Server 2008, and later versions of Windows,
to view or change settings for the local computer in the WSMan: drive,
including changes to the session configurations, trusted hosts, ports, or
listeners, start Windows PowerShell with the "Run as administrator" option.
Note: In Windows Server 2008 R2, the Windows PowerShell icon is pinned
to the taskbar by default.
Set-Service cmdlet.
To run the command on multiple computers, you can create a text file or
CSV file of the computer names.
For example, the following commands get a list of computer names from the
Servers.txt file and then sets the startup type of the WinRM service on all
of the computers to Automatic.
C:\PS> $servers = get-content servers.txt
C:\PS> set-service WinRM -computername $servers -startuptype Automatic
To see the results use the Get-WMIObject cmdlet with the Win32_Service objec
t.
For more information, see Set-Service.
red
for remoting.
1. Configure the computer for HTTPS transport or add the names of the
remote computers to the TrustedHosts list on the local computer.
For instructions, see "How to Add a Computer to the TrustedHosts
List" below.
2. Verify that a password is set on the workgroup-based computer. If a
password is not set or the password value is empty, you cannot run
remote commands.
To set password for your user account, use User Accounts in Control
Panel.
3. Use the Credential parameter in all remote commands.
This is required even when you are submitting the credentials
of the current user.
To add all computers to the list of trusted hosts, use the following
command, which places a value of * (all) in the ComputerName
set-item wsman:localhost\client\trustedhosts -value *
You can also use a wildcard character (*) to add all computers in a
particular domain to the list of trusted hosts. For example, the following
command adds all of the computers in the Fabrikam domain to the list of
trusted hosts.
set-item wsman:localhost\client\trustedhosts *.fabrikam.com
To add the names of particular computers to the list of trusted hosts, use
the following command format:
set-item wsman:\localhost\Client\TrustedHosts -value <ComputerName>[,<Co
mputerName>]
where each value <ComputerName> must have the following format:
<Computer>.<Domain>.<Company>.<top-level-domain>
For example:
set-item wsman:\localhost\Client\TrustedHosts -value Server01.Domain01.F
abrikam.com
To resolve the error, change the remote command to comply with the quota.
Or, determine the source of the quota, and then increase the quota to allow
the command to complete.
For example, the following command increases the object size quota in the
Microsoft.PowerShell session configuration on the remote computer from 10 MB
(the default value) to 11 MB.
Set-PSSessionConfiguration -name microsoft.powershell `
-MaximumReceivedObjectSizeMB 11 -Force
For more information about the New-PSSsessionOption cmdlet, see
New-PSSessionOption.
For more information about the WS-Management quotas, see the Help topic for
the WS-Management provider (type "get-help WSMan").
For more information about the WS-Management timeouts, see the Help topic fo
r
the WS-Management provider (type "get-help WSMan").
For more information about the New-PSSsessionOption cmdlet, see
New-PSSessionOption.
TROUBLESHOOTING UNRESPONSIVE BEHAVIOR
This section discusses remoting problems that prevent a command from completing
and prevent or delay the return of the Windows PowerShell prompt.
HOW TO INTERRUPT A COMMAND
-------------------------Some native Windows programs, such as programs with a user interface, consol
e
applications that prompt for input, and console applications that use the
Win32 console API, do not work correctly in the Windows PowerShell remote ho
st.
When you use these programs, you might see unexpected behavior, such as no
output, partial output, or a remote command that does not complete.
To end an unresponsive program, type CTRL + C. To view any errors that might
have been reported, type "$error" in the local host and the remote session.
SEE ALSO
Online version: http://go.microsoft.com/fwlink/?LinkID=135188
about_remote
about_remote_requirements