While initiating EMS received error :The user load quota of 2147483647 requests per 60 seconds has been exceeded

Issue : While initiating EMS received error 

"Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The user load quota of 2147483647 requests per 60 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least 2137494400 milliseconds. For more information, see the about_Remote_Troubleshooting Help topic."

Resolution : Reset IIS or from IIS Manager > Server > Application Pools > Recycle "MsExchangePowerShellAppPool"

Exchange 2010 Sp3 Ru7 OWA search is not working

Issue : OWA search is not working for all of the users, No issues with Outlook users on Exchange 2010 SP3 RU7 on SBS server

Troubleshooting steps performed
1. Last time When Index catalog has been built : Recently

2. How many users are facing this issue : All

3. How many nodes of Exchange server : Single

4. What if Mailbox moved to another Server/ Database : Not possible (SBS)

5. Since when Users are facing this issue : After installing Windows Update

6. Is Search is working for outlook Client : Yes

7. On newly Created Test user, Search is working : Not working

9. Test-MailboxDatabase –MailboxDatabase <DB> : Error "Time out for test thread"

10. Test-ExchangeSearch :  The MSExchangeSearch service isn't running.   

11. “Microsoft.Exchange.Search.ExSearch.exe”  from Task Manager and check the processor : Normal , between 6% to 12%

12. Please check Search on Different Internet Browser like Chrome or Firefox : Same issue,Not Working

13. Download SymLink from Repair-ExchangeSearchSymlinks.ps1 and run the command (this script repairs symbolic links) : Still Search is not working

14.  .\ResetSearchIndex.ps1 [-force] <dbname> [<dbname>]...

You will receive an Event ID 109 when the rebuilding of the index starts for each database and an Event ID 110 for each database when the index rebuild has completed : Still Search is not working

15. After receiving Event ID 110 for each database, test to make sure search functions correctly with both OWA and Outlook operating in Online Mode : Still Search is not working

16. From Exchange SP3 media, Goto Setup.Exe folder and from Command Prompt with "Run as administrator" First run setup /PrepareAD and then run setup /PrepareSchema and after that reboot he box and make sure “Microsoft Exchange Search Indexer Service” and “Microsoft Information Store” service is started and checked the issue


Now, issue is resolved

“Your mailbox can't be accessed using the address you entered, please obtain the correct address, please contact your helpdesk”

“Your mailbox can't be accessed using the address you entered, please obtain the correct address, please contact your helpdesk”

Method1:

To proceed to the control panel you can access the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server locally, use the following URL: https://localhost/ecp?ExchClientVer=15.
Same way applies if you want to access the Exchange 2010 ECP and your mailbox hosted on an Exchange 2013 Mailbox server, use the following URL: https://localhost/ecp?ExchClientVer=14

Method2:

Through PowerShell create a new mailbox on Exchange 2013 and give it the necessary administrative permissions.

refered from: http://blogs.technet.com/b/meamcs/archive/2013/05/04/exchange-2013-coexistence-ecp-your-mailbox-can-t-be-accessed-using-the-address-you-entered-please-obtain-the-correct-address.aspx

Troubleshooting Steps : The Proxy address "MBX:0" is already being used by org/users/username

Issue : Error received when for few user tried to change the "Set as Reply" 

The Proxy address "MBX:0" is already being used by "org/users/username". Please choose another proxy address

Resolution :  From the ADSIEdit.msc, remove the Problematic address from the Attribute "ProxyAddress"

Users had been migrated from Exchange 2003 to Exchange 2010, while moving mailbox Exchange stamps mailbox for processing with MBX:0 and MBX:1 likewise

Cross Forest Migration

Tools

1.  Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1) 
2. MIIS
3. FIM, other 3rd party dirsync tool, etc

2. Scripts

(a) This example configures the Availability service to retrieve per-user free/busy information on a Mailbox server in the target forest.

Get-MailboxServer | Add-ADPermission -Accessrights Extendedright -Extendedrights "ms-Exch-
EPI-Token-Serialization" -User "<Remote Forest Domain>\Mailbox servers"

Add-AvailabilityAddressSpace -Forestname ContosoForest.com -AccessMethod PerUserFB -UseServiceAccount:$true

(b) To configure bidirectional cross-forest availability, repeat these steps in the target forest.


If you choose to configure cross-forest availability with trust, and also choose to use a service account (instead of specifying organization-wide or per-user credentials), you must extend permissions as shown in the example in the "Use the Shell to configure trusted cross-forest availability with a service account" section. Performing that procedure in the target forest gives Mailbox servers in the source forest permission to serialize the original user context.
(c) This example configures trusted cross-forest availability with a service account.
Get-MailboxServer| Add-ADPermission -Accessrights Extendedright -Extendedright "ms-Exch-EPI-Token-Serialization" -User "<Remote Forest Domain>\Exchange servers"

