asked on
Exchange 2010 - Database policies - do they exist??
Running Exchange 2010 here.
I want to create policies to apply to a certain set of my databases, for items like storage limits, maintenance schedule, etc. Basically all the information you see when you go to a DB properties page.
I could do this in Exchange 2003 no issue.
I just can't seem where to create a policy in Exchange 2010, and then apply that policy to my databases.
I really don't want to manage these settings on each DB separately. That is prone to human error, and creates a lot of work when changes need to be made. I have 30 DB's currently.
Anyone know how to do this?
I want to create policies to apply to a certain set of my databases, for items like storage limits, maintenance schedule, etc. Basically all the information you see when you go to a DB properties page.
I could do this in Exchange 2003 no issue.
I just can't seem where to create a policy in Exchange 2010, and then apply that policy to my databases.
I really don't want to manage these settings on each DB separately. That is prone to human error, and creates a lot of work when changes need to be made. I have 30 DB's currently.
Anyone know how to do this?
Exchange
Last Comment
Vjz1
ASKER
i can use the EMS pretty easily, just need to know the commands.
do you have a MSKB or any doc that outlines the functions that used to be in the "Mailbox Policy" settings in 2003? That's what I'm looking for.
do you have a MSKB or any doc that outlines the functions that used to be in the "Mailbox Policy" settings in 2003? That's what I'm looking for.
Hi,
The Set-MailboxDatabase cmdlet would be your friend along with Get-MailboxDatabase .. use them piped...like
Get-MailboxDatabase | Set-MailboxDatabase -ProhibitSendQuota <<numbers>>
Thanks
Nitin
The Set-MailboxDatabase cmdlet would be your friend along with Get-MailboxDatabase .. use them piped...like
Get-MailboxDatabase | Set-MailboxDatabase -ProhibitSendQuota <<numbers>>
Thanks
Nitin
ASKER
ok so while i can see this would be useful to set the values initially, it doesn't restrict anyone from making a change through the EMC per database.
in 2003, the policy would grey out all those options, so they couldn't be edited, just from the policy.
Is there no way to do that in 2010?
in 2003, the policy would grey out all those options, so they couldn't be edited, just from the policy.
Is there no way to do that in 2010?
I am not sure if I got your question. Well if you give permissions to people then they can obviously change it
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Use Powershell (EMS) to achive this....pretty straight forward.
Let me know
Thanks
Nitin Gupta (gupnit)