Powershell to local server install of CAS HT will not start correctly. Exchange 2010

Hi

When I try to start powershell on a 2010 CAS HT server I get the following when trying to connect to the local powershell, not remote.

I have re-built the server with a new name, WinRM is installed.  The server is R@ 2008 exchange is running rolluo2.

VERBOSE: Connecting to xxxxxxx.cc.ooo.au
[SERVER] Connecting to remote server failed with the following error message : The WinRM client cannot pr
ocess the request. It cannot determine the content type of the HTTP response from the destination computer. The content
 type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed


VERBOSE: Connecting to WMEXCASHT3.wm.org.au
[wmexcasht3.wm.org.au] Connecting to remote server failed with the following error message : The WinRM client cannot pr
ocess the request. It cannot determine the content type of the HTTP response from the destination computer. The content
 type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed

Anyone know how to get powershell starting correctly?

Peter
LVL 4
PeterSingerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PeterSingerAuthor Commented:
The second one does not apply it is running 2008 R2.  I have already seen the first one with no help.
0
Shreedhar EtteCommented:
Hi,

Refer this:
http://technet.microsoft.com/en-us/library/dd298084.aspx

Hope this helps,
Shree
0
PeterSingerAuthor Commented:
Would the permissions to run powershell not be domain wide?  The suer "Administrator" in this case can run it from any other server fine except this one.  It can also connect to another server and use it fron from this server.  It is only when it trys to accwess the local server that it fails.
0
PeterSingerAuthor Commented:
I resolved this issue by the following;
1. Go to Server Manager / Features
2. Remove the IIS WinRM IIS Extention Feture
3. Reboot the server
4. Go to Server Manager / Features
5. Install the IIS WinRM IIS Extention Feture
6. reboot the server
7. Open a os opt not a powershell prompt as admistra
8. run winrm quickconfig
Done


 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.