Hi, The error message you've is quite explicit. It cannot find the "Microsoft.PowerShell" session configuration on the computer named COMPNAME.
The link you mentioned on powershell.com forum is a good one. You should check what sessions are available with the Get-PSSessionConfiguration cmdlet. As Aleksandar said, you'll need to register the missing sessions again with the Register-PSSessionConfiguration cmdlet. For the particular error message you've, doing the following on the computer COMPNAME should fix the issue: Register-PSSessionConfiguration -Name Microsoft.PowerShell On Mon, Mar 30, 2015 at 8:04 PM, Krueger, Jeff <[email protected]> wrote: > 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] > > 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 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 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
