To configure a Dynamic Distribution Group in Exchange 2010, you can do it in two ways:
1. From EMC
in Recipient Configuration > Distribution Group, right click on a existing Dynamic Distribution Group and select Properties. Go to Filter and Conditions tabs and select the appropriate settings.
2. From EMS
you will only find a few conditions/filters that you can choose from in the GUI. So you will have to use EMS to fine tune your DDG.
For example, if you want to filter the members of a Dynamic Distribution Group by city, you can use it to query users that have the City attribute assigned.
To change the existing Dynamic Distribution Group which uses LDAP filter to use OPATH filter you use:

If you don't want to export it locally, you need to configure the network share in which the permissions for Exchange Trusted Subsystem are set to read/write.
Pipe Get-MailboxExportRequest into the Get-MailboxExportRequestStatistics cmdlet and you will get detailed information regarding your export.
When it finishes, the request remains on the server until removed by an administrator using Remove-MailboxExportRequest.
To clear all your Exchange requests:

Check if you Client Access Server is listed in: 001e6602
If the dca740c8c042101ab4b908002b2fe182 key or the 001e6602 string is missing, stop the BlackBerry Mail Store Service, and create the missing key or string.
Enter the Fully Qualified Domain Name of the correct Client Access Server or the pool name under Value data in 001e6602
Also, check if the string 001e6602 exists in:

This will take all folders and data and export them into the specified .pst file.If we want to add different parameters, we can find them hereBe careful, as in Exchange 2010 (non SP1 version) the command was different:

Export-mailbox -Identity webkod -PSTFolderPath c:\pst

There are a lot of new features in SP1's version of Exchange 2010, but if you still have the previous version, check out this tutorial on how you can export the mailbox.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {} to the user SID (). This security permission can be modified using the Component Services administrative tool.

The Active Directory Installation Wizard cannot continue because the forest is not prepared for installing Windows Server 2003. Use the Adprep command-line tool to prepare both the forest and the domain. For more information about using the Adprep, see Active Directory Help.

The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer.