• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 634
  • Last Modified:

Mailbox Manager/System attendant shows no mailboxes processed

I have read previous support questions found here on this topic and reviewed the help tip at Exchange.org. The Default Recipient Policy looks like it is set correctly. Yet, no mailboxes are processed accourding to the System Attendant. Notice the processing time of a few seconds.

The Microsoft Exchange Server Mailbox Manager has completed processing mailboxes
Started at:      2006-05-07 01:06:35
Completed at:      2006-05-07 01:06:37
Mailboxes processed:      0
Messages moved:      0
Size of moved messages:      0.00 KB
Deleted messages:      0
Size of deleted messages:      0.00 KB

I don't recall the response from the System Attendant ever processing any mailboxes. I also don't know where else to look for further information as to how to make this process the mailboxes in our infor store.

What would cause the Mailbox Manager to not process any mailboxes? How do I check to see if the policy is even applied correctly? Should I create another policy and if so, what is the effect of that policy on the existing policy?

Thanks...
0
-Garren-
Asked:
-Garren-
  • 3
  • 2
1 Solution
 
SembeeCommented:
I always recommend that a second policy is created for mailbox manager. The best practise is not to change the default policy in any way.
As long as you replicate the default policy, it shouldn't affect the operation of Exchange. Make sure that you get all settings correct. The only thing that will be different is the filter - as this is what you want to change to include users who need to have their mailbox managed.

Simon.
0
 
-Garren-Author Commented:
That is interesting... been afraid to crate a new policy because I don't understand how it works. So the default policy doesn't really do much then does it? So you can create a policy that will move or delete messages after a set amount of time. What is a standard practice here? I know it depends on the amount of disk space but what other practices would apply.

Also, when you apply a new policy, are the policies cummulative? Do they combine to form a dynamic policy?

Thanks for the help on this...
0
 
SembeeCommented:
The default policy sets the default information on the domain.
That will typically include the domain name that you originally configured when setting up Exchange and that all email addresses are username@

The default policy is the lowest priority. When you create a new recipient policy, they take a high priority. You can then change the order of the policies around so that certain policies have more priority than others. Combined with the filtering capabilities you can do some pretty clever stuff.

Therefore you need to be careful that the policy does what you need it to, so that email addresses are changed etc - hence my point above about replicating the recipient policy before trying to do anything else.

Recipient Policy is most often used to add new domains to the Exchange server. That is what tells Exchange what domains it is responsible for.

For example, if I have a new domain where there will be limited numbers of users who need to have an email address on that domain, I will usually create a separate policy for that domain, then change the user individually.

Simon.
0
 
-Garren-Author Commented:
OK... so replicate the default and leave it at that... then add yet another policy to do "special" stuff that I might want to apply. Is that about it?

Again, thanks for the help.
0
 
SembeeCommented:
The practise is to use a separate policy for email and another policy for other tasks. It is an awful way of working - what mailbox manager has to do with recipient policy is anyone's guess. However we have to live with it.

Simon.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now