WinRM cannot complete the operation

Question

_{Tuesday, July 23, 2013 12:23 PM}

I have been trying to deploy Microsoft Dynamics NAV on Windows Azure. Microsoft has gives few scripts which helps us deploy. While running the script I get the error :

"Get-WSManInstance : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859046" 
Machine="MyCompName"><f:Message>WinRM cannot complete the operation. Verify that the specified computer name is valid, 
that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this 
computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. 
</f:Message></f:WSManFault>"

WinRM Service is running and WinRM is also setup for Remote Management using the Enable-PSRemoting -force.

It would be helpful if anyone can suggest a solution.

All replies (4)

_{Wednesday, August 7, 2013 8:06 AM ✅Answered | 1 vote}

The issue was because of my office network. the same command worked fine in my home network. But I still want to make this command work in office network. 

Thanks Thom and Yen for answers.

_{Tuesday, July 23, 2013 1:25 PM}

Firewall exception or turned off?

Is the PC in the same domein? If not you need to add it to the trust list.

Can you resolve the PC name?

Run this on your target PC:

%windir%\system32\Configure-SMRemoting.exe -enable

http://technet.microsoft.com/en-us/library/hh921475.aspx#BKMK_ps

_{Wednesday, July 24, 2013 5:53 AM}

Hi,

Please read below article to understand more about PS remoting.

Understanding PowerShell Remote Management

http://blogs.technet.com/b/heyscriptingguy/archive/2012/12/30/understanding-powershell-remote-management.aspx

Hope that helps.

Regards,

Yan Li

Cataleya Li
TechNet Community Support

_{Wednesday, July 24, 2013 12:27 PM}

Hi Thom and Yan,

Thanks for your suggestions.

I have added the remote VM in trusted list.

Windows Remote Management program is allowed through Windows Fire Wall.

I have also enabled : Allow local port exceptions in "Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall\Domain Profile"

Still i'm getting same error.