[Exchange 2013]: Exchange Org admin cannot Manage Mail enabled USG owners / members in (EAC) Exchange admin center

Exchange 2013 uses browser based Exchange Admin center for all administrative transitions / operations. I don't want to bore you with lot of details like split permissions, changes in Exchange server 2010 RTM/SP1 / SP3 and how we managed Mail enabled universal Security groups in EMC … In Exchange Server 2013 Exchange Org Admin /…


Exchange 2010: Manage "Send-As" Permission only Works on the Mailbox Server Where "Public Folder" was Created.

Exchange 2010 can only add "Send As" permissions to mail-enabled public folders for which the Owner of the AD object corresponding to the PF is an Exchange 2010 server. For Example In a environment  with many Exchange 2010 servers, If a "Public Folder" is created using Exchange 2010 server PF console on E2010 server MB01 (in Our Example),…

8

Exchange Server 2013: Fast Search Infrastructure Troubleshooting Articles.

These articles describe how to troubleshoot Fast Search issues with Exchange Server 2013.When you think the page is missing information or to be included, please leave a comment or notify the blog author.   [Troubleshooting]- Content Index 'status' shows "Failed" on all mailbox databases. [Troubleshooting]- Update 2874216 (MS13-061) breaks the content index in Exchange Server 2013. [Blog/Troubleshooting]- Exchange…

2

Exchange 2013 Search not Working (3) :NodeRunner.exe process Terminated with an "OutOfMemoryException"

Background: Microsoft Exchange Host Controller Service starts 4 worker processes, each named NodeRunner (Admin Nodes). The Individual functionality of Each NodeRunner process is conferred by  configuration. The NodeRunner.exe  which activates single Admin node in a process of its own. NodeRunner.exe is a standalone process, it derives some of the operating properties from  NodeRunner.exe.config the application configuration file during the start of Admin…


Exchange Server 2010 : Searching via OWA Fails with Error "An unexpected error occurred and your request couldn't be handled"

With Exchange 2010, you may find that performing a search via Outlook Web App (OWA) results in an error message, "An unexpected error occurred and your request couldn't be handled". Additionally, Outlook clients operating in Online Mode can search and view the results. "An unexpected error occurred and your request couldn't be handled" Request Url:…