RE: Mailbox Manager Policies

Thanks again Robert....

I ran it as you suggested and the same query/filter information shows up.
Here is an example of the policy. I am using the Store name and a department
as a rule set (Email Retention Store and "Processing"). I have tried them
seperately also:

(&(&(&(& (mailnickname=*) (|
(&(objectCategory=person)(objectClass=user)(homeMDB=CN=Email Retention
Store,CN=First Storage
Group,CN=InformationStore,CN=Servername,CN=Servers,CN=MySite,CN=Administrative
Groups,CN=NCH,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com))
)))(objectCategory=user)(department=Processing*)))

EBPA showed the same string yet my users all get the message. Any other
suggestions?


"Robert Baker [MSFT]" wrote:

> Hi Scott,
>
> Here is a way to test your search. Download the ExBPA tool from the microsoft site http://www.microsoft.com/exchange/exbpa
> Run the tool and expand the Exchange server object down through the recipient policies object. the purported serch is the LDAP
> filter used for the policy. You could use LDIFDE like this
>
> ldifde -f output.ldf -f "=(&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)
> (msExchHomeServerName=*)))(objectCategory=group) ))))" -dn
>
> This will create a report (output.ldf) that you can look at to make sure your filter is correct.
>
>
> The section between the quotes is the purported search from the exbpa output.
>
> I don't mean to be continually harping on this but I've tested this with my own systems and the only person who get the notification is
> the one person who I have filtered for. My filter was based on the email address.
>
>
> --------------------
> >Thread-Topic: Mailbox Manager Policies
> >thread-index: AcU/hACCkr1TeaR8T3SNwoupvLyfxQ==
> >X-WBNR-Posting-Host: 209.218.88.3
> >From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <EC48FA55-6E43-4886-97EB-07FDC0EED14E@xxxxxxxxxxxxx> <LC1t0BvPFHA.1960@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Mailbox Manager Policies
> >Date: Tue, 12 Apr 2005 10:21:02 -0700
> >Lines: 73
> >Message-ID: <DE517BA8-0705-4C2F-B6A4-B32A47303CC8@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.exchange.admin
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.admin:59129
> >X-Tomcat-NG: microsoft.public.exchange.admin
> >
> >Thanks Robert, but it does the same thing. I show the context of the policy
> >to apply against the one user in that particular store, my test ID. However,
> >when I run the policy by right clicking my server in the ESM and choosing
> >Start Mailbox Manager Process, it starts crawling the entire mail system, not
> >the single store I have filtered in the recipient policy. Each user gets a
> >mail message from the system attendant. Am I doing some thing wrong here?
> >
> >"Robert Baker [MSFT]" wrote:
> >
> >> Hi Scott,
> >>
> >> Test the mailbox manager policy by clicking on "Modify" and then "Find Now" This will show you the results of the LDAP filter on
> the
> >> General tab. If you only see the users on the on mailbox store then you are good to go. It won't process anything that is not within
> the
> >> scope of the filter.
> >>
> >> I hope that helps,
> >> --------------------
> >> >Thread-Topic: Mailbox Manager Policies
> >> >thread-index: AcU+rxsdpvmfD6UjQZGXGg1PJ2/WmA==
> >> >X-WBNR-Posting-Host: 209.218.88.3
> >> >From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >Subject: Mailbox Manager Policies
> >> >Date: Mon, 11 Apr 2005 08:57:04 -0700
> >> >Lines: 21
> >> >Message-ID: <EC48FA55-6E43-4886-97EB-07FDC0EED14E@xxxxxxxxxxxxx>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.exchange.admin
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.admin:58935
> >> >X-Tomcat-NG: microsoft.public.exchange.admin
> >> >
> >> >Hi all,
> >> > I have an Exchange 2003 Server with 2 stores under a single storage group,
> >> >store #1 and store #2. The goal is to define and apply a deletion of email
> >> >one year old on store #2. Store #1 should remain in tact. I have created the
> >> >Recipient Policy and used a filter rule to isolate it to Store #2 only. Now,
> >> >the issue. I recall from setting a policy when I had a single store, that if
> >> >I turn ON the mailbox manager policy, it emails all users. 9Maybe this is
> >> >because I had one store and the filter wasnt isolated??)
> >> >
> >> >My question/concern is, if I filter this process to just the #2 store and
> >> >enable the mailbox manager policy to run, will it still email the users in
> >> >store #1 even though its not under policy? The last time this happened, I had
> >> >it to report only and of cource, they freaked on me. Some even claimed they
> >> >lost email!
> >> >
> >> >I think the answer is no, it will only email/apply to users in store #2, but
> >> >I just want a little hand holding to make sure I am on the right track. Your
> >> >timely responses are greatly appreciated.
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >> --
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms
> >> specified at http://www.microsoft.com/info/cpyright.htm
> >>
> >> Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
> >> which they originated.
> >>
> >>
> >
>
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms
> specified at http://www.microsoft.com/info/cpyright.htm
>
> Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
> which they originated.
>
>
.

Relevant Pages

  • RE: Mailbox Manager Policies
    ... If you havent already try using the Advanced tab to build your query. ... >Here is an example of the policy. ... >as a rule set (Email Retention Store and "Processing"). ... >> This will create a report that you can look at to make sure your filter is correct. ...
    (microsoft.public.exchange.admin)
  • Re: Exclude Mail Store from Mailbox Management Policy
    ... Modifying the LDAP query manually ... then add the filter you put in this message to the end? ... to exclude mailboxes on that store. ... you do not want to have the policy applied. ...
    (microsoft.public.exchange.admin)
  • Re: Unable to unwrap a symmetric key using the private key of an X
    ... the certificate (public and private key) is ... installed in the personal store of both local computer and current user and I ... The problem is related to the certificate store on the web service side. ... You installed the certificate in "OtherPeople" store but the policy points ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Home Depot fires two managers
    ... Said " they violated co. policy " yea right, ... store policy, and it is a good policy, perhaps a known fine ... Thank you for contacting The Home Depot Customer Care ... violation could have put our customers and associates at greater risk, ...
    (alt.home.repair)
  • WSE3 enabled application work in WinXP but not work in Vista Business.
    ... Services host in the same development machine, the WSE policy is setup ... People Store, on Vista it is stored in the Current User->Personal ...
    (microsoft.public.dotnet.framework.webservices)