Exchange Tasks 2010 Frequently Asked Questions

Frequently Asked Questions (FAQ) about Exchange Tasks 2010, U-BTech's ADUC add-on for managing Microsoft Exchange 2010 recipients.

Published: |

Click any question to view its answer.


Does Exchange Tasks 2010 extend the Active Directory schema?

Absolutely not!

Exchange Tasks 2010 adds configuration settings to Active Directory objects called displaySpecifiers.

You can read more about them here:

Which credentials do I need to provide within Exchange Tasks 2010 installation, and why?

You should provide the credentials of an Enterprise Admin or equivalent, in order to perform changes in the Configuration partition of Active Directory.

This partition holds the objects called displaySpecifiers (see previous question).

Exchange Tasks 2010 requires the credentials in order to make the required changes during setup.

The credentials are sent securely to the domain controller for authentication and are discarded immediately after the configuration changes.

The privileged user is required only once. In the first installation of Exchange Tasks 2010, or when upgrading to a newer version.

So each installation will require these credentials to install Exchange Tasks 2010 ?

No. as stated in the previous question:

The privileged user is required only once. In the first installation of Exchange Tasks 2010 , or when upgrading to a newer version.

You could issue a quick and silent install after running an installation with the required credentials with the following command:

  msiexec.exe /i exchange-tasks-2010.msi /qb

Note: Local administrator permissions are still required for the installation.

What are the minimum requirements for installing Exchange Tasks 2010?

Exchange Tasks 2010 as an application has the following prerequisites:

  • Any Windows OS above and including Windows XP Service Pack 2,
    Windows XP SP2 and Windows Server 2003 SP1 require the latest Windows Server 2003 Administration Tools Package (adminpak.msi)
    Windows Vista, Windows 7, Windows 2008 and Windows 2008 R2 require the Remote Server Administration Tools (RSAT) for Active Directory Domain Services to be installed.
  • At least one Exchange Server 2010 Client Access Server available in the Active Directory environment.
  • Windows Management Framework Core package - Windows PowerShell 2.0 and WinRM 2.0 (Not required when running Windows 7 and Server 2008 R2)
  • .NET Framework 3.5 or above
  • A connection to an Active Directory domain

What sort of permissions do I need in order to manage a mailbox using Exchange Tasks 2010?

Exchange Tasks 2010 uses the built-in PowerShell cmdlets and commands for mailbox management.

Each command has different permission requirements.

To read about the commands follow this link:

Import / Export Mailbox keeps failing! HELP!

Exchange 2010 RTM Only - For Export/Import mailbox feature, the requirements are:

  • The RBAC role assignment to the required group/user:
     New-ManagementRoleAssignment –Role:"Mailbox Import Export" –User:HelpDesk
  • Outlook 2010 64-Bit installed on the Exchange servers , rather the CAS servers, as Exchange Tasks connects to a CAS server as a preference.

Why am I getting all sorts of COM and DLL error messages when trying to run certain tasks?

Exchange Tasks 2010 uses the Exchange Server 2010 Management Snap-In to manage mailboxes and run the different commands and tasks.

This snap-in has some known compatibility issues with the Exchange Server 2003 management tools.

Try removing them and everything should start working.

The ADM (Administrative Template) included with Exchange Tasks 2010 doesn't work, why?

While the ADM is included in every version of Exchange Tasks 2010, only the Premium edition of Exchange Tasks 2010 supports these GPO changes.

I installed Exchange Tasks 2010 but I don’t see any changes in the action or properties menu.

This is mostly caused by two reasons:

  1. The credentials provided in the “Active Directory Authentication” screen during the installation were not privileged for the Configuration partition in Active Directory.
  2. You’re not using the default Active Directory Users and Computers snap-in. If you’ve created custom management snap-ins, you might need to create them again.
  3. If the above two does not apply to you, try to uninstall our prodcut, delete the following registry key, and reinstall Exchange Tasks: HKEY_CLASSES_ROOT\CLSID\{F9168C5E-CEB2-4FAA-B6BF-329BF39FA1E4}\

How can I find if there are any updates available to Exchange Tasks 2010?

That’s simple. Just go to the About dialog and click on the ‘Check for Updates’ link.

Customers who purchased our retail products are automatically added to our mailing list and receive email notifications about updates and news.

I need to activate my product and I don’t have a working Internet connection from my workstation, what can I do?

You can use our offline activation web page where you can use your purchased serial code and unique machine code to activate your license and receive an offline activation code. The serial code is your proof of purchase and the machine code, which will be provided by each of our products on its offline activation dialog, is our way of verifying the use of the license on a single machine.

I've received an error while trying to activate my license using the Offline activation web page, What should i do ?

You are welcome to contact our support staff, please send your information and machine code to and we will activate the product for your purchased license and send you back your license code.

I need more time with the Trial version, who should I contact?

You can contact our sales department at

They will consider each request and decide whether to provide you with a trial extension key.

Exchange Tasks 2010 looks great. What is the licensing scheme for it?

Exchange Tasks 2010 uses a per user, per machine licensing method.
You have to purchase a single license for each user who is going to manage recipient mailboxes using Exchange Tasks 2010 and that license can be activated twice on that machine for maintenance reasons (operating system reinstallation for example).


Additional Help


comments powered by Disqus