Install Exchange Server 2010 RTM – Step by Step

Hi, i write this post with the step by step to install Exchange Server 2010 RTM

Install the Windows Server 2008 R2 operating system prerequisites

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack

http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en

1. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

2. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

Restart

3. After the system has restarted, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:

Set-Service NetTcpPortSharing -StartupType Automatic

Prepare Active Directory

http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx

Prerequisites

• Your domains and the domain controllers must meet the system requirements in the "Network and Directory Servers" section of Exchange 2010 System Requirements.
• In each domain in which you will install Exchange 2010, you must have at least one domain controller running Windows Server 2003 Service Pack 1 (SP1).
• If you are running the release to manufacturing (RTM) version of Exchange 2010 Setup.com, in each domain (including child domains) where you have the Exchange Enterprise Servers and Exchange Domains Servers security groups and therefore must run Setup /PrepareLegacyExchangePermissions, you must have at least one domain controller running Windows Server 2003 SP1 or a later version.
• If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domains by using a computer running Windows Server 2008, you must first install the Active Directory management tools on the Windows Server 2008 computer prior to preparing the schema or domains. To do this, run the following command.

ServerManagerCmd -i RSAT-ADDS

• The computers on which you will install Exchange 2010 must meet the system requirements. For details, see Exchange 2010 System Requirements.

Prepare Active Directory and domains

1. If you have any computers in your organization running Exchange 2003, open a Command Prompt window, and then run one of the following commands:
   • To prepare legacy Exchange permissions in every domain in the forest that contains the Exchange Enterprise Servers and Exchange Domain Servers groups, run the following command.
     setup /PrepareLegacyExchangePermissions.or setup /pl
   • To prepare legacy Exchange permissions in a specific domain, run the following command.
     setup /PrepareLegacyExchangePermissions: < FQDN of domain you want to prepare > or setup /pl:<FQDN of domain you want to prepare>

Note:

You can skip this step and prepare the legacy Exchange permissions as part of Step 2 or Step 3. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

1. Note the following:
   • To run this command to prepare every domain in the forest, you must be a member of the Enterprise Admins group. To run this command to prepare a specific domain, or if the forest has only one domain, you must be delegated the Exchange Organization Management role, and you must be a member of the Domain Admins group in the domain that you will prepare.
   • If you don't specify a domain, the domain in which you run this command must be able to contact all domains in the forest. If the server can't contact a domain that must have legacy Exchange permissions prepared, it prepares the domains that it can contact, and then returns an error message that it was unable to contact some domains.
   • You can run this command from any 64-bit Windows Server 2003 SP1 server in the forest.
   • You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency. For information on how to identify the schema master, see Identify the schema master. To change site membership for the schema master:

5. For information on how to transfer

o After you run this command, you must wait for the permissions to replicate across your Exchange organization before continuing to the next step. If the permissions haven't replicated, the Recipient Update Service on your Exchange Server 2003 computers could fail. The amount of time that replication takes depends on your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Microsoft Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

1. For detailed information about the permissions set by this command, see Preparing Legacy Exchange Permissions.

From a Command Prompt window, run the following command.
setup /PrepareSchema or setup /ps

Note:

You can skip this step and prepare the schema as part of Step 3.

Important:

You must not run this command in a forest in which you don't plan to run setup /PrepareAD. If you do, the forest will be configured incorrectly, and you won't be able to read some attributes on user objects.

Note:

It isn't supported to use the LDIF Directory Exchange tool (LDIFDE) to manually import the Exchange 2010 schema changes. You must use Setup to update the schema.

This command performs the following tasks:

o Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2010 specific attributes. The LDIF files are copied to the Temp directory, and then deleted after they are imported into the schema.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step.

Note the following:

o If you want to verify the updates to the schema before the changes are replicated to other servers in the domain, you must disable outbound replication on the computer on which you run the command before you run it, and then enable outbound replication after you have verified that the import completed successfully.

o To run this command, you must be a member of the Schema Admins group and the Enterprise Admins group.

o You must run this command on a 64-bit computer in the same domain and in the same Active Directory site as the schema master.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o If you use the /DomainController parameter with this command, you must specify the domain controller that is the schema master.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

For more information, see Exchange Server Changes to the Active Directory Schema.

From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName: <organization name> ] or setup /p [/on:<organization name>]
This command performs the following tasks:

