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...]
Honey, Does my Exchange Database look big in this?
“… nothing a defrag wouldn’t fix…” Yes – maybe the title and the joke are not as good as it sounds, but the topic is a serious one. Weight loss for your Exchange Database. When was the last time you put your Exchange Database on a diet? When did you last run a defrag of it and get it to lose a few GB of space? Recently I was doing a migration for a client … [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...]
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...]