Showing posts from October, 2013

Exchange 2010 Multi-Mailbox search fails over 100mb

Hi All We are now coming to the end of our Exchange 2010 upgrade project and everything has gone pretty well so far. From time to time our administrators are asked to complete searches in Exchange.  This could be for a number of reasons e.g Data Protection request or a disciplinary query. In Exchange 2007 we used to complete multi mailbox searches using a third party tool which would use MAPI to search every users' mailbox for items which matched our search terms.  This process was extremely slow (90 hours to cover 2000 mailboxes) and not particular reliable. In Exchange 2010 Microsoft released a feature called Multi-Mailbox search.  This allowed administrators to search all of the mailboxes using the search index which is built into Exchange.  This means the searches in Exchange 2010 are much much quicker.  It also means that this search will look at attachments which is excellent, although does create far more results to review. MSExchange Link for more information on M

Solarwinds - Error: "Network connection failed. HResult: No

During our Exchange 2010 upgrade project we noticed the monitoring on one server stopped working. We use a product called Solarwinds, this uses a combination of Powershell, WMI and SNMP to monitor services on hardware and software from around the business. We noticed that Solarwinds would return the following error message when polling this particular server Network connection failed. HResult: No data to return. Error: Unable to connect to the specified computer, or the computer is offline. After a quick search online we found the following Solarwinds KB It recommends restarting the WMI service on the server. We completed this but the issue remained. One of my learned colleagues kept searching and found that the Remote Regsitry service was set to Manual. He set it to Automatic and started the server. Immediately the polling began to work! So if you have this problem, check the Remote Registry service! Sam Cheers to John Manley for finding this! Google +