o If the Microsoft Exchange container doesn't exist, this command creates it under CN=Services,CN=Configuration,DC=<root domain>.

o If no Exchange organization container exists under CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain >, you must specify an organization name by using the /OrganizationName parameter. The organization container will be created with the name that you specify.
The Exchange organization name can contain only the following characters:
A through Z
a through z
0 through 9
Space (not leading or trailing)
Hyphen or dash
The organization name can't contain more than 64 characters. The organization name can't be blank. If the organization name contains spaces, you must enclose the name in quotation marks.

o Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<your organization>, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container. The objectVersion value for the RTM version of Exchange Server 2007 is 10666.

o If they don't exist, creates the following containers and objects under CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>. These are required for Exchange 2010.
CN=Address Lists Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Addressing,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Client Access,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Connections,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Folders Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Global Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Mobile Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Recipient Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=System Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM AutoAttendant,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM DialPlan,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM IPGateway Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>

o If it doesn't exist, creates the default Accepted Domains entry, based on the forest root namespace, under CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

o Assigns specific permissions throughout the configuration partition.

o Imports the Rights.ldf file. This adds the extended rights required for Exchange to install into Active Directory.

o Creates the Microsoft Exchange Security Groups organizational unit (OU) in the root domain of the forest and assigns specific permissions on this OU.

o Creates the following universal security groups (USGs) within the Microsoft Exchange Security Groups OU:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange Servers
Exchange View-Only Administrators
Exchange Public Folder Administrators (New in Exchange Server 2007 Service Pack 1)
ExchangeLegacyInterop

o Adds the new USGs that are within the Microsoft Exchange Security Groups OU to the otherWellKnownObjects attribute stored on the CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> container.

o Creates the Unified Messaging Voice Originator contact in the Microsoft Exchange System Objects container of the root domain.

o Prepares the local domain for Exchange 2010. For information about what tasks are completed to prepare a domain, see Step 4.

Note the following:

o To run this command, you must be a member of the Enterprise Admins group.

o The computer where you run this command must be able to contact all domains in the forest on port 389.

o You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency.

o If you haven't completed Step 1, setup /PrepareAD will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. If you are also a member of the Schema Admins group, and if you haven't completed Step 2, setup /PrepareAD will automatically perform the PrepareSchema step. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology. 

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it is located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

o To verify that this step completed successfully, make sure that there is a new OU in the root domain called Microsoft Exchange Security Groups. This OU should contain the following new Exchange USGs:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange View-Only Administrators
Exchange Servers
Exchange Public Folder Administrators (new in Exchange 2007 SP 1)
ExchangeLegacyInterop

From a Command Prompt window, run one of the following commands:

o Run setup /PrepareDomain or setup /pd to prepare the local domain. Note that you don't need to run this in the domain where you ran Step 3. Running setup /PrepareAD prepares the local domain.

o Run setup /PrepareDomain:<FQDN of domain you want to prepare> to prepare a specific domain.

o Run setup /PrepareAllDomains or setup /pad to prepare all domains in your organization.

These commands perform the following tasks:

o Sets permissions on the domain container for the Exchange Servers, Exchange Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators.

o If this is a new organization, creates the Microsoft Exchange System Objects container in the root domain partition in Active Directory and sets permissions on this container for the Exchange Servers, Exchange Organization Administrators, and Authenticated Users. This container is used to store public folder proxy objects and Exchange-related system objects, such as the mailbox database's mailbox.

o Sets the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain>. This objectVersion property contains the version of domain preparation. The version for Exchange 2007 RTM is 10628.

o Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain.

Note:

The Exchange Install Domain Servers group is used if you install Exchange 2010 in a child domain that is an Active Directory site other than the root domain. The creation of this group allows you to avoid installation errors if group memberships haven't replicated to the child domain.

o Assigns permissions at the domain level for the Exchange Servers USG and the Exchange Recipient Administrators USG.

Note the following:

o For domains that are in an Active Directory site other than the root domain, /PrepareDomain might fail with the following messages:
"PrepareDomain for domain <YourDomain> has partially completed. Because of the Active Directory site configuration, you must wait at least 15 minutes for replication to occur, and run PrepareDomain for <YourDomain> again."
"Active Directory operation failed on <YourServer>. This error is not retriable. Additional information: The specified group type is invalid.
Active Directory response: 00002141: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0
The server cannot handle directory requests."
If you see these messages, wait for or force Active Directory replication between this domain and the root domain, and then run /PrepareDomain again.

