none
Retention policy is not working

    Frage

  • I created retention policy for clear the junk e-mail folder daily. The following is detail setting. I monitoring 1 week but found it's not working. That's mean it haven't clear the email junk e-mail folder. But it's working if I ran the PS Start-ManagedFolderAssistant -Identity <email_address>. So I'm not sure any setup or procedure missed in this retention policy or server.

    Created a retention policy tag (tag type: Junk E-mail / age limit for retention: 1 / action: permanently delete)

    Created a retention policy (type: Junk E-mail / action: permanently delete / age limit for retention: 1 / retention enabled: true / mailboxes: my testing mailbox)

    Thanks!!

    Freitag, 15. Juni 2012 03:28

Antworten

  • My question is the retention policy, not the managed folder assistant. BTW, thanks all for the knowledge sharing.

    In Exchange 2010 SP1, the Managed Folder Assistant is a throttle-based assistant. Throttle-based assistants are always running and don't need to be scheduled. The system resources they can consume are throttled. You can configure the Managed Folder Assistant to process all mailboxes on a Mailbox server within a certain period (known as a work cycle).

    Note: If we have large number of Email items which needs to be processed due to retention period exceeded, then in such case it is not necessary Mailbox assitant will delete all the Emails as per the retneion Policy tags within the same workcycle. Mailbox assistant runs 24 hours in the background and it is throttle-based and will try to utilize minimum resource during production hours and will delete only few set of Emails and keep rest of the left Emails pending for next work cycle. If we manually run the start-ManagedFolderAssistant for the User mailbox then it will forcefully deleted all the Email items which have exceeded retention Limit as per retention settings without waiting for the work cycle to process on every email items.

    Running the Start-ManagedFolderAssistant is a resource-intensive process, especially when it's run for the first time. The first time the Managed Folder Assistant runs, it typically processes a large number of items. This can be a resource-intensive process for the Mailbox server and the network. It can also result in Microsoft Outlook clients consuming large amounts of time and network resources while synchronizing with the server. Be sure to plan carefully to avoid overloading resources.

    You should run the Managed Folder Assistant only when your server can tolerate the extra load. This is usually during off-peak hours. You should also run the Managed Folder Assistant often enough to meet your organization's message retention requirements.

    http://technet.microsoft.com/en-us/library/bb123958.aspx

     


    Thank you, Anil Yadav


    • Als Antwort markiert everSSS Donnerstag, 12. Juli 2012 04:45
    Freitag, 22. Juni 2012 02:41

Alle Antworten

  • Hi

    Here is an article on how the retention age is calculated:

    http://technet.microsoft.com/en-us/library/bb430780.aspx

    Freitag, 15. Juni 2012 05:49
  • In Exchange 2010 SP1, the Managed Folder Assistant is a throttle-based assistant. Throttle-based assistants are always running and don't need to be scheduled. The system resources they can consume are throttled. You can configure the Managed Folder Assistant to process all mailboxes on a Mailbox server within a certain period (known as a work cycle).

    Note: If we have large number of Email items which needs to be processed due to retention period exceeded, then in such case it is not necessary Mailbox assitant will delete all the Emails as per the retneion Policy tags within the same workcycle. Mailbox assistant runs 24 hours in the background and it is throttle-based and will try to utilize minimum resource during production hours and will delete only few set of Emails and keep rest of the left Emails pending for next work cycle. If we manually run the start-ManagedFolderAssistant for the User mailbox then it will forcefully deleted all the Email items which have exceeded retention Limit as per retention settings without waiting for the work cycle to process on every email items.

    Running the Start-ManagedFolderAssistant is a resource-intensive process, especially when it's run for the first time. The first time the Managed Folder Assistant runs, it typically processes a large number of items. This can be a resource-intensive process for the Mailbox server and the network. It can also result in Microsoft Outlook clients consuming large amounts of time and network resources while synchronizing with the server. Be sure to plan carefully to avoid overloading resources.

    You should run the Managed Folder Assistant only when your server can tolerate the extra load. This is usually during off-peak hours. You should also run the Managed Folder Assistant often enough to meet your organization's message retention requirements.

    http://technet.microsoft.com/en-us/library/bb123958.aspx

     


    Thank you, Anil Yadav

    Sonntag, 17. Juni 2012 19:52
  • My question is the retention policy, not the managed folder assistant. BTW, thanks all for the knowledge sharing.

    In Exchange 2010 SP1, the Managed Folder Assistant is a throttle-based assistant. Throttle-based assistants are always running and don't need to be scheduled. The system resources they can consume are throttled. You can configure the Managed Folder Assistant to process all mailboxes on a Mailbox server within a certain period (known as a work cycle).

    Note: If we have large number of Email items which needs to be processed due to retention period exceeded, then in such case it is not necessary Mailbox assitant will delete all the Emails as per the retneion Policy tags within the same workcycle. Mailbox assistant runs 24 hours in the background and it is throttle-based and will try to utilize minimum resource during production hours and will delete only few set of Emails and keep rest of the left Emails pending for next work cycle. If we manually run the start-ManagedFolderAssistant for the User mailbox then it will forcefully deleted all the Email items which have exceeded retention Limit as per retention settings without waiting for the work cycle to process on every email items.

    Running the Start-ManagedFolderAssistant is a resource-intensive process, especially when it's run for the first time. The first time the Managed Folder Assistant runs, it typically processes a large number of items. This can be a resource-intensive process for the Mailbox server and the network. It can also result in Microsoft Outlook clients consuming large amounts of time and network resources while synchronizing with the server. Be sure to plan carefully to avoid overloading resources.

    You should run the Managed Folder Assistant only when your server can tolerate the extra load. This is usually during off-peak hours. You should also run the Managed Folder Assistant often enough to meet your organization's message retention requirements.

    http://technet.microsoft.com/en-us/library/bb123958.aspx

     


    Thank you, Anil Yadav


    • Als Antwort markiert everSSS Donnerstag, 12. Juli 2012 04:45
    Freitag, 22. Juni 2012 02:41
  • everSSS how did you resolve this issue?

    Thanks

    Donnerstag, 11. Oktober 2012 11:10