A worth reading KB about hosting a domain controller in a virtual environment.
Considerations when hosting Active Directory domain controller in virtual hosting environments
Finally we can download Exchange Server 2010 .chm help file. Here is the link (Exchange Server 2010 help).
Enjoy it 
In the first post about Exchange 2010, I talked about some key features and the prerequisites needed to deploy Exchange 2010.
http://tariqjaber.com/blog/2010/02/01/exchange-server-2010-part1-features-and-prerequisites
In the second post I prepared the organization for Exchange 2010 to coexist with Exchange 2003.
In this part we will go through the installation process.
After preparing the domain and installing the prerequisites for Exchange 2010 we can start the installation wizard. In the first page we are choosing the language option. I’ll select “Install only languages from DVD” this will install English language support.
Select “Install Microsoft Exchange”
Click Next, accept the terms and in the error reporting page choose yes if you want to enable Exchange Error Reporting to automatically send errors to Microsoft.
In the Installation Type page, I’ll choose Custom Exchange Server Installation because in my lab I’ll install Hub Transport and Client Access server roles on this server, then we will install Mailbox role on other server.
Now select Client Access Role and Hub Transport Role and choose the installation path.
Now we are in the Configure Client Access server external domain, if this Client Access server will be internet-facing and used for Outlook Web App, ActiveSync and Outlook Anywhere then enter the domain name that the clients will use.
Because we are installing Exchange 2010 in an existing Exchange 2003 environment, the Mail Flow Settings page appeared to select the Exchange 2003 server to be used for the routing group connection creation.
In the following page you are invited to join Customer Experience Improvement Program (CEIP).
Now the wizard will check the system for Exchange prerequisites.
After the Readiness Checks succeed, the installation takes place and starts
Now we have Hub Transport and Client Access server roles installed. Next step is to test the coexistence with Exchange 2003. This will be in the next post.
This a great article about how to migrate your Windows XP to Windows 7 :
USMT and OfflineWinOld: Taking XP to Windows 7 in a Hurry
In the first post about Exchange 2010, I talked about some key features and the prerequisites needed to deploy Exchange 2010.
http://tariqjaber.com/blog/2010/02/01/exchange-server-2010-part1-features-and-prerequisites
In this post I’ll start installing Exchange 2010 in an existing Exchange 2003 environment.
-Client Access
-Hub Transport
-Unified Messaging (UM)
-Mailbox Server
The first thing we should do is to change the Exchange organization to native mode. To change it we will use Exchange 2003 System Manager:
1. Open Exchange System Manager.
2. Right-click the organization and click Properties.
3. In the General tab, under Change Operations Mode, click Change Mode. Click Yes to permanently switch the organization’s mode to native mode.
Legacy Host Names:
Now if you have Outlook Web Access (OWA) published and the users are accessing their mailboxes from outside the network, you have to use a legacy host name. A legacy host name is a name that will be assigned to Exchange 2003 OWA like legacy.domain.com, and the name that was being used for OWA, like mail.domain.com, will be assigned to the newly installed Exchange 2010. When the users connect to mail.domain.com, they will be redirected to Exchange 2003 front-end server and they will not be interrupted accessing their mailboxes using POP3, IMAP4 and Outlook Anywhere.
SSL Certificate:
Prepare your Exchange server 2010 certificate, it is better to have a Subject Alternative Names (SAN) certificate which contains the names of all Exchange 2010 and 2003 server’s names.
Preparing Active Directory for Exchange 2010 installation:
We need to prepare our Active Directory for Exchange 2010 installation. The account that we will use for the preparation should be member of the Schema Admins, Domain Admins and Enterprise Admins groups
1. Because we have an earlier version of Exchange 2003 installed, we must run
Setup.com /PrepareLegacyExchangePermissions or Setup.com /pl
On the server Mig-R2Ex14, which we have installed Exchange 2010 prerequisites on, I’ll run this command, run it as administrator:
The forest functional unit must be Windows Server 2003 native or later or you will got the error:
For more details about How to raise domain and forest functional levels in Windows Server 2003 see KB322692 and here for Windows Server 2008
2. Now we will prepare the schema using the command
Setup.com /PrepareSchema or Setup.com /ps
Wait for the replication to complete or force the replication.
For Exchange 2003, the schema version is 6903, you can check it using ADSIEdit.msc
After preparing the schema for Exchange 2010, the version will be 12640
3. After this, we will prepare Active Directory using the command
Setup.com /PrepareAD or Setup.com /p
Note in the command it says:
“Setup is going to prepare the organization for Exchange 2010 by using ‘Setup /PrepareAD’. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 server roles.”
4. Finally, we will prepare the domain
Setup.com /PrepareDomain or Setup.com /pd
If you want to prepare all the domains in your organization run the command
Setup.com /PrepareAllDomains or Setup.com /pad
Now we have prepared the domain, we are ready to start Exchange 2010 installation. I’ll talk about it in the next post.
References
Prepare Active Directory and Domains http://technet.microsoft.com/en-us/library/bb125224.aspx
Prepare Legacy Exchange Permissions http://technet.microsoft.com/en-us/library/aa997914.aspx
If you want to deploy Exchange Server 2010 on a Hyper-V guest machine then make sure your environment meets the following conditions:
Requirements for Exchange guest machine:
|
for more information about this, see Exchange 2010 System Requirements.
In this series of posts I’ll talk about installing Exchange Server 2010 on Windows Server 2008 R2 and how to migrate mailboxes from Exchange 2003 to Exchange 2010.
My lab will consist of the following servers:
|
What is new in Exchange 2010
|
And a lot of other features that I’ll talk about in other posts.
Let’s start our lab. First of all we will install Exchange 2010 prerequisites.
Import-Module ServerManager
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
Set-Service NetTcpPortSharing -StartupType Automatic
- Exchange 2010 Prerequisites (http://technet.microsoft.com/en-us/library/bb691354.aspx)
- Register Filter Pack IFilters with Exchange 2010 (http://technet.microsoft.com/en-us/library/ee732397.aspx)
- This Exchange server is also a domain controller, which is not a recommended configuration (http://technet.microsoft.com/en-us/library/aa997407(EXCHG.80).aspx)
The following link provides a good description of “Licensing Windows Server in a Virtual Environment”:
In the following url you can find a description of Aurora Internet Explorer exploit which the Chinese hackers used to hack google.com gmail accounts:
I wrote an article at ExchangeInbox.com about “Exchange 2007 Standby Continuous Replication – Configuration & Testing”. You can find it @ (http://exchangeinbox.com/article.aspx?i=149)