Ms Exchange Server 2010 Activation
An Exchange Server 2010 Database Availability Group DAG provides several benefits to an organization, primarily that of continuous availability of mailbox databases.
How to Install, Setup and Configure Microsoft Exchange Server 2010.
Get your free link to the most detailed Exchange Server 2010 setup and configuration instructions available online. All you need to do is fill out the form below and.
I had to install Exchange 2010 on a 120day trial for a client recently. The planned weekend for the down time had arrived but the new partner licenses had not. No bother I thought, it will be easy to enter the Exchange 2010 license when it arrives as the new ‘change your license key anytime’ feature in Server 2008 is great. Not so in Exchange 2010. What you get when running on a trial key is a pop-up box every time you open the Exchange Management Console. It informs you to enter your new license in the “Exchange server work centre action pane” but where on earth is that? Expand Microsoft Exchange Select ‘Server Configuration’ Select the unlicensed Exchange 2010 server and right click. Finally select ‘Enter Product Key…’ to start the license wizard. Once you’re all done you should get the success message. Simply restart the Information Store service or restart the machine with any necessary Windows Updates. Note: The preferred way of doing anything now in the majority of Microsoft’s server products is with PowerShell 2.0. Exchange 2010 is no exception. The confirmation screen of the wizard nicely displays the PowerShell command executed; here it is repeated with a dummy product key for completeness. Set-ExchangeServer -Identity yourserver -ProductKey ABC12-DEF34-GHI56-JKL78-MNO90
In this tutorial I will demonstrate a recovery scenario for a failed Mailbox server that is a member of an Exchange 2010 Database Availability Group.
Microsoft concentrated on high availability features in Exchange Server 2010, eliminating local continuous replication, standby continuous replication, single copy.
Follow the steps below to correctly configure your Exchange Server 2010 email server for general use, and for use with IGetMail. Note that for this document we are assuming you are installing Exchange 2010 on Windows Server 2008 R2 64 Bit.
Add role - Active Directory Services
Installing Exchange Server 2010
Allow IGetMail access to your Exchange Server
Make sure you have all of the following steps in place before you setup Exchange Server 2010 on Windows Server 2008 R2 64 Bit.
For simplicity we are assuming you are setting up a small office where one machine will be used for both the Active Directory and the Exchange Server. This setup works just fine and reduces the number of machines to maintain. If you have a larger office you may want to consider separating the Active Directory machine and the Exchange 2010 Server.
Install Windows Server 2008 R2 64 bit version
Exchange 2010 is a 64 bit application and requires 64 bit versions of Windows Server 2003 or Windows Server 2008. You should select a computer that is capable of running the 64 bit version of Windows Server 2003 or 2008. For this example, we will start with a clean installation of Windows Server 2008 R2 64 bit version that has not had any roles installed.
After installing Windows Server 2008 R2 we set the clock and the name of the server to be "EX2010". At this point this server is configured to be a stand alone computer with default settings.
The default installation of Windows 2008 sets your IP v4 and IP v6 addresses to use DHCP. Since we will be configuring this computer to be a domain controller, you must change the IP address of the computer to be a static IP address.
To change your IP address, click on "View Network Connections" in the Server Manager screen. This will display the list of active network interfaces.
Highlight "Internet Protocol Version 4 (TCP/IPv4)" and then press the Properties button.
Change the radio button to "Use the following IP address" and enter an IP address you want to use for this server. In our example, we chose to assign this server the internal IP address "192.168.1.25". We also have a firewall appliance that operates as a gateway at the IP address "192.168.1.1".
NOTE: It is important to include this computer in the DNS list. You should list the IP address of this computer as the first entry in the list of DNS servers. In the alternate DNS servers field, enter the IP address of a DNS server provided by your ISP.
Press OK to save your changes.
Now you will need to modify the support for IP v6. If your network uses IP v6, then you will need to select "Internet Protocol Version 6 (TCP/IPv6)" , press the Properties button, then enter a static address. If you are not using IP v6, you can leave the IP v6 set to the default setting of DHCP.
NOTE: Exchange requires that IP V6 be enabled. Even if you do not use IP V6 you must leave it enabled. During the setup of Active Directory, the Active Directory Setup Wizard will check that both IP v4 and IP v6 have static addresses. As long as the IP v4 address is static you can continue the installation. DO NOT DISABLE IP V6 or else the Exchange Hub Transport Service will not start.
At this point you should have all IP addresses on this server configured as static IP addresses. OR you have the IP v4 address configured as static and the IP v6 configured using DHCP. Press OK to save your changes and close the Network Connection screen.
The next step in making this server a Domain Controller is to activate auto update. Active Directory will not install until this computer has auto updates active. To activate auto updates, click on the link "Configure Updates" and then select the option to have Windows automatically install updates. At this time Windows will download updates and will most likely need to reboot your computer. Allow the updates to be applied and the computer to be restarted until all updates are applied before installing Active Directory. You do not want to be in the middle of installing Active Directory when an auto update needs to reboot your computer.
The process of installing Active Directory consists of two steps: the first step is to install Active Directory and the second step is to configure your Active Directory. Once this is complete, your Windows Server will now be a Domain Controller.
Step 1 - Install Active Directory
At the Computer Management Screen, press the "Add Roles" link.
At the Select Server Roles dialog, check/tick the option "Active Directory Domain Services".
When you select Active Directory the Select Server Roles Screen will inform you that you also need to install the feature ".NET Framework 3.5.1". Press the "Add Required Features" button.
Active Directory Domain Services will present information about the changes it will make to your server. Review this information and press Next.
Now the installation will scan your configuration and inform you if there are any pre-requisites that you have not fulfilled. If the Active Directory Installation presents an errors, correct these at this time and then repeat the installation. Once the Setup program indicates that you have met all pre-requisites, then press the Install button to start the installation process.
When the installation is complete, you should see a message indicating "Installation Succeeded".
Press Close to return to the Server Management Screen.
At the Server Management screen you should now see that you have 1 role installed. The Active Directory Domain Services may indicate that it is installed but there are errors. This is because the software is installed but not configured.
To configure Active Directory, click on the line under Roles labeled "Active Directory Domain Services". The Server Manager will show you a page about the status of the Active Directory Role.
Click on the link "Run the Active Directory Services Installation Wizard (dcpromo.exe)". When the Active Directory Domain Services Installation Wizard appears, press Next.
Enter the name of your domain. The domain name you enter here is the domain name that Exchange will associated with all of your email. If you use a hosting company to host your Internet Domain, then you may want to enter the name of your Internet domain with ".local". If you host your own Internet Domain then you would enter your domain name here.
In our example, we are assuming that IGetMail.com is hosted at an Internet Hosting Company. Since we do not host IGetMail.com on this Exchange Server, we will use IGetMail.local to indicate our internal domain for IGetMail.
NOTE: Once you enter your domain name it is very hard to change it in the future, so you should take great care when enter this name.
Once you have decided on the name of your internal domain, that will be your Active Directory Domain and the domain serviced by Exchange, press Next.
The Installation Wizard will now ask you about compatibility. If you plan to have domain controllers running various versions of Active Directory, then you will want to chose a function level to include the lowest version of Windows that you are using for domain controllers. Press Next.
You will be asked a similar question which is at the domain level instead of the forest level on the previous screen. You should follow the same approach and include the function level to include the lowest version of Windows you plan to use for domain controllers. Press Next.
The first Domain Controller needs to have a DNS server running locally. The optimal location is to start out with having the installation wizard install the DNS server locally. Also, it will automatically make this computer a global catalog server. Press Next.
You can specify where you want Active Directory to store its data. If you only have one drive in your Server, then use the defaults. If you have multiple drives, you can select which drive to use. Press Next.
Should you need to restore Active Directory in the event of a hard drive failure, you will need to boot your Server into a special mode called "Directory Restoration Mode". Should you need to boot your computer into this special mode, you will need to use a special password just for this restoration. You can define this password at this time. NOTE: This password is different than the administrator account and if you change the administrator password this password will not change. So you will need to store this password forever in a safe place. Press Next.
After restarting your computer, Windows should show you the Server Manager. You should see on the Server Manager screen that you have Active Directory and DNS Server roles installed. Also the process of installing Active Directory will add the features "Group Policy Management" and "Remote Server Administration Tools".
Now that have your Server configured for Active Directory, Exchange requires that you add the Lightweight Service. NOTE: Exchange only requires that the Lightweight services are installed. It does not require the Lightweight Services to be configured.
Click on the link "Add Roles" and then select to add the role "Active Directory Lightweight Directory Services" and press Next.
At this point your Server Manager should show you that you have the Active Directory Lightweight Directory Services installed. This is sufficient for Exchange. If you want to create LDS instances you are welcome to, but that task is not required by Exchange.
Add feature - Windows Process Activation Service
The next feature that Exchange needs installed is the "Windows Process Activation Service". To install this feature, click on the link "Add Features".
At the Select Features screen, check/tick the feature "Windows Process Activation Service".
Select the items under this service and press Next.
The next Role that Exchange needs installed is the Web Server IIS. To install this role, at the Server Manager click on "Add Roles".
In addition to the default settings, check/tick the following additional services:
Security - Basic Authentication
Security - Windows Authentication
Security - Digest Authentication
Performance - Dynamic Content Compression
Management Tools - IIS 6 Management Compatibility (include all items under this service)
Press Next.
Now you are ready to install the next feature that Exchange requires as a prerequisite: "Windows Power Shell". At the Server Manager click on the link "Add Feature".
At the installation confirmation screen, press Install to begin the process of installing this feature.
When the Power Shell feature is installed, press Close to return to the Server Manager.
When you install Windows Server 2008, the default setup disables a service that is needed by Exchange. You will need to enable this service.
At the Server Manager screen - expand "Configuration" in the left hand panel. Then click on "Services". The middle of the screen will show the installed Services. Scroll to the Service named "Net.Tcp Port Sharing Service".
You will need to download the 2007 Office System Converter Pack. Click on this link to go to Microsoft's Download Site.
Exchange has a requirement to use its own SMTP service and not the SMTP Role that is built into Server 2008. As a result, you must not install the SMTP feature from the Server Manger. This will be installed by Exchange. Note that the Exchange Setup wizard will issue a warning that the SMTP services are not already installed, yet if you install the Windows 2008 SMTP feature, the Exchange Setup will consider that an error.
You are now ready to install Exchange Server 2010.
When you run the Exchange Server setup, the first 2 steps have been completed and will be inactive. The next step you need to perform is to select the Language Option. Click on "Choose Exchange Language Option".
Since this is Exchange Server is intended to be our only Exchange server, we will chose the typical installation which installs all of the components to make this Exchange receive, store and send email. Select "Typical Exchange Server Installation" and press Next.
Exchange will now ask what you want to specify for the Internet facing side of Exchange. In our example, using IGetMail we would create the Internet facing side of Exchange as mail.igetmail.com.
Exchange will now verify that all prerequisites are met. If there are any items that Exchange needs, it will inform you at this time. If the prerequisites have all been met, then press Install to begin the installation.
When the Exchange Server 2010 installation wizard completes, it will show the results of installing each component within Exchange Server. You should see all components with a green check mark.
Press Finish and your Exchange Server should now be ready to use.
When Exchange completes its installation, the Exchange System Manager will appear. The Exchange System Manager will guide you through several post installation tasks.
IGetMail Version 3.x instructions:
When you are running IGetMail version 3.x you can instruct IGetMail to send email to your Exchange server using an authenticated user or anonymous access.
Authenticated User Access - With this method you instruct IGetMail to use a specific Exchange user account to connect to the Exchange Server. Once connected through this account, IGetMail can send email to any of your Exchange user accounts. In order to use this method, the Exchange user account must be a member of the Exchange Server Group within Active Directory.
Open the Exchange Management Console
Expand "Server Configuration"
Select "Hub Transport"
In the middle section of the Management Console you will see the list of Receive Connectors.
Right click on the Receive Connector "Default ServerName" and choose Properties
Select the "Authentication" tab.
If you do not have an SSL certificate from a third party SSL provider, then Uncheck / Untick the option "Offer Basic authentication only after starting TLS". By default Exchange will not allow users to authenticate until you have an SSL certificate. Unchecking / Unticking "Offer Basic authentication only after starting TLS," allows Exchange to offer Authenticated login over standard SMTP.
The Windows account must have a mailbox in Exchange
The Windows user must be a member of the group "Exchange Servers"
Commonly, the Administrator account does not work because it does not have a mailbox and a standard Windows account is normally not a member of the Exchange Server group. To solve this you can either give the administrator a mailbox, or in our example below we created a Windows user, made this Windows user a member of the "Exchange Servers" groups, and then created a mailbox for the user. In our example this new Windows user is named "IGetMail".
Run Active Directory for Users and Computers.
Select the Users group in the column on the left.
Right Click and add a new user. In our case we choose to name this new user "IGetMail" since we will use this Windows user account to route the email through as the email is delivered to all of the other users within Exchange.
Go to the "Member Of" panel.
Press the Add... button.
Add the Group "Exchange Servers" to make this Windows account a member of the "Exchange Servers" group. This will grant this Windows account the rights to route email to other users. This is needed for IGetMail to route email to your users.
Run the Exchange Management Console
Expand "Recipient Configuration"
Select Mailbox to show a list of existing Exchange Users
Right Click on "Mailbox" under "Recipient Configuration" and select New Mailbox or Click on New Mailbox in the Actions Column on the right hand side.
Add the Windows account that you want IGetMail to use to the list of Exchange users. In our example below we have added the account "IGetMail" to the list of Exchange Users.
At the Status Panel, press the "Modify SMTP Settings" button.
Check / Tick the option "Authenticate as - "
Enter the Name of a Windows User Name that you want IGetMail to use to connect to the Exchange Server. This Windows account must have a mailbox in Exchange and must be a member of the "Exchange Servers" group.
Anonymous access - With anonymous access you can allow anyone to send email to any of your users. In this case, IGetMail only has to connect to the Exchange Server. It does not need to log into a Windows Account.
To configure Exchange to allow any user to route email perform these steps:
Open the Exchange Management Console
Expand "Server Configuration"
Select "Hub Transport"
In the middle section of the Management Console you will see the list of Receive Connectors
Right click on the Receive Connector "Default ServerName" and choose Properties
Select the "Permissions Group" tab
Check / Tick "Anonymous Users"
Save your changes
Now anyone can connect to the Exchange Server and route email to any user
When you are running IGetMail Version 2.x and 1.x you need to allow anonymous SMTP connections for your server.
Method 1 - Run the Exchange Management Console. Expand the Server Configuration and select Hub transport. In the lower half of the screen under the tab "Receive Connectors" right click on the connect labeled "Default
Home; Articles Tutorials ; Exchange 2010 Articles ; Management Administration ; Planning, Deploying, and Testing an Exchange 2010 Site-Resilient Solution sized.
