Cloudy with a Chance of InsightsReaching for the Cloud NewsletterSubscribe to NewsletterSubscribe via RSS
The Microsoft Cloud Blog

Expert insights on Microsoft Azure, Cloud Architecture, and Enterprise Technology

1 min read
2013 PreviewExchange Server

Exchange 2013 Preview: Error connecting to server via PowerShell after installation

ShareLinkedInXBlueskyThreadsFacebook

After installing the pre-requisites and installing Exchange, when connecting to the exchange server using the Exchange Management Shell you may receive an error similar to the following.

“The WS-Management service does not support the request. For more information, see the about_Remote_Troubleshooting Help Topic”

It appears that the setup routine may not always register the .NET framework on IIS, so to get this to work you need to register .NET Framework 4 on IIS manually. To do this run the following command from an administrative command prompt.

%SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable

then restart IIS, this should solve the problem.

Want more cloud insights? Listen to Cloudy with a Chance of Insights podcast:

Spotify | YouTube | Apple Podcasts

Tags

Errors
Like this article?

Comments

Loading comments...

Richard Hogan - Global Chief Architect, Microsoft Practice

Richard Hogan

Global Chief Architect, Microsoft Practice | IBM

Global Chief Architect, Microsoft Practice at IBM. 20+ years experience working at the intersection of cloud architecture, security, and emerging AI capabilities across Azure and the wider Microsoft ecosystem. Host of the Cloudy with a Chance of Insights podcast. Regular speaker at tech conferences and active contributor to the Microsoft Tech Community.

LinkedInYouTubeMore About Me

You might also like

Error: New-AzResourceGroupDeployment: Cannot retrieve the dynamic parameters for the cmdlet. Cannot find path ‘.json’ because it does not exist.

I received the above error today whilst working on a new Bicep template which caused me a bit of confusion as it seemed to be indicating that a file was missing. What I figured out in the end is that it was really saying that I had messed up something in my Bicep template file… Continue Reading →

SharePoint 2013 Error: The filtering process has been terminated

I had just completed a PowerShell scripted deployment of a SharePoint farm and was just performing the final checks when I noticed the following error in the crawl logs. “The filtering process has been terminated” This turned out that because in the PowerShell script I had specified that the SharePoint installation location should be different to… Continue Reading →

Error message when you view an Outlook Web App Web Part in a SharePoint Online site in Office 365: “This content cannot be displayed in a frame”

Over the last couple of weeks I have been working on an Office 365 project, and whilst in general I have been impressed with the SharePoint aspects of Office 365.  There have been a couple of gotchas.  I will be positing a couple of articles dealing with these in more detail.  Anyway, I thought it would be… Continue Reading →

Cloudy with a Chance of Insights

Practical discussions on cloud engineering, architecture, and the reality behind the diagrams.

Reaching for the Cloud

Bi-weekly reflections on cloud architecture, Azure, and the decisions teams wrestle with in practice.

Get the newsletter by email →Follow along on LinkedIn →
← View All Posts