o To run setup /PrepareAllDomains, you must be a member of the Enterprise Admins group.

o To run setup /PrepareDomain, if the domain that you are preparing existed before you ran setup /PrepareAD, you must be a member of the Domain Admins group in the domain. If the domain that you are preparing was created after you ran setup /PrepareAD, you must be a member of the Exchange Organization Administrators group, and you must be a member of the Domain Admins group in the domain.

o You must run this command in every domain in which you will install Exchange 2007. You must also run this command in every domain that will contain mail-enabled users, even if the domain doesn't have Exchange 2007 installed.

To verify that this step completed successfully, confirm the following:

o You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers.

Note:

To view the Microsoft Exchange System Objects container in Active Directory Users and Computers, on the View menu, click Advanced Features.

o The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.

o On each domain controller in a domain in which you will install Exchange 2010, the Exchange Servers USG has permissions on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.

Install Exchange Server 2010

Technet Webcast: Unified Communication Introduction

Hola, los invito a particiar en este webcast el 11 de Noviembre a las 4:00 pm Bogota

Registrarse

Idiomas:
Español.

Productos:
Microsoft Exchange Server 2007,Microsoft Office Communications Server 2007.

Audiencia(s):
Generalista de IT.

Moderador(es):

Andrés Lozada

Duración:
60 Minutos

Fecha de Inicio:

miércoles, 11 de noviembre de 2009 04:00 p.m. Bogotá

Información general del Evento

Integre su plataforma de comunicaciones, audio, voz y video con su sistema de mensajeria con Exchange Server 2007 y Office Communication Server 2007.

Exchange Server 2010 RTM Released!

Hi folks,

Today was released the RTM BITS of Exchange Server 2010, you can now download from your licensing Website Download Microsoft Exchange Server 2010 TRIAL

http://technet.microsoft.com/en-us/evalcenter/dd185495.aspx

Virtual Experience

Take a simple web-based test drive. Get your free end
user account to preview Exchange Server 2010 and Office
Communications Server 2007 R2 together for 60 days.

Downloads

Free 120-day Software Trial

Try Exchange Server 2010 in your own environment.

Virtual Hard Drive

Try a pre-configured Exchange Server 2010 VHD.

Exchange Online Trial

Get a Free Exchange Online account for 30 days.
Experience the suite of hosted services
provided by Microsoft Online.

Webcast TechNet: Como migrar a Exchange Server 2010

Hola,

Los invito a participar en este Webcast el proximo lunes 9 de Noviembre, Migracion a Exchange Server 2010

Registrate ya

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032420899&EventCategory=4&culture=es-AR&CountryCode=AR

 Idiomas:
Español.

Productos:
Microsoft Exchange Server 2007.

Audiencia(s):
Generalista de IT.

Moderador(es):

Andrés Lozada

Duración:
60 Minutos

Fecha de Inicio:

lunes, 09 de noviembre de 2009 04:00 p.m. Bogotá

Información general del Evento

Evalúe los requisitos y la forma más sencilla de migrar su plataforma de correo a Microsoft Exchange Server 2010.

Do NOT Apply KB974571 to LCS/OCS Servers

Hey folks,  check this post URGENT, CRITICAL to LCS and OCS

http://blogs.technet.com/dodeitte/archive/2009/10/13/do-not-apply-kb974571-to-lcs-ocs-servers.aspx

Update #1 - Until this issue can be resolved, I am only suggesting that you either hold off on deploying this update, or test very throughly to make sure that this won't cause an outage in your environment.  Security updates are VERY important, and once this issue is resolved, you should deploy this update to all of your LCS/OCS servers.

Currently an issue is being observed after applying KB974571 (MS09-056: Vulnerabilities in CryptoAPI could allow spoofing) to LCS/OCS servers, that is causing them to believe that they are running an evaluation version of LCS/OCS and that it has expired.

http://support.microsoft.com/kb/974571/

If you apply the patch, the LCS/OCS services fail to start and you see these errors in the event log:

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              12290
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:         
Description:
The evaluation period for Microsoft Office Live Communication Server 2005 has expired. Obtain the released version of this product and upgrade to the non-evaluation version by running setup.exe

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              16417
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:         
Description:
Unable to initialize the protocol stack. The service has to stop.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              12299
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:         
Description:
The service is shutting down due to an internal error.

