A parameter cannot be found that matches parameter name ‘DeleteContent’

exchange-2013

I am attempting to run this command:

Get-Mailbox | Search-Mailbox -SearchQuery '(Received:01/01/2010..31/12/2013)' -DeleteContent

but I receive error message:

A parameter cannot be found that matches parameter name 'DeleteContent'.

I have searched this error message online and viewed other solutions like ensuring the account has Mailbox Import Export Role. I checked and this role is part of Organization Management, which Administrator is a member of.

Best Answer

Your user must be assigned the roles: Discovery Management and Mailbox Import Export role.

https://technet.microsoft.com/en-us/library/dd638205(v=exchg.150).aspx

Related Solutions

Exchange CU 10 Install Error

Update: I have now determined that this error was occurring because of a trust relationship with another forest that was unavailable during the installation of the CU. I have recreated the problem and every time the old trust that is no longer being used is still listed under trusts in the Domains and Trusts dialog, the error occurs. Simply removing no longer needed, no longer used trust allows the installation to complete without needing to delete (or do anything with) the discovery search mailbox. Just wanted to update so that this might help someone else facing the same issue.

Exchange 2016 Co-Existence – OWA Won’t login when behind a load balancer

I ended up reasonably working around this issue. Several posts had mentioned for similar issues that adding Cookie-based persistence on their load balancer had solved the issue for them.

I had resisted this "because I shouldn't have to", all the technical articles from Microsoft say this is no longer needed, and indeed not recommended.

But I caved, and ended up adding persistence for both OWA and ECP. The result was the issue was not completely resolved, but it became barely noticeable. The only time I experience issues is if I log out of OWA on one mailbox, and then immediately log into another. Even then, it kicks you out once, but if you try to login again it works fine.

There is no ongoing issue after this. Furthermore, I noticed the remaining issue only when moving from a 2013 to 2016 mailbox.

This isn't something our end users are likely to do, and we're nearly finished moving all our mailboxes to 2016. So I'm considering this work around "good enough".

Since we're using HA Proxy, it wasn't a big deal to add some layer 7 cookie-based persistence in the config. In fact, it only took about 5 minutes all up to figure out:

# HTTPS Outlook Web App (OWA)
backend bk_EXCHANGE_https_owa
  cookie LB01 insert indirect nocache # <-- Added this
  balance roundrobin
  mode http

  ...

  # Added the "cookie <name>" at the end of each CAS node definition
  # These names must be unique to each node.
  server n1_exch16_syd_01 172.16.10.2:80 maxconn 1000 weight 10 check cookie EXCH16-SYD-01
  server n1_exch16_syd_02 172.16.10.3:80 maxconn 1000 weight 10 check cookie EXCH16-SYD-02
  server n1_exch13 172.16.10.1:80 maxconn 1000 weight 10 check cookie EXCH13-SYD

Best Answer

Related Solutions

Exchange CU 10 Install Error

Exchange 2016 Co-Existence – OWA Won’t login when behind a load balancer

Related Topic