You can also access the discovery mailbox by giving another account the rights to do so. Then you can open the mailbox in Outlook and copy the search results to pst manually. Not as fast as powershell, but sometimes easier in my experience when noodling out very specific things.
On Mon, Sep 29, 2014 at 10:01 PM, Michael B. Smith <[email protected]> wrote: > Exchange 2010, starting in SP2, has some pretty decent throttling logic. > By Exchange 2013, the throttling logic is everywhere. > > > > If your mailbox servers run at load – I probably wouldn’t add more load > during business hours. > > > > If they don’t – just run the searches. If you have concern, just run one > at a time. > > > > You can export the DiscoverySearchMailbox to PST using > New-MailboxExportRequest. I do not think that it overrides GP, but what do > I know? J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Binner, Lori > *Sent:* Monday, September 29, 2014 10:44 AM > *To:* '[email protected]' > *Subject:* [Exchange] Discovery Searches - questions > > > > Hello- > > I’ve been asked to run a Discovery search on two different domains that > have sent to us or that we have sent to. I would only be searching on the > past 90 days because we purge our emails after 90 days. > > > > I’m estimating on a typical work day we typically receive 20,000 emails > and also can send out approximately 20,000 as well. This does not include > our “internal” communications which I have no idea. > > > > Thus my questions – > > > > Have others found it safe to run Discovery searches during the working > hours or should I do this after hours so I don’t accidentally cause any > system performance issues during the day for users? Or, is this not a > problem due to how the searches are performed? When searching for emails > to/from a particular outside domain, should I run the 3 months at once or > run a month at a time to help not create any issues? > > > > If I want to then take the info from the Discovery Search mailbox and > write it to .pst, is this possible? Or is it better to run a separate > (perhaps, some type of powershell) to get this to a .pst? We lock down .pst > on our users workstations via group policy so it makes it a bit difficult > for me to do this via my workstation, so again, is there a better, say > administrative command or way to do this? > > > > We are currently running Exchange 2010 RU2 SP3 > > > > Thank you very much for your help and feedback in advance. >
