Get started Bring yourself up to speed with our introductory content.

Hosted Exchange server management basics

Managing hosted Exchange servers may be in your near future. Now is the time to familiarize yourself with some basics of what you can and can’t manage.

Many organizations have already started outsourcing Exchange Server 2010 deployments to cloud service providers....

Still, Exchange admins are unclear on how to perform basic management tasks for Exchange in the cloud. Currently, there’s no standard for managing hosted Exchange servers, but here are some of the fundamentals.

Moving Exchange to the cloud does not have to be an all or nothing proposition.

Brien Posey, Contributor

In the Exchange Management Console (EMC) screenshot, you’ll notice that Exchange Server 2010 lists the selected node as Microsoft Exchange On-Premise (Figure 1). Microsoft designed the EMC for managing on-premise servers as well as cloud-based Exchange installations.

The on-premise portions of an Exchange organization are listed under the Microsoft Exchange On Premise node; Exchange servers located in the cloud are accessible in a separate node. Moving Exchange to the cloud does not have to be an all or nothing proposition. Exchange Server 2010 is actually flexible enough to allow you to keep some your servers on premise and host other Exchange servers in the cloud.

You can use the EMC to manage both on-premise and hosted Exchange servers
Figure 1. Exchange Management Console allows you to manage both on-premise and hosted Exchange servers.

EMC's design might lead you to believe that you can use it to manage cloud-based deployments; however, this is misleading. After moving to the cloud, Exchange organizations relinquish a large amount of control, allowing cloud service providers to decide how their customers manage the hosted Exchange servers. Many providers don't allow customers to use the EMC.

If admins can't manage Exchange via the Exchange Management Console, how do they manage hosted servers? The most common way is to use the host provider’s management proprietary tools.

I know of at least one cloud service provider that supplies customers with a proprietary Web interface for managing hosted Exchange servers. However, the company also allows customers to treat the hosted servers as a remote Exchange Server organization so they can perform more advanced management tasks.

This might sound a little odd, but Microsoft designed both the Exchange Management Console and the Exchange Management Shell (EMS) to be used for remote Exchange organization management.

If you look at Figure 2,you’ll notice that the Actions pane contains an option to Add an Exchange forest. With this option, EMC displays multiple forests simultaneously.

You can use the EMC to connect to remote Exchange organizations
Figure 2. You can use the Exchange Management Console to connect to remote Exchange organizations.

The Exchange Management Console is designed to manage up to 10 different forests at once. Some hosting vendors take advantage of this capability, allowing customers to manage Exchange through the EMC even though the servers reside in a remote forest.

Exchange Management Shell can also manage remote Exchange servers. The trick is to establish a remote PowerShell connection and define that connection as a variable. Here’s an example:

$rs = new-pssession -conf -conn http://CAS_SERVER_NAME/powershell -auth kerberos -cred (get-credential)

In this command, the $rs variable points to a remote PowerShell connection to http://CAS_SERVER_NAME/powershell. To run an EMS command against the remote system, you can use the Invoke-Command cmdlet with the name of the defined variable, for example:

Invoke-Command $rs {Get-Mailbox}

Nothing is set in stone when it comes to managing hosted Exchange servers. And since Exchange 2010 is still relatively new and many organizations are still waiting to migrate, hosting providers will likely give customers more consistent management methods as the cloud services market matures.

Brien M. Posey, MCSE, is a seven-time Microsoft MVP for his work with Windows 2000 Server, Exchange Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. For more information visit

Dig Deeper on Exchange Server setup and troubleshooting

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.