Exchange 2013 RTM Install – Is RSAT Clustering CmdInterface Required?

While upgrading Exchange 2013 RTM to CU1, I was surprised to see that the setup picks up that the RSAT Clustering CmdInterface was not installed. I thought that was a prerequisite for 2013 RTM! Let me run through the way I installed 2013 RTM so that it makes more sense. First step was to install…

While upgrading Exchange 2013 RTM to CU1, I was surprised to see that the setup picks up that the RSAT Clustering CmdInterface was not installed. I thought that was a prerequisite for 2013 RTM!

Let me run through the way I installed 2013 RTM so that it makes more sense. First step was to install the Desktop Experience.

Install Desktop Experience

Then I was able to install the Unified Communication Managed API 4.0

UCMA

I made use of the option in the 2013 setup to install the windows features it needed.

Install required features 2013 setup

2013 RTM got installed successfully. But, the setup doesn’t install RSAT Clustering Commandline interface for some reason and it looks like it is not a prereq for installing 2013 RTM.

Features installed as part of Exchange 2013 setup

TechNet clearly states it as a prereq though.

Technet Prereqs

But, while upgrading to 2013 CU1, setup failed with an error that the RSAT Clustering Cmdline Interface needs to be installed.

Error while upgrading Exchange 2013 to CU1 

I installed the Clustering Cmdline Interface and the 2013 CU1 setup went ahead and completed successfully.

Install clustering cmdline interface

Anyone else encountered the same issue?

4 Comments

  1. And yet again CU2v2 is here and still the same error with very little availbale info as to why it is as such. One could speculate, but no real hard core answer from MS as to why detect it as a prereq.

    1. Rajith Jose Enchiparambil says:

      Fun and games Akr ;-)

  2. Jean-François FLAVIEN says:

    Yes. I encountered the same issue and use the same resolution than yours.

    1. Rajith Jose Enchiparambil says:

      Thanks Jean-Francois. Looks like MS needs to fix it.

Leave a Reply

Your email address will not be published. Required fields are marked *