Good day to all

There is the  corporate Exchange 2013 server in main office  and  local Windows 8 (and 8.1 too) and Windows 7 Enterprise workstations in regional office in one AD domain.

I am local admin in this regional office and one of my duty is work with my part of Exchange accounts. So I do it with PowerShell Win ISE environment .

I make initial connect to Exchange server by this script (running in Win ISE with admin rights)

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://exchange.server/PowerShell/ -Authentication Kerberos -Credential $UserCredential
Import-PSSession $Session

 

On Windows 8 WS it issued an error with a such strange message :

---------------------------------------------------------------------------------------------------------------

New-PSSession : [exchange.server] Connecting to remote server exchange.server  failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.

------------------------------------------------------------------------------------------------------------------

But if I try to run this script on Windows 7 Ent workstation in a same environment (Win ISE) I  havent got any errors and I can to connect with corporate server.

All of these workstations (Win 8, Win 7 ), have got  same versions of PS (4.0) .  There is no firewalls between server ans workstations . Local firewall on Win 8 WS disabled .

Because I am local admin  I can't  rule by the  Exchange Server console, accordingly to corporate policy. I cant reach it anymore . But I think that problem is deep in Win 8 settings.

So why I can't connect to ES from Win8 ? Any help would be appreciated .

Thanks again.

Hi,

Since it works fine with same command in Windows 7, this issue may be caused by Windows 8.1 client side.
According to the error message, I find an blog for Exchange server side. For your reference:
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

Just in case, please open IIS manager and switch to Default Web Site. Right-click Default Web Site, and then click Edit Bindings to double check the configuration for HTTP:
1. Make sure the value of Hostname is empty.
2. Ensure the port is 80.
For your question, I have test this command in Windows 8, it works fine.
Is there any extra software installed on it? please try to run Windows with clean boot, also we can try this within a new Windows.

Besides, please try to telnet port 5985 and manually open this port in firewall ports.

Allen, thank for the answer

1. It is impossible to make changes on  the Exchange server side (I havent got enough rights as an local admin) .

2. I can reach Exchange server from  Win 8.1 WS by telnet . No problem , all works fine.

3.Yes I have got a lot of soft installed at Win 8.1 , so I will try to follow with your  hints and  make connection from out-of-the-box Win 8.1 WS to Exchange server.

Thanks for advices

Andrew

• Edited by Andrew Wereshchaka 20 hours 52 minutes ago

Allen, thank for the answer

1. It is impossible to make changes on  the Exchange server side (I havent got enough rights as an local admin) .

2. I can reach Exchange server from  Win 8.1 WS by telnet . No problem , all works fine.

3.Yes I have got a lot of soft installed at Win 8.1 , so I will try to follow with your  hints and  make connection from out-of-the-box Win 8.1 WS to Exchange server.

Thanks for advices

Andrew

• Edited by Andrew Wereshchaka Friday, April 03, 2015 10:31 AM

Hi,

Any updates about this question?
Besides, please do it in another fresh Windows 8 Workstation for testing.

Thanks

Hi Allen !

Here is the news 8-) Fresh installation either 8 or 8.1 issued no errors 8-)

So there will be  some troubles in error finding in a heap of software and their settings 8-)

Thanks to  You . Really error is on my side, something wrong on 8.1 setings.

So the issue has decided by full reinstall OS . It is hard to say clearly about source of this issue . But now I have no problem. So thanks for advices and patience 8-)