Introduction
Just got my hands on this latest new messaging product from Microsoft, and this has been one of the most anticipated products - Microsoft Exchange Server 2010 Beta (code named Exchange 14). You may can find the download link here, if you wish to test this out in your environment.
Design Diagram @MyLab
Below is the Exchange Server 2010 design in my Lab setup, all the servers are virtualized.
Prerequisites
Before installing Exchange Server 2010, here are the prerequisites to be installed in all the servers
Step by Step
1. Prepare your forest and organization in Active Directory
First you need to do the Schema preparation. Since this is a fresh new setup in the lab, I will perform the preparation on domain controller
Run Setup from the directory where your Exchange 2010 installation files are located. Here is the cmdlets
Next, you will need to prep the domain and organization. Here is the cmdlet
Now we have done the initial preparation. The forest and domain are ready to have the first Exchange 2010 server installed.
2. Install first Exchange 2010 server
We will do that on server "Bugis" which will have Client Access Role, Transport Role and Mailbox Role. But we will eventually remove the Mailbox role and deploy DAG on server "Outram", "Redhill" and "Dover". There is a reason behind why I choose to have 3 mailbox servers to form a DAG. That will be discussed in my future articles soon.
There are additional components needed before Exchange installation.,
As my first Exchange server is a combination all the 3 roles mentione above, I used the following command (refer the below screen capture)
Here is the break down of what you will need to install in role level.
Client Access Role
After the installation, you are required to perform restart server.
There are some updates & fixes need to be applied in specific.
Execute the command as shown in the screen capture below.
Voila, you have now completed the installation and enjoy. (below are the two screenshots of new Exchange Management Console and OWA after installation)
Just got my hands on this latest new messaging product from Microsoft, and this has been one of the most anticipated products - Microsoft Exchange Server 2010 Beta (code named Exchange 14). You may can find the download link here, if you wish to test this out in your environment.
Design Diagram @MyLab
Below is the Exchange Server 2010 design in my Lab setup, all the servers are virtualized.
Prerequisites
Before installing Exchange Server 2010, here are the prerequisites to be installed in all the servers
1. Net Framework 3.5The above three components must be installed regardless of which role you wish to install.
2. Powershell 2.0 CTP 3
3. Windows Remote Management
Step by Step
1. Prepare your forest and organization in Active Directory
First you need to do the Schema preparation. Since this is a fresh new setup in the lab, I will perform the preparation on domain controller
Run Setup from the directory where your Exchange 2010 installation files are located. Here is the cmdlets
Setup /PrepareSchema or Setup /ps*If you are running the prep process on the computer which is member of the forest or domain, and the OS is Windows Server 2008, you need to install the following component before executing the prep.
ServerManagerCmd -i RSAT-ADDSBelow screen capture shows that its completed.
Next, you will need to prep the domain and organization. Here is the cmdlet
Setup /p /on:SG or Setup /PrepareAD /OrganizationName:SG (where SG is my organization name in the Lab)
Now we have done the initial preparation. The forest and domain are ready to have the first Exchange 2010 server installed.
2. Install first Exchange 2010 server
We will do that on server "Bugis" which will have Client Access Role, Transport Role and Mailbox Role. But we will eventually remove the Mailbox role and deploy DAG on server "Outram", "Redhill" and "Dover". There is a reason behind why I choose to have 3 mailbox servers to form a DAG. That will be discussed in my future articles soon.
There are additional components needed before Exchange installation.,
As my first Exchange server is a combination all the 3 roles mentione above, I used the following command (refer the below screen capture)
ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDS
Here is the break down of what you will need to install in role level.
Client Access Role
ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDSTransport Role
ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext RSAT-ADDSMailbox Role
ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext RSAT-ADDS*For Mailbox Role, you have to install another component call "MSFilter Pack"
After the installation, you are required to perform restart server.
There are some updates & fixes need to be applied in specific.
Client Access RoleNow we are truly ready for the installation. I will not talk about installation using UI, because I prefer using command line.
KB951725, KB950888, KB952664, KB953290
Transport Role
KB951725, KB950888, KB952664
Mailbox Role
KB951725, KB950888, KB952664
Execute the command as shown in the screen capture below.
Here are the definitions of the parameters
Just hit "Enter" and sit back enjoy your coffee or newspaper. :-)
/m = /mode
/r = /role, /roles
H = Transport or you can use HT
C = Client Access or you can use CA
M = Mailbox or you can use MB
Voila, you have now completed the installation and enjoy. (below are the two screenshots of new Exchange Management Console and OWA after installation)
No comments:
Post a Comment