The SQL job Assign Security to All Messages calls another SQL job, Assign Security to New Messages, which in turn sets message security and assigns messages to mailboxes for a single designated 24-hour period. The Assign-to-All job calls the Assign-to-New job iteratively, 10 times (by default), to be applied to the most recent 10 days.
Notes:
The number of Assign-to-New iterations constitutes a date/age limit for messages to be processed, set to 10 days by default. But that default setting can be changed to some other value in the Archive Manager Configuration Editor, by the PopulateMailboxMessageDays parameter.
Note that, regardless of the threshhold limit value, the Assign-to-New job does not re-process messages that have already been processed by a prior run of the job. But the job is meant to be re-applied to past days as a way of catching messages that for various reasons may have been missed in prior runs. Most admins feel that 10 is a reasonable number of daily re-iterations to assure that all messages are eventually processed, but the PopulateMailboxMessageDays parameter now lets an admin set some other threshhold.
In Archive Manager versions prior to 4.1.1: The Assign Security to All Messages SQL job set message security and assigned all previously unprocessed messages to mailboxes, with no message age limit, while the Assign Security to New Messages job called the Assign-to-All job and additionally added messages to virtual mailboxes. The two jobs were redesigned for 4.1.1 with the configurable threshhold, as a performance enhancement to bypass the repetitive rescanning of older messages, since most admins felt that rescanning beyond a certain age (typically 10 days) was unnecessary.
