Exchange retention policy - is it possible to automatically apply to new mailbox?

We are using Exchange 2010 (soon to migrate to 2016).

I recently setup a retention policy to automatically delete email in the 'Deleted Items' which have been there longer than a year.

This has been applied to a number of test users and I would now like to roll it out to all users.

Is there a way to automatically apply this retention policy to any new mailboxes that we create?  Or is it a case of having to manually add them?

Thank you
fieldjAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CodeTwo SoftwareSoftware DeveloperCommented:
Hi fieldj,
When you migrate to 2016 - you can configure the default MRM policy (https://technet.microsoft.com/en-us/library/dn775046%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396) and this will be automatically applied to any new user. Unfortunately, this functionality has been introduced in Exchange 2013 so the only way to make it "automatic" in your case would be to run a daily script to assign your policy to the freshly created users.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fieldjAuthor Commented:
That is really helpful.   Thanks.  

In that case I wont bother trying to do anything too clever on our existing 2010 server, but will ensure that it is configured correctly when we migrate to 2010.
CodeTwo SoftwareSoftware DeveloperCommented:
Good thinking! You will have enough to worry about with the migration project anyway, no need to complicate things any further.
fieldjAuthor Commented:
Of course I meant "when we migrate to 2016"!
fieldjAuthor Commented:
great answer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.