step by step installation of exchange 2010 on win 2008 r2

Prerequisites

Before installing Exchange Server 2010, here are the prerequisites to be installed in all the servers

1. Net Framework 3.5
2. Powershell 2.0 CTP 3
3. Windows Remote Management

The above three components must be installed regardless of which role you wish to install.
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-ADDS

Below 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-ADDS

Transport Role

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext RSAT-ADDS

Mailbox 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 Role
KB951725, KB950888, KB952664, KB953290
Transport Role
KB951725, KB950888, KB952664
Mailbox Role
KB951725, KB950888, KB952664

Now we are truly ready for the installation. I will not talk about installation using UI, because I prefer using command line.
Execute the command as shown in the screen capture below.

Here are the definitions of the parameters

/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

Just hit "Enter" and sit back enjoy your coffee or newspaper. :-)

Voila, you have now completed the installation and enjoy. (below are the two screenshots of new Exchange Management Console and OWA after installation)

Service 'MSExchangeTransport' failed to reach status 'Running' on this server.

Aparently, this normally happens when you disable IPv6 in Local Area Connection.
This is due to the behavior of IPv6 in Windows Server 2008, when you disable IPv6 in Local Area Connection on Windows 2008 server.

The following error was generated when: “$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”

After doing lot of troubleshooting and searching on the net, found that this is happening due to IPV6, and installation needs IPv6 to be disabled in your local area connection on the system. After disabling my setup went smoothly, follow the below instructions to disable IPv6 from your system.
To completely disable IPv6 on a Windows Server 2008-based system, follow these steps:
1. Open Registry Editor.
2. Locate the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
3. In the details pane, click New, and then click DWORD (32-bit) Value.
4. Type DisabledComponents, and then press ENTER.
5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.
If setup still gives error, remove IPv6 entry from “hosts” file %systemroot%\system32\drivers\etc

then enable ip6 from network by changing adapter settings. 

enable windows remote managemetn on win2008 r2

Assuming the remote server is all set up and prepared to enter production, first, open Server Manager on the remote server.
Click on the "Configure Server Manager for Remote Management" link.
Select the "Enable remote management of this server from other computers".
Click "Ok".

The server's firewall will automatically be configured to allow the relevant traffic in.
How do you connect to the remote server?
On the computer you wish to use as the management machine (running either Windows Server 2008 R2 or Windows & with RSAT), open Server Manager.
Right-click on the Server Manager item and select "Connect to Another Computer".

In the Connect to Another Computer window, type the name or browse to the server you wish to connect to.

voip client for android 2.2 frio

http://code.google.com/p/csipsimple/

it works with 

G.711 A audio codec

finding srv records in dns

nslookup -type=SRV _sip._udp.domain name

in place of domain name user your domain name