Installing and Using the Exchange Server 2013 Management Tools

With the release of the Exchange Server 2013 a lot of people in the Exchange community are talking about the big changes to the management tools.

Exchange Server 2013 no longer uses the MMC-based management console that we became familiar with in Exchange 2007 and Exchange 2010. Instead, the management console has been changed to a web-based management portal called the Exchange Admin Center.

In this video I take a quick look at the Exchange Admin Center.

For PowerShell-based administration we can still use the Exchange Management Shell, or just use PowerShell remoting. Remoting is simpler because it requires no management tools to be installed on the computer that you are connecting from. However you can still install the management shell on a workstation or server if you prefer.

To connect to a remote Exchange 2013 server using PowerShell you need to be running Windows 7 SP1, Windows 8 (or higher), Windows Server 2008 R2 SP1, or Windows Server 2012 (or higher).

From a PowerShell console run the following commands, using the FQDN of a Client Access server in your organization:

PS C:\> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex2013srv1.exchangeserverpro.net/PowerShell -Authentication Kerberos

PS C:\> Import-PSSession $session

If you need to provide different credentials for the connection use the following commands instead, and enter the credentials in the logon box that appears:

PS C:\> $creds = Get-Credential

PS C:\> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex2013srv1.exchangeserverpro.net/PowerShell -Authentication Kerberos -Credential $creds

PS C:\> Import-PSSession $session

You can exit the remote session by running the following command:

PS C:\> Remove-PSSession $session

If you’d prefer to install the management tools on the server, run the following setup command in an elevated command prompt from the folder containing the extracted Exchange 2013 setup files. This example is from a Windows Server 2012 R2 server.

C:\Admin\ex2013cu5>setup /m:install /r:t /InstallWindowsComponents /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 5 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Management tools

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Prerequisite Analysis                                     COMPLETED

Configuring Microsoft Exchange Server

    Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Language Configuration                                    COMPLETED
    Exchange Management Tools                                 COMPLETED
    Finalizing Setup                                          COMPLETED

The Exchange Server setup operation completed successfully.
About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Find Paul on Twitter, LinkedIn or Google+, or get in touch for consulting/support engagements.

Comments

  1. Chanchal says:

    Hi Paul,
    Really Nice. You are my Hero.

  2. interesting! atleast its will be quicker than MMC!!

    i noticed that it said office 365 in the top corner.. is that because MS are forcing you down the Hybrid route?

    i also see they have shelved the Hub transport role, is there still Transport Rules available?

  3. hi,

    what’s the benefit for Microsoft while removing Exchange management console…?

    • Not sure I understand the question.

      It makes sense to detach the Exchange management tools from a component like MMC, especially given some of the issues that have been caused with the Exchange management tools when other windows components were updated (the IE bug for example).

  4. David Smith says:

    Hi Paul,
    2 quick questions, 1 related to this video! You may want to move this question away from this topic?

    1. What do you feel that the main drivers will be for customers/users to move from their 2007/2013 platforms? apart from general Microsoft support. What, in your opinion, will be the key selling points to 2013.
    2. What software do you use to produce your videos?

    Keep up the good work, appreciated here in the UK.

    Regards,
    David
    p.s Ashes tickets bought yesterday!!!!

    New twitter account: msexchangeuk

    • 1) 2013 (and 2010 for that matter) have much better HA/SR capabilities than 2007 or earlier, and can save money due to the lower storage costs while also providing benefits such as large mailboxes. There are also a long list of improvements and new features such as DLP, builtin anti-malware, FAST search, deeper integration with products such as Lync and Sharepoint, and more. Microsoft publishes a lot of “whats new” material but some of the technical meat will emerge only as more and more customers deploy it and talk about it.

      2) I use Camtasia from Techsmith.

  5. what about roles ? can you explain some one what are all the roles using for exchange2013.

  6. Thanks for some other excellent post. The place else may anyone get that kind of information in such an ideal manner of writing?
    I have a presentation subsequent week, and I’m at the look for such info.

  7. Irakoze Clovis says:

    Hello Paul,

    I’m trying to log in Exchange Admin center but instead of getting “Exchange Admin Center” on the credentials page I’m getting “Outlook Web App”.Any clue?

    Thanks.

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.