You can reregister the library:
psexec \\<computername> powershell -noprofile -command
register-pssessionconfiguration microsoft.powershell -force
OR
winrs /r:<computername> powershell -noprofile -command
{register-pssessionconfiguration microsoft.powershell -force}
OR you can specify the config library when you start pssession:
Enter-PSSession -ComputerName <computername> -ConfigurationName
microsoft.powershell
From: [email protected] [mailto:[email protected]] On
Behalf Of Sherry Kissinger
Sent: Monday, March 30, 2015 2:44 PM
To: [email protected]
Subject: Re: [powershell] RE: PowerShell remoting not working after upgrade to
WMF 4.0 from 2.0
There's some elements in here:
http://mnscug.org/blogs/sherry-kissinger/299-compliance-setting-to-enable-winrm
which are only applicable if you're powershell 3 or higher.
specifically, it checks the results of this:
cd WSMan:\localhost\Service
(Get-ChildItem AllowremoteAccess).value
is equal to True. If not, (if remediation is enabled on the Baseline) it
re-runs winrm quickconfig.
On Monday, March 30, 2015 1:13 PM, Donnie Taylor
<[email protected]<mailto:[email protected]>> wrote:
Ports open? 5985 and 5986 are the new ports for remoting.
From: [email protected] [mailto:[email protected]] On
Behalf Of Krueger, Jeff
Sent: Monday, March 30, 2015 1:04 PM
To: [email protected]
Subject: [powershell] PowerShell remoting not working after upgrade to WMF 4.0
from 2.0
After upgrading a machine from WMF 2.0 to WMF 4.0 we are having problems with
using powershell remotely on that machine. Getting the following error:
[COMPNAME] Connecting to remote server RH711766 failed with the following error
message : The WS-Management service cannot process the request. Cannot find the
Microsoft.PowerShell session configuration in the
WSMan: drive on the COMPNAME computer. For more information, see the
about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (COMPNAME:String) [],
PSRemotingTransportException
+ FullyQualifiedErrorId : InvalidResourceUri,PSSessionStateBroken
We’re experiencing the exact same issue as described in this post
http://powershell.com/cs/forums/t/11825.aspx?PageIndex=1 , that one was going
from 2.0 to 3.0. We have enabling WinRM configured in GPO.
Jeff Krueger
[email protected]<mailto:[email protected]>
IT - Henry Ford Health System
248.853.4466
________________________________
CONFIDENTIALITY NOTICE: This email contains information from the sender that
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected
from disclosure. This email is intended for use only by the person or entity to
whom it is addressed. If you are not the intended recipient, any use,
disclosure, copying, distribution, printing, or any action taken in reliance on
the contents of this email, is strictly prohibited. If you received this email
in error, please contact the sending party by reply email, delete the email
from your computer system and shred any paper copies.
Note to Patients: There are a number of risks you should consider before using
e-mail to communicate with us. See our Privacy & Security page on
www.henryford.com<http://www.henryford.com/> for more detailed information as
well as information concerning MyChart, our new patient portal. If you do not
believe that our policy gives you the privacy and security protection you need,
do not send e-mail or Internet communications to us.
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
Nothing in this message is intended to constitute an electronic signature
unless a specific statement to the contrary is included in this message.
Confidentiality Note: This message is intended only for the person or entity to
which it is addressed. It may contain confidential and/or privileged material.
Any review, transmission, dissemination or other use, or taking of any action
in reliance upon this message by persons or entities other than the intended
recipient is prohibited and may be unlawful. If you received this message in
error, please contact the sender and delete it from your computer.
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be
used for urgent or sensitive issues
================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1
