The article I used as a guide was: http://technet.microsoft.com/en-us/library/dd335072.aspx I was using ECP to create the search and the error I am getting is: "Search failed as the results link to the target mailbox 'DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}@domain.obfuscated' couldn't be generated." I am not getting any hits on this search in Google (except for a copy of a previous post, which really surprises me!) "Search failed as the results link to the target mailbox" so maybe I am the only one running into this? SnoBoy

Hi SnoBoy, Can you search in the EMS? Create a Discovery Search http://technet.microsoft.com/en-us/library/dd353189.aspx Please make sure you are assigned the permission to run a search.Frank Wang

First, a little explanation. I had posed a general question on open records requests. I got some helpful answers relating to the old Exchange 2007 system, but wanted to try out the new Discovery Search capabilities in Exchange 2010, since we are in transition to that system and have a number of mailboxes, including my own on the Exchange 2010 system. I have the search term I have been using in my tests in my own mailbox in several email messages, both in the Inbox and in the Deleted Items, so I should be getting results. The account I am using in my testing is a member of Organizationn, Recipients and Discovery Management groups. I always get the message above when running the search from ECP, so per your suggestion, I tried it from the EMS as well. The same message appears in ECP after running it from the Shell, but the output from the Shell concerns me. Here it is with some details obfuscated to protect confidentiality: RunspaceId : e57ace97-bc85-4637-b42d-3ab103c32f03 Identity : 6b7fc7f6-0b52-4ce4-b5b1-5f15f8f8b30e Name : search_name CreatedBy : domain\username SourceMailboxes : {} TargetMailbox : domain_name/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} SearchQuery : "Search_term" Language : en-US Senders : {} Recipients : {} StartDate : EndDate : MessageTypes : {email} SearchDumpster : True IncludeUnsearchableItems : True DoNotIncludeArchive : False EstimateOnly : False ExcludeDuplicateMessages : True Resume : False LogLevel : Full StatusMailRecipients : {} Status : InProgress LastRunBy : My_Display_Name LastStartTime : 11/15/2010 8:55:26 AM LastEndTime : NumberMailboxesToSearch : 0 PercentComplete : 0 ResultNumber : 0 ResultNumberEstimate : 0 ResultSize : 0 B (0 bytes) ResultSizeEstimate : 0 B (0 bytes) ResultSizeCopied : 0 B (0 bytes) ResultsLink : Errors : {} KeywordHits : {} FWIW, I also ran the Test-ExchangeSearch commandlet on my account and got these results: Database Server Mailbox ResultFound SearchTime Error InSeconds -------- ------ ------- ----------- ---------- ----- Mailbox D... Server MyDisplayName True 3.547 No output was obtained from the Get-FailedContentIndexDocuments commanglet. My concern is that it should have results, not 0k bytes of output. My account is also a member of the Exchange Organization Administrators group - membership in other groups won't negate being in the correct groups will it(except possibly the Exchange View-Only group, which I am not a member of)? SnoBoy

First, a little explanation. I had posed a general question on open records requests. I got some helpful answers relating to the old Exchange 2007 system, but wanted to try out the new Discovery Search capabilities in Exchange 2010, since we are in transition to that system and have a number of mailboxes, including my own on the Exchange 2010 system. I have the search term I have been using in my tests in my own mailbox in several email messages, both in the Inbox and in the Deleted Items, so I should be getting results. The account I am using in my testing is a member of Organizationn, Recipients and Discovery Management groups. I always get the message above when running the search from ECP, so per your suggestion, I tried it from the EMS as well. The same message appears in ECP after running it from the Shell, but the output from the Shell concerns me. Here it is with some details obfuscated to protect confidentiality: RunspaceId : e57ace97-bc85-4637-b42d-3ab103c32f03 Identity : 6b7fc7f6-0b52-4ce4-b5b1-5f15f8f8b30e Name : search_name CreatedBy : domain\username SourceMailboxes : {} TargetMailbox : domain_name/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} SearchQuery : "Search_term" Language : en-US Senders : {} Recipients : {} StartDate : EndDate : MessageTypes : {email} SearchDumpster : True IncludeUnsearchableItems : True DoNotIncludeArchive : False EstimateOnly : False ExcludeDuplicateMessages : True Resume : False LogLevel : Full StatusMailRecipients : {} Status : InProgress LastRunBy : My_Display_Name LastStartTime : 11/15/2010 8:55:26 AM LastEndTime : NumberMailboxesToSearch : 0 PercentComplete : 0 ResultNumber : 0 ResultNumberEstimate : 0 ResultSize : 0 B (0 bytes) ResultSizeEstimate : 0 B (0 bytes) ResultSizeCopied : 0 B (0 bytes) ResultsLink : Errors : {} KeywordHits : {} My concern is that it should have results, not 0k bytes of output. My account is also a member of the Exchange Organization Administrators group - membership in other groups won't negate being in the correct groups will it(except possibly the Exchange View-Only group, which I am not a member of)? SnoBoy

