Skip to main content

Problem using Invoke-Command with Windows 7 client

By

While testing some code that used PowerShells Invoke-Command to send code to both Windows Server 2008 R2 and Windows 7, I discovered an inconsistency in the way Windows Remoting is applied to both platforms. The servers worked fine.  Even though I disabled to firewall for testing, I received this error when sending commands to the Windows 7 client:

 

[ClientName] Connecting to remote server failed with the following error message : The client cannot connect to the destingatoin specified in the request.  Verify that the service on the destination is running and is accepting requests.  Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.  If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service” winrm quickconfig”.  For more information, see the about_Remote_Troubleshooting Help topic.

+ CategoryInfo       : OpenError: (:) [], PSRemotingTransportException

+ FullyQualifiedErrorId : PSSessionStateBroken

The fix that I came up with was to deploy and Group Policy that allowed remoting and scope it to the client.

1. Open Group Policy Management console
2. Select the domain, and right-click the Default Domain Policy to edit it
3. Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Remote Management > WinRM Service
4. Allow automatic configuration of listeners, put * in the IPv4 and IPv6 filter text boxes
5. Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Remote Shell
6. Allow Remote Shell Access, Enabled
7. Save everything. Run Gpupdate on all servers that are currently running.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more