Note: This article was originally published in 2013. Some steps, commands, or software versions may have changed. Check the current Exchange documentation for the latest information.

In this step-by-step guide, you’ll learn add your license key to an exchange server 2007 or 2010. Microsoft Exchange Server is a mail server and calendaring server developed by Microsoft, used for enterprise email, calendar, contacts, and task management.

Prerequisites

Before you begin, make sure you have:

  • Exchange Server installed and configured
  • Administrative access to Exchange Management Console/Shell
  • Active Directory environment

How to: Add your license key to an (http://www.microsoft.com/exchange “Microsoft Exchange Server”) or Exchange Server 2010 via de (http://en.wikipedia.org/wiki/Command-line_interface “Command-line interface”)

You can easily add your license key via the (http://en.wikipedia.org/wiki/Graphical_user_interface “Graphical user interface”) on Exchange Server, however, sometimes you need to do this via the terminal window. In order to do this you simply need to fun the following command :

set-exchangeserver -Identity ‘ServerName’ -ProductKey xxxx-xxxx-xxxx-xxxx-xxxx

Below is an example of what the GUI actually executes in order to accomplish this: Summary: 1 item(s). 1 succeeded, 0 failed. Elapsed time: 00:00:12 EXCHANGE-2010 Completed Warning: The (http://en.wikipedia.org/wiki/Product_key “Product key”) has been validated and the product ID has been successfully created. This change won’t take effect until the Information Store service has been restarted. Exchange Management Shell command completed: set-exchangeserver -Identity ‘EXCHANGE-2010’ -ProductKey xxxx-xxxx-xxxx-xxxx-xxxx Elapsed Time: 00:00:12

(http://img.zemanta.com/zemified_h.png?x-id=4840c744-1f67-425b-a395-27a0caaf33b0)](http://www.zemanta.com/?px “Enhanced by Zemanta”)

Summary

You’ve successfully learned add your license key to an exchange server 2007 or 2010. If you run into any issues, double-check the prerequisites and ensure your Exchange environment is properly configured.