Hi SnoBoy, Could you please post the cmdlet you run here? From the Output: Status : InProgress If the search is finished, the status should be Successed. Please run the cmdlet Get-MailboxSearch search_name to check. And there will be a search result in the ECP as well: Manage My Organiation->Mail Control->DiscoveryFrank Wang

Commandlet I ran: new-mailboxsearch -name Test1 -targetmailbox "Discovery Search Mailbox" -searchquery "QueryTerm" -messagetypes email -includeunsearchableitems -loglevel full Output (italics indicate obfuscation) from get-mailboxsearch test1 commandlet: RunspaceId : bcadfee6-a364-4889-b4dc-b8439f03b0a8 Identity : 41812a01-fa43-4ab0-bdc1-1f21099fd917 Name : Test1 CreatedBy : domain\myID SourceMailboxes : {} TargetMailbox : domain/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} SearchQuery : QueryTerm Language : en-US Senders : {} Recipients : {} StartDate : EndDate : MessageTypes : {email} SearchDumpster : True IncludeUnsearchableItems : True DoNotIncludeArchive : False EstimateOnly : False ExcludeDuplicateMessages : True Resume : False LogLevel : Full StatusMailRecipients : {} Status : Failed LastRunBy : MyDisplayName LastStartTime : 11/16/2010 10:44:26 AM LastEndTime : NumberMailboxesToSearch : 24 PercentComplete : 0 ResultNumber : 0 ResultNumberEstimate : 2446 ResultSize : 0 B (0 bytes) ResultSizeEstimate : 1.904 GB (2,044,612,255 bytes) ResultSizeCopied : 0 B (0 bytes) ResultsLink : Errors : {"Search failed as the results link to the target mailbox 'DiscoverySearchMailbox{D919BA05-4 6A6-415f-80AD-7E09334BB852}@domain could n't be generated."} KeywordHits : { QueryTerm 20 313.3 KB (320,791 bytes) 2} Note: I also tried creating a new Discovery Search Mailbox, but got the same results when directing output to it as well.. SnoBoy

Hi SnoBoy, Could you please run the EXBPA and post the error message here?Frank Wang

Thisi sis going to take a while since .NET 1.1 isn't required or supported by Exchange 2010, I don't have it installed, but is required by ExBPA 2.8. So I will have to patch and restart and since this is a production server, will have to do that overnight. Just wanted you to know I am not ignoring you, it is just going to take some time.SnoBoy

RUnning the BPD from the EMC, Tools, with the Health Check option chosen (you didn't specify which one to run) , I get: Organization incoming message size too high Organization: ORGANIZATION The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is 52.26171875 MB. Set to 52MB – our organizations external mail gateway’s default – still complains, no performance issues noted! Organization outgoing message size too high Organization: ORGANIZATION The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is 52.26171875 MB. Set to 52MB – our organizations external mail gateway’s default – still complains, no performance issues noted. Multiple default gateways detected Server: SERVER More than one network interface on server SERVER has a default IP gateway listed. Communication errors may occur if these network connections link to independent subnets. The other gateway is the internal interface to the iSCSI storage. DNS search order is blank Server: SERVER The DNS search order for network interface '[00000008] Intel(R) PRO/1000 MT Network Connection' on server SERVER is blank. Exchange relies on domain name system lookups to resolve other server names. DNS search order is blank Server: SERVER The DNS search order for network interface '[00000013] Intel(R) PRO/1000 MT Network Connection' on server SERVER is blank. Exchange relies on domain name system lookups to resolve other server names. These interfaces are for iSCSI use only. VMware detected Server: SERVER Exchange server SERVER appears to be running as a virtual machine. Please review the system requirements detailed at http://go.microsoft.com/fwlink/?LinkId=148058. No violations of the requirements. PDC emulator is not excluded from the Active Directory Access (ADAccess) topology Server: ORGANIZATIONMAIL A recommended value for the 'MinUserDc' registry entry on server 'ORGANIZATIONmail.ORGANIZATION.tamus.edu' should be between 1 and 3. As a best practice, create this registry entry to avoid overloading the PDC emulator. Added the registry entry of 3, but still reports same info on rerun of BPA – perhaps a server restart is required? If you want a different option chosen when running BPA, let me know. SnoBoy

I have an answer for the errors I was seeing. Although the documentation doesn't tell you so, the Discovery Search Mailbox is disabled by default, at least it was on my system. I went into the ECP website and ran a test search. I finally got a folder in the DSM for the test results, but it errored out and gave no results. Then I reran the exact same search, except I clicked the logging checkbox. Then I actually got the results that I was looking for. Odd!SnoBoy