This example sets the organization-wide account on the availability configuration object to configure the access level for free/busy information in the target forest
Set-AvailabilityConfig -OrgWideAccount "Contoso.com\User"

This example adds the Availability address space configuration object for the source forest.
$a = Get-Credential (Enter the credentials for organization-wide user in Contoso.com domain)
Add-AvailabilityAddressspace -Forestname Contoso.com -Accessmethod OrgWideFB -Credential:$a


From Microsoft Technet : http://technet.microsoft.com/en-us/library/bb125182(v=exchg.150).aspx









from Blog :http://blogs.technet.com/b/ucedsg/archive/2010/04/22/how-does-federated-calendar-sharing-work-in-exchange-2010.aspx



Four things needed to get you started:

1) Obtain a X.509 certificate from a Trusted Root CA (GoDaddy, Entrust, etc) for use with Microsoft Federation Gateway (MFG) for signing and encrypting delegation tokens.  (more here). Here is a list of Trusted Root CAs that MFG is aware of here.

2) Create a Federation Trust using cmdlet with the MFG (more here):

New-FederationTrust

3) Provide domain ownership by creating a DNS TXT record similar to (more here):

Contoso.com IN TXT AppId = 1C2

4) Add your SMTP domains (other Exchange Orgs) and add Federated domains to trust calendar information with (other org must accept) using cmdlet (more here):

Set-FederatedOrganizationIdentifier  - to enable your SMTP domains for federation sharing with the MFG

Add-FederatedDomain – to add other External Orgs to share calendar information with

The trust relationship between this workstation and the Primary domain failed

Issue : The trust relationship between this workstation and the Primary domain failed

Resolution : 

On Windows Server 2008 R2

Login to machine with local admin account and open Windows Shell "Run as Administrator" 

and run this command and then log off and try login with Domain credentials

NETDOM RESETPWD /Server:enteryourDCFQDN /UserD:domain\accountwithprivilege  /PasswordD:enteryourpassword

Alternatively, you can run the following command from shell also

Reset-ComputerMachinePassword -server yourDCFQDN -confirm

and for WINDOWS 7
Disjoin and Join Computer from Domain and that will resolves the issue

RpcClientAccessServer Exchange 2010 FAQ

Why there is a "Microsoft Exchange RPC Client Access" service in CAS and MBX server ?

Public folder connections from an Outlook client occur against the RPC Client Access service on the Mailbox server role. It is optional on a Mailbox server, only required for Outlook public folder access. 

How to point RPC Cas service  to Newly created Database ?

Get-Mailboxdatabase | Set-Mailboxdatabase -RpcClientAccessServer "CASArrayname.domain.com"

Setting Static RPC ports for MAPI and Directory Access ?
By default you need to open the TCP 135 EndPointMapper and the Dynamic RPC range TCP 1024-65535 between your internal Client network and the CAS server or Arrays and your Mailbox servers.

On CAS servers, for Mailbox connections, add D-Word “TCP/IP Port" and set the value 55000, 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem

also from

Microsoft.exchange.addressbook.service.exe.config 

Open the file in Notepad and then change the “RpcTcpPort” value from the default assignment of “0” to the port you want Outlook clients and Exchange to use for the directory access via the NSPI EndPoint. In this article we use port 55001.

Unicast Mode

With the WNLB cluster configured in unicast mode, the MAC address of each server’s network adapter will be changed to a virtual cluster MAC address, which is the MAC address that will be used by all servers in the Windows NLB cluster. When unicast mode is enabled, clients can only connect to the servers via the VIP address on the network interface card (NIC) that has been configured with the cluster MAC address.

Multicast mode

With the Windows NLB cluster configured in multicast mode, a multicast MAC address is added to the cluster adapter of each server in the cluster. Note that I write “is added”, as each server will retain their original MAC address.

A Windows NLB cluster, no matter what mode it is configured in, works with just a single network adapter installed in each server, but it is recommended to install a second network adapter in each server, in order to achieve optimal performance, and to separate ordinary and cluster related network traffic.

So what mode should I use for my Exchange 2010 CAS array and how many network adapters should I install in each Client Access server? Well, a best practice recommendation is to install two network adapters and use unicast mode, so that the host and cluster network traffic are separated on their own respective network interface. However, if you only have the option of installing one NIC in each CAS server or if you’re forced to using multi-cast mode because of the switches used in your organization, you should pick multicast mode.