Error Code: 0xC3ED0804.
Resolution:
Check the previous event log entries and resolve them. Restart the server. If the problem persists contact product support.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Uninstalling the patch is the only way to currently fix this issue.

The issue is currently being escalated, but until a fix can be found, delaying the install of KB974571 is recommended.

Webcast Introduccion Exchange Server 2010 (Nivel 100)

Hola,

Los invito a participar de este Webcast

Webcast TechNet: Introducción a Exchange Server 2010

Registrarse

Idiomas:Español.

Productos:Microsoft Exchange Server 2010.

Audiencia(s): Generalista de IT.

Moderador(es): Andrés Lozada

Duración:60 Minutos

Fecha de Inicio:miércoles, 14 de octubre de 2009 04:00 p.m. Bogotá

Información general del Evento

Conozca lo nuevo de Exchange 2010 y evalue los pre requisitos para migrar su plataforma de mensajeria a Exchange 2010

Microsoft Virtual Academy 2

Hola,

Los invito a participar de la nueva version Microsoft Virtual Academy, pueden encontrar entrenamiento gratuito y la nueva carrera de Exchange Server 2010

http://www.mslatam.com/latam/technet/mva2/Home.aspx

Exchange Server 2010

Evento Virtual Nueva Eficiencia Registrate YA!

Hola, Los invito a participar en este evento virtual el proximo 7 de Ocutbre, registrate YA!

 http://www.microsoft.com/latam/technet/nuevaeficiencia/

Windows 7

· Características, despliegue y seguridad en Windows 7

· De Vista a 7: virtualización de escritorios, migración de redes y fundamentos de administración Optimización de aplicaciones

Windows Server 2008 R2

· Revisión de la nueva tecnología, optimización en el consumo de energía

· Mejoras de virtualización, analizador de mejores prácticas e infraestructura para trabajar en cualquier sitio

Exchange Server 2010

· Revisión general, movilidad y Outlook Web Access

· Alta disponibilidad y almacenamiento

· Herramientas de manejo, transición y descarga

Forefront

· Introducción y la nueva generación de productos Forefront

· Forefront y Office SharePoint Server, mejor juntos!

Information Workers

· Introducción a Office 2010

· Novedades, mejoras y trucos

PreCallDiagnostic Resource Kit Tool

Brief Description

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect.

Download

http://www.microsoft.com/downloads/details.aspx?FamilyID=f16ab4c2-353f-4c9b-b353-22a656c03c9b&displaylang=en

Overview

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect. The tool should be installed on any desktop or laptop PC that suffers from inconsistent network connection quality. The PreCallDiagTool can provide a quick check of the current network conditions and also preserve a history of quality data to let users profile their network performance over time or other conditions. The tool is particularly useful for home/mobile users and users using WIFI access points.

Note: This is the 32 bit version of the PreCallDiagTool. The 64 bit version can be found in the Office Communications Server 2007 R2 Resource Kit.

System Requirements

• Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Vista; Windows XP Embedded Service Pack 2
  
• This download works with the following Office program:
  
  • Microsoft Office Communications Server 2007 R2
    

Install Exchange Server 2010 RC1 Edge Role

Hi, now i going to show you a few steps to install the Edge Server Role on Windows Server 2008 R2

Before you run the setup add the FQDN DNS suffix over the computer properties

The DNS suffix is not set on the local computer

To set the primary DNS suffix of the local computer

1.     Right-click My Computer, and then click Properties. The System Properties dialog box will appear.

2.     Click the Computer Name tab.

3.     Click Change. The Computer Name Changes dialog box will appear.

4.     Click More. The DNS Suffix and NetBIOS Computer Name dialog box will appear.

5.     Enter the appropriate DNS suffix for the domain.

6.     Select the Change primary DNS suffix when domain membership changes check box.

7.     Click OK to save the changes, and then click OK to exit the Computer Name Changes dialog box.

8.     Click OK to close the System Properties dialog box, and then restart the computer for the change to take effect.

Then, install the pre-requisites 

Windows Server 2008 R2 operating system prerequisites

1. 1.     On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.

2. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:
   
   

Import-Module ServerManager

1. 3.     For a server that will host the Edge Transport role:
   
   

Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS -Restart<?xml:namespace prefix = o />

Run the setup wizard Introduction License Agreement Error Reporting Select the installation directorySelect the Edge Role   Customer Experience Improvement ProgramInstallation Status