vWorld.nl

By default Outlook 2003 doesn’t support encryption towards the Exchange server. Enable it using the mail settings or disable encryption traffic on the exchange server :

The last time I ran into a few problems with Activesync and Exchange 2010.

First, Activesync with Exchange 2010 doesn’t work when you have an admin account.  You get a strange error (HTTP Options not allowed). Remove your account from the domain admins group for example and it should be working fine.

Activesync still not working? One customer changed the default domain policy. The following settings are important :

Still not working ?

Open dsa.msc (Active Directory Users and computers). Enable the advanced option under view.

Now check out the properties of the account who is trying to sync.

Select Security / Advanced.

Enable the include inheritable permissions from this object’s parent.

Check it out here (mirror : Configuring Exchange 2010 Certificates )

Found it here  (PDF:MailboxMoveInExchange2010)

Use the following commando to disable OWA and Activesync for everyone :

get-Mailbox -ResultSize Unlimited| set-CASMailbox -ActiveSyncEnabled:$False -OwaEnabled:$False

You can then create an CSV to enable OWA and Activesync for specific users :

Create a CSV with one column named UserPrincipalName and below it the users defined for which it needs it be active: import-csv c:\ActiveSync.csv | foreach-object {set-CASMailbox -identity $_.UserPrincipalName -…

Some mailboxes may be reported as failed in your mailbox move report, with the following error information:

Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262.

Check the properties of the account in Active Directory Users & Computers and you should find that the account is disabled.  Exchange will not move a mailbox for a disabled user account.  Your options here are to enable the account temporarily while you move the mailbox, or just delete the mailbox from your legacy Exchange server.

Before :

After ;

Microsoft recommends using the PFDAVADMIN utility from a workstation, not from the console of the Exchange server, though. If you get this message, do NOT install the v1.1 Framework on an existing Exchange 2007 server. You run the risk of resetting some of the v2.0 Framework settings and, thus, breaking Exchange Server 2007! If you want to run PFDAVADMIN from the console of an Exchange 2007 server, you need to install the v1.1 .NET Framework prior to building Exchange. Thus, the “workstation” option is much more desirable.