1. Choose Computer Name, like MAIL1. If the domain controller has already been established, then the name will already be something like MAIL1.yourdomain.lan. [NOTE: To establish and configure a domain controller on Server 2008 (64-bit) upon which Exchange 2010 can be installed (like a “One Box” setup), see this article at: http://www.sheldonsblog.com/index.php/configure-windows-server-2008-r2-sp1-for-exchange-server-2010/ ]
2. Make sure Administrative user is member of: Enterprise Admins and Schema Admins. Open Active Directory Users and Computers, under the windows domain, click Users folder, double click Administrator (or other logged in user account) and click properties, then click the tab Member Of, and make sure the user is a member of Enterprise Admins and Schema Admins..
3. Setting up Pre-requisite Roles. Open server management console, right click features and click add features, ADD FEATURES WIZARD opens, Select Features: add .NET Framework 3.5.1 (but this was already added when installing Active Directory services on server 2008 to convert to a domain controller), add RPC over HTTP Proxy and also click button to Add Required Role Services including Web Server (IIS) and Management Tools, Remote Server Admin Tools with Role Admin Tools; for Internet Framework expand the +WCF Activation and check HTTP Activation and Add Required Role Services (Web Server and Windows Process Activation Model), expand +Remote Server Administration Tools, expand Role Administration Tools (installed), make sure Web Server (IIS) Tools in checked, and Check AD LDS Snap-Ins And Command line tools. Next
4. Select Role Services link on Wizard left menu: Add ASP .NET +Add Required Role services, In security, make sure Basic Authentication checked, Make sure Windows Authentication checked, and check Digest Authentication, ALL IIS 6 Management Compatibility, including check IIS 6 Metabase compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and IIS 6 Management Console. Click NEXT (leads to confirmation), Click INSTALL button. When done installing, click Close button.
5. Set Net.tcp Port Sharing Service Startup Type to Automatic (with Delayed Start). Go to Start, Administrative Tools, Select Services, Select Net.tcp Port Sharing Service, Properties, It is set to Disabled by default. Change Startup type to “Automatic (Delayed Start)” and click Apply and click OK. Close Services
6. Install Microsoft Office 2010 Filter Pack (index content of attachments, docx, xlsx). Note Adobe has its own filter pack for exchange. Office Filter Pack download 64-bit version: http://www.microsoft.com/download/en/details.aspx?id=17062
Microsoft filter pack 2.0 has completed successfully.
7. Install Exchange 2010
1. Insert Exchange 2010 DVD Install Disk in DVD drive. Run Setup.EXE
2. Step 3, Choose Exchange language option – Select install only languages from the DVD
3. Step 4, Click Install Microsoft Exchange, [echo: Microsoft Exchange Server 2010 Setup Initializing]
4. Exchange Server 2010 Setup screen, click Next.
5. Accept License Agreement (radio button), click Next.
6. Enable Error Reporting (this automatically sends error reports to Microsoft). It’s up to you to select Yes or No.
7. Installation Type: Select “Typical Exchange Server Installation” click Next (rather than custom which includes 2 extra items called Unified Messaging, and Edge Transport), and with Typical Installation these items are setup (along with path to Exchange Program Files):
1. Hub Transport
2. Client Access
3. Mailbox
4. Exchange Management Tools
8. Specify Name for Exchange Organization. Default is First Organization. Organization Name: Stored in Mail Database. First Organization – Use the name of your company.
9. Client Setting Do you have any client computers running Outlook 2003 or Entourage in your organization? Yes or No. Next. (Outlook 2003 clients will require setup of public folder database) Recommended: Select Yes. (Just in case), Click Next
10. Configure Client Access server external domain. For internet facing services, for example Exchange ActiveSync, Outlook Web App, Outlook Anywhere. This will allow clients to connect to your exchange deployment outside of your (internal windows) domain.
1. Check the box for The Client Access server role will be internet facing.
2. Enter the domain name you will use with your external Client Access Servers (for example, mail1.yourdomain.com. Click Next button.
11. Customer Experience Improvement Program –
1. The industry that best represents you organization. (Select drop down or not specified)
2. Join the Exchange Customer Experience Improvement Program (CEIP)
3. I don’t wish to join the program at this time.
4. Next button
12. Readiness Checks. Warnings.
1. Warning such as “Setup is going to prepare the organization for Exchange Server 2010 by using ‘Setup /PrepareAD’ and no Exchange Server 2007 roles have been detected in this topology. After this operation, it will be impossible to install any Exchange Server 2007 roles.” If you decide that you need to deploy an Exchange 2007 server prior to deploying Exchange 2010, the deployment of a single Exchange 2007 with all server roles is sufficient to enable the deployment of future Exchange 2007 servers in the organization. I doubt this warning is fatal. It applies mostly to 3rd party or custom apps built on Exchange 2007.
2. Setup cannot verify that the ‘Host’ (A) record for this computer exists within the DNS database on server 127.0.0.1. Check your internet connection. Also, verify on IP v4 connection the following DNS entries dns1 = 127.0.0.1 and dns 192.168.x.x of this servers NIC. Don’t use forwarders in DNS. Just show bind to all IP addresses of server.
13. Install. Click Install. Go find something to drink. It will take quite a while. 00:33:47
8. Finalize this Installation using the Exchange Management Console. (Configure Exchange.) Leave Checkbox Checked (to Finalize). And Click Finish Button which will close Exchange Server 2010 Setup, and will ADD Snap-in to Console.
1. Finalize Deployment Tasks (Checklist)
2. Enter Product Key. Exchange Management Console. Expand +Microsoft exchange On Premises; Click Organization Configuration, Exchange unlicensed, has 119 days remaining. Click Server configuration, and under the Exchange server node name on the right side menu, Click Enter Product Key, and enter it. The 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. Click Finish button, then go to Administrative Tools, Services, and restart the “Microsoft Exchange Information Store” service. Right click the name of the service and left click “Restart.”

THE REMAINDER OF THIS ARTICLE STILL WORK IN PROCESS:
3. Install Forefront Protection 2010 for Exchange Server. (Optional.  MS download. Look into it.)
4. Another author reports that you may need to enable Exchange Search to index Microsoft Office 2007 file formats by registering the installed iFilters for Exchange 2010 by modifying the registry. It is suggested to perform this step after installing Exchange 2010. Ask yourself, did I not already install the 2010 filter pack? Note, the other author offered some script to save to file and run. Look into this.
5. Organization configuration, Mailbox. Client Access, Hub Transport most important to configure.
6. Send Connector, New Send Connector, name = internet, add type smtp, *, dns mx record. Next pick a server, this one. New, finish.
7. Server config, client access, owa, enable Outlook Anywhere.  External hostname, same as previously named.
8. Exchange active sync.
9. Imap and pop3, enable. But still need to enable the services under admin tools, services. Change from manual to automatic, delayed start.
10. Allow Anonymous Access on the Server’s Default Receive Connector. Exchange Management Console, expand Server Configuration. Select “Hub Transport” Under “Receive Connectors” right click the “Default” Receive Connector, select Properties, select Permission Groups tab, to configure receiving on TCP Port 25 by enabling anonymous users (Specify who is allowed to connect to this Receive connector). Check the Anonymous Users checkbox, and click Apply button and click OK. DONE. Caution: My first guess is that this anonymous connectivity may create an open relay, unless mail can only be delivered to local exchange mailboxes from this Receive connector. Note: Port 587 will have no anonymous access on the other Receive connector here.
11. Recipient configuration. Mailbox. Where you configure all email accounts.
1. New mailbox, next, existing users, add, select the usernames to create mailboxes.
9. Configure Port forwarding on router, for ports 25, 80, 443.
10. Configure some things in IIS.
1. Certificates. Exchange creates default certificates for itself.
2. Default website.  http redirect: ./owa checkbox only redirect requests to content in this directory (not subdirectory). This redirect works only with https not http, unless you put full url redirect in like this: https://etc/owa.