Error “Failed To Connect To An Exchange Server In The Current Site” While Running Exchange 2013 Shell

MS Exchange

I received an email today from an Exchange admin who is testing 2013 Preview & is stuck with the error mentioned while running the 2013 Shell.

The detailed error is as follows.

VERBOSE: Connecting to
New-PSSession : [] Connecting to remote server failed with the following error message : The WS-Management service does not support the request. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : WinRMOperationNotSupportedOnServer,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

The fix is to run one of the prerequisite steps for installing Exchange 2013.

From an elevated command prompt, run the following.

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

This step is required to register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS).

Exchange admins get all excited about installing the latest version and miss the steps ;)

Other Popular Articles

MS Exchange

Keep Track Of Exchange 2013 Database Failovers

MS Exchange

Playing With Exchange 2013 Performance Logs

MS Exchange

Tackle .Net Framework 4.6.1 On Exchange Servers

  1. Hi Rajith I have the dame problem.
    With Win server 2012 and MS EXCHANGE 2016.
    Also in the server Exchange the DNS IP on the ethernet adapter , change to and in automatic
    What Happen?
    My mail service is stop.

    Mario Borges

  2. Hi Rajith,

    Thanks for your article on this issue.
    I followed it but getting still getting the error:

    “New-PSSession : [] Connecting to remote server failed with the
    following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic”

    I have 2 Ex2013 CAS servers and 2 MBX servers (all 2013 – SP1 – CU7) on Win 2008 R2 SP1.

    Followed the article –

    The Powershell site (in IIS under Default Web site) is pointing to the right directory.

    D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell

    But on clicking the “Test Settings” button it gives an error “Invalid application path”.

    If I click on “connect As” and putin my same login credentials the “Test settings” is success !!

    Pls help.

    Many thanks,


    • I JUST got off the phone with Microsoft, and this problem (for ME) was all
      because the PDC and the Exchange Server were NOT “TIME synchronized”!!!
      IF the Exchange Server is OFF by 6+ minutes THEN you will have this problem
      as well as EMAIL to the Outside WILL STOP!

      This article
      provided my answer. (My PDC had ALREADY been configured to use an
      “authoritative Time”, but apparently all my other Servers were NOT being
      told to “Look to the PDC for your TIME”.
      ON ALL your DCs and ALL your Servers, open a “Command Prompt (Admin)
      and type the , type the following 3 lines (hitting enter after each
      command): (each one will take a second or 2 to complete)

      w32tm /config /syncfromflags:domhier /update (Enter)
      net stop time (Enter)
      net start time (Enter)

      Do ALL the DCs FIRST, then do the Exchange Server.

      Then you MUST reboot the Exchange Server for this to have an effect
      for Exchange. After Rebooting and waiting until ALL the services
      have come back up, I was again able to open “Exchange Management Shell”
      and “Exchange Toolbox”!

      Hope this helps someone!

  3. I’m running Windows 2012 Standard with IIS 6 came with the HP server base install and the command to install 4.5 simply lists the available options and does nothing and I continue to get errors trying to run the management shell of not being able to connect.

    Should I upgrade IIS to 7 or 8 first? The cert errors are showing up for users so I have to either shutdown this box asap or fix it

    Please advise! Thanks!!

  4. I am also Exchange 2013 with Server 2012 with the same problem.

    New-PSSession : [] Connecting to remote server failed with
    the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    • Hi Steve,

      What build of Exchange 2013 are you using? This used to be an issue in 2013 Preview. RTM, CU1 and CU2 should work fine.
      Is Windows 2012 fully patched? If not, please do that.

  5. hi

    I have exactly the same issue and it looks like that this is the only answer all over the web but it is not helping me

    i run this command for Microsoft (R) ASP.NET RegIIS version 4.0.30319.17929 and this is what i am reciveing

    Microsoft (R) ASP.NET RegIIS version 4.0.30319.17929
    Administration utility to install and uninstall ASP.NET on the local machine.
    Copyright (C) Microsoft Corporation. All rights reserved.
    Start installing ASP.NET (4.0.30319.17929) without changing existing web applica
    tions to use this version of ASP.Net.
    This option is not supported on this version of the operating system. Administr
    ators should instead install/uninstall ASP.NET 4.5 with IIS8 using the “Turn Win
    dows Features On/Off” dialog, the Server Manager management tool, or the dism.e
    xe command line tool. For more details please see
    Finished installing ASP.NET (4.0.30319.17929) without changing existing web appl
    ications to use this version of ASP.Net.

    i also run
    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -ir -enable
    but this time i am reciving this :

    Start installing ASP.NET (2.0.50727).
    An error has occurred: 0x80004005 Unspecified error


    any suggestion ?


Leave a Comment

Disable Windows Copilot Using Intune

Windows Copilot is Microsoft’s take on making life easier for Windows users using the power of AI. This article explains how to disable the feature using Intune, if your organization is not ready yet to walk into the AI world.

Disable Windows Copilot Using Intune

We need to create a Configuration Profile for Windows devices in the Intune portal to disable Windows Copilot. Below are the steps that we need to create the profile.

Launch the Intune Portal and login as a Global Admin or Intune Admin.

Navigate to Devices -> Windows -> Configuration Profiles.

Windows Configuration Profile Intune

Click on Create -> New Policy.

Select Windows 10 & later as the platform and Settings Catalog as the profile type & click on the Create button.

Settings Catalog Intune CoPilot

Give the policy a meaningful name & description and click Next.

Policy Name Disable CoPilot

Within the configuration settings, click on the Add Settings option.

Add Settings Disable CoPilot

Search for ‘copilot’, Windows AI will come up as the category. Click on Windows AI and the Turn off Copilot in Windows (User) setting will come up. Check the box and click Next.

Turn off CoPilot Setting Intune
Turn off CoPilot Setting Intune Summary 1

Specify scope tags if required and click Next.

Select tags CoPilot Intune

Select who this policy should apply to in the Assignments section. I have selected to add all users. If you want to test the setting, you can create a test group and select that group here.

Similarly, you can also exclude certain group from disabling AI (say IT team) if required.

Add all users disable copilot intune

A summary of selected settings will be displayed. Click on the Create button to setup the policy to disable Windows Copilot.

Create configuration policy disable CoPilot Intune 1

Wait for the replication to complete in the cloud backend and login to your machine. Your chatty Copilot should now be disabled.

Disable Windows Copilot On Windows 11 Pro

Follow the steps below to disable Copilot on a personal Windows 11 Pro machine (say your own laptop).

Search for ‘group’ in Windows 11 and click on Edit Group Policy option.

Group Policy Windows 11 Disable Copilot

Navigate to User Configuration -> Administrative Templates -> Windows Components -> Windows Copilot.

Windows Copilot GPO setting

Double click on Turn off Windows Copilot setting on the right pane.

Select Enabled and click OK.

Turn off copilot gpo Windows 11 Pro 1

Close the Group Policy Editor. This will disable Windows Copilot on a Windows 11 Pro machine.


We have learned to disable Windows Copilot using Intune and Group Policy on Windows 11 machines.

Please let me know if you have any questions in the comments section.

Promote Windows Server 2025 To Domain Controller

Domain controllers are the backbone of any Active Directory domains in the Microsoft world. Any Windows server can be promoted to be a domain controller. In this article, we will go through the steps of promoting a Windows 2025 Server to be a domain controller.

Windows Server 2025

The latest version of the server operating system has been named Windows Server 2025. You can start with a 2025 Server & create an AD domain or you can promote a member server that is already a part of a domain.

The Windows Server 2025 needs to be installed on a machine before it can be promoted to be a domain controller.

Promote Windows Server 2025 To Domain Controller

If you have been working with Windows servers long enough, everything starts with the Server Manager app. Promoting a server to a domain controller is no different.

Launch ‘Server Manager’ & click on Add roles and features.

Windows 2025 Server Manager

You land on the summary page that explains what is required to run this wizard successfully. Click Next.

Windows Server 2025 Add Remove Roles

Select Role-based or Feature-based installation and click Next.

Windows Server 2025 Role Based Install

Select the server that needs to be promoted and click Next.

Windows Server 2025 Destination Server

Select Active Directory Domain Services (second option) and click on Add Features.

Windows Server 2025 AD Domain Services

Go with the default options for features that need to be installed.

Windows Server 2025 AD Domain Services Features

A summary of AD DS pops up next, click next to continue.

Windows Server 2025 AD DS

Select Restart the server automatically if required and click Install.

Windows Server 2025 AD Restart Server

You get to keep an eye on the progress of the installation.

Windows Server 2025 AD Install Progress

Once the role has been installed, you will find an exclamation mark on the top right corner of the Server Manager. Click on that and select Promote this server to be a domain controller.

Windows Server 2025 AD Install Continue

You get an error straight away (which you have never seen before) – Error determining whether the target server is already a domain controller. Role change is in progress or this computer needs a restart.

Windows Server 2025 Domain Controller Setup Error

We never needed to restart the server after installing the role in the DC promotion process. Given that it is an insider build of Server 2025, I am hoping that this will get fixed before the public release.

Restart the server, launch Server Manager and click on the Promote this server to be a domain controller option again.

Windows Server 2025 AD Install Continue 1

I am setting up a brand new AD forest and hence I select the third option (Add a new forest) and enter my root domain name.

Windows Server 2025 Add a forest

Next window brings the option to set your forest & domain functional level and the DSRM password. In the insider build, it shows what looks like a variable (the Windows server version on which the you are working).

Windows Server 2025 Forest Functional Level

You can leave the default options in the DNS options wizard and click next.

Windows Server 2025 DNS Options

Enter the netbios name of the domain in the next window and click next.

Windows Server 2025 Netbios Domain Name

You can stick with the default paths for the AD database, log & sysvol folder or pick a location of your choice.

Windows Server 2025 AD Paths

Review the selections that you have made so far and click next.

Windows Server 2025 Options Review

Wait for the green check mark on the prerequisites page and click next.

Windows Server 2025 Pre reqs Check

Click Install in the final window & wait for the magic to happen. Once the machine gets restarted (which it will do automatically), you will have a brand new domain controller based on Windows Server 2025.

Windows Server 2025 AD Snap In


Promoting a Server 2025 to a domain controller follows pretty much the same steps as previous operating systems. The Insider build has few errors that needs to be fixed, but hey, it is an insider build!

Please let me know if you have any questions in the comments section.

Install Windows Server 2025 – Full Guide

Microsoft has released an insider preview of it’s next server operating system named Windows Server 2025. We will have a look at the installation steps involved in setting up a 2025 server.

Windows Server 2025

Microsoft has gone with the same look and feel of Windows 11 operating system in it’s current server operating system – Windows Server 2025. As the product is in insider preview, there might be slight changes before it hits the public shelves.

It is refreshing to see a ‘modern’ feel in the installation process of a server operating system. Gone are the days where the installation of a consumer based OS felt much better compared to it’s server counterpart.

Installing Windows Server 2025

Let’s take a look at the steps involved in setting up a Windows Server 2025 machine. First step is to download the ISO from the Windows Insider portal.

Next step is to boot the virtual / physical machine from the ISO which will kick off the installation of Server 2025.

First option to select is the language settings. Pick the one based which relates to you and click next.

Windows Server 2025 language settings

Select the keyboard settings in the next screen and click next.

Windows Server 2025 keyboard

You get the option to select whether you want to Install Windows Server or Repair the installation. The bottom left corner also has the option to go to the previous version of setup.

Windows Server 2025 setup option

You are asked to enter the product key, which is available in the Windows Insider portal.

Windows Server 2025 product key

Next option to choose is the type of image you want to install – Windows 2025 core or full blown desktop experience.

Windows Server 2025 Desktop

You need to agree to the licensing terms to move forward in the next step.

Windows Server 2025 Agreement License

Select the partition on which the server OS should be installed and click next. You also have the option to slice the partitions the way you see fit in the same screen.

Windows Server 2025 Disk Partitions

The Ready to Install window comes up, click the install button.

Windows Server 2025 Install 1

Installation of Server 2025 is underway and you get to see the progress.

Windows Server 2025 Install Progress

Once the installation is complete, you need to enter an administrator password of your choice to finalize the setup.

Windows Server 2025 Password

And there you go! You see a Windows 11 login screen staring at you ;-)

Windows Server 2025 Login Screen

After logging in, you get to set the options around sending diagnostic data to Microsoft, which I always set as ‘required only’.

Windows Server 2025 Diagnostic Data

The Windows Server 2025 desktop looks similar, doesn’t it? ;-)

Windows Server 2025 Desktop Feel scaled

Now that the server is up and running, you can promote it to be a domain controller.


The Windows Server 2025 has the same look and feel as a Windows 11 operating system. The installation options also provide that modern ‘feel’ and makes it a bit soothing to the eyes!

Please let me know if you have any questions in the comments section.