Working with a client on an Exchange 2003 to Exchange 2010 migration and had some issues with Outlook Anywhere working. I did some digging and resolve the issue as being something stupid I had done with the TMG 2010 rules. However along the way I found this particular error occurring at times and for a short while it lead me on a wild goose chase. I eventually … [Read more...]
Exchange 2010 Migration Tip – 403 – Forbidden: Access is denied
One of the things that is not well documented is that in Exchange 2010, if you are member of the inbuilt administrators group then you will NOT be able to use ActiveSync to access your mail. If you do you will get the following error message “An HTTP 403 forbidden response was received. The response appears to have come from IIS7” if you look closely you will see … [Read more...]
Cool ActiveSync Test Tool
I stumbled across this tool on my iPad on the Apple Apps Store. I used it to help diagnose why my iPad would not correctly sync with and Exchange 2010 server that I had deployed. The Microsoft tools said it was all working fine, but this tool helped me understand that there are in fact differences in the way the Apple iPhones/iPads perform ActiveSync vs the way that … [Read more...]
How can I move a user with large number of corrupt items in Exchange 2010?
More migration tips for Exchange 2003 to Exchange 2010 migrations. When moving a users mailbox from Exchange 2003 to Exchange 2010, I got the following error Large BadItemLimit (60) is specified. Please confirm your intention to accept a large amount of data loss by specifying AcceptLargeDataLoss. I reviewed the Exchange 2010 Move Request console in the Exchange 2010 … [Read more...]
Exchange 2010 Migration–Mailbox database is offline when moving users
Doing a migration for a client last week from Exchange 2003 to Exchange 2010 and when I went to move users mailboxes from Exchange 2003 to Exchange 2010, I got the message below “Mailbox Database… is offline”. It put me in a bit of a spin to start with but I eventually found it was referring to the Exchange 2003 server. The solution was to add the Exchange 2010 servers … [Read more...]