I stumbled across this gem last week and thought I’d share it with you. Using the tables listed here you can figure out what version of Exchange Server you are running. You can use the Get-ExchangeServer powershell command to find the Exchange 2010 and 2007 versions, but you will need to use the GUI in Exchange 2003. … [Read more...]
Object Not Found when moving mailboxes from Exchange 2003 to Exchange 2010
Recently when doing an SBS 2003 to SBS 2011 Standard migration, I had an error of “Object not found” in the Local Move Request screen as you can see below. I did some digging and found that the permissions on the SBS 2003 / Exchange 2003 mailbox store had been changed for some third party application. Too fix it do the following, Open Exchange System Manager on … [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...]
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...]