Prev: EdgeSync
Next: copy of exchange 2000
From: HankC on 15 Feb 2010 11:45
MRM can only be applied at the mailbox level, is this correct?

Sounds like the policy needs to be applied to each mailbox as they are
created and policies removed and applied as people change roles (from
HR to Marketing, say).

Is there any way to apply the MRM policy to a mailbox based on the
user's mailbox server without running the 'Set-Mailbox -Identity -
ManagedFolderMailboxPolicy' cmdlet every time a user changes jobs?

In Exchange 2003, these policies were set based on an ldap filter...


TIA,
HankC
From: Rich Matheisen [MVP] on 15 Feb 2010 17:51
On Mon, 15 Feb 2010 08:45:11 -0800 (PST), HankC <clarkc(a)missouri.edu>
wrote:

>MRM can only be applied at the mailbox level, is this correct?

That's correct.

>Sounds like the policy needs to be applied to each mailbox as they are
>created and policies removed and applied as people change roles (from
>HR to Marketing, say).

How you decide which policy applies to which user is something you'll
have to decide.

>Is there any way to apply the MRM policy to a mailbox based on the
>user's mailbox server without running the 'Set-Mailbox -Identity -
>ManagedFolderMailboxPolicy' cmdlet every time a user changes jobs?

You could create a powershell script that verifies the correct policy
is applied on each mailbox and, if not, applies the appropriate
policy. Schedule the script to run periodically. What that period will
be depends on your company. You could also automate the "job change"
procedure and make the change at that time.

>In Exchange 2003, these policies were set based on an ldap filter...

Same idea in 2007 except you get to customize it. The application of
"policy" in Exchange 2003 was spotty, at best.
---
Rich Matheisen
MCSE+I, Exchange MVP
 | 
Pages: 1
Prev: EdgeSync
Next: copy of exchange 2000