Some of us would have faced the issue that the failure of OAB update in version 2 and 3a due to various issues. Recently I have faced this issues and the resolution was simple when it got resolved, but till then it was really tuff.
Here are the couple events which are logged in the Application event viewer of generating server when the failure happens during the OAB update interval(ensure you enable the dignostic logging at least to medium for troubleshoting this issue).
I know we all were a little uncomfortable when Microsoft has come up with the new Message Tracking in Exchange Server 2007 and Exchange 2010 (of course even me). But, now I become very comfortable with it and mainly because of its flexibility/features. Recently the message tracking helped me in identifying a spam attack from an application server, which made me to write this post. Here I have tried to explain how to easily track and export the tracking results to a file and do the further filtration for troubleshooting purpose.
Note – I used the Exchange 2010 SP1 Exchange Management Console and Shell.
Open the Tool Box from EMC and locate Tracking Log Explorer, and do your normal tracking for a desired output. Here I did tracking for couple of test message that I sent.
Below shows the result window,
As you know that the Exchange 2007 and 2010 tracking give plenty of detail in the message tracking result. Now, how will you interpret these results? Is it easy to read the information shows in this output?
Now, what is this Soft-Deleted mailbox?
I feel that the name itself gives us an answer. When a mailbox is moved from one database to other, the original mailbox has not been deleted immediately after the successful move. The mailbox in the source database switched in to a soft-deleted state. In case if you need to restore any data from this mailbox, you can use the MailboxRestoreRequest cmdlet set. This soft-deleted mailbox retained until the retention period set on the source database for deleted mailboxes. You need to ensure that both the source mailbox server and the CAS server are in Exchange 2010 SP1 when performing the requests. We can use the cmdlet Get-MailboxStatistics against the database and look for the mailboxes in which the DisconnectReason property value to set to SoftDeleted.
I have seen questions like Installing Exchange 2010 Standard on SBS 2008 Standard and inplace upgrade of Exchane 2007 to Exchange 2010 in SBS 2008 etc on few forums. You will find the answer for why the inplace upgrade and the exchange 2010 installation can not be done on SBS 2008.
SBS 2008 comes with exchange 2007 and the exchange 2010 having a different schema structure, It will not allow you for an inplace uppgrade as well. See the operating system requirement for installing Exchange 2010 on the below article.
The exchange 2010 can be installed succesfully on 64-bit edition of Windows Server 2008 Standard or Enterprise with Service Pack 2 and 64-bit edition of Windows Server 2008 R2 Standard or Enterprise.
Hope you will not have confusion now.
There are few posts that I have seen related to the Exchange 2007 SP3 upgrade. Thought of sharing few information related to the schema upgrade part of Exchange 2007 SP3.
When you install Exchange 2007 SP3 it updates the Active Directory schema. The schema extension is basically to enable co-existence with Exchange 2010.
Before you install Exchange 2003 SP3, please verify few things mentioned below,
The machine on which you run the Exchange 2007 setup schema extension process must be:
Microsoft has found an issue with the Exchange 2010 Personal Archives support for Outlook 2007 in the December 2010 cumulative update for OL 2007, which may have resulted in not able to access the personal archive of Exchange 2010 mailbox.
There is a fix has been checked-in in the Feb 2011 Cumulative Update for Office 2007, which is expected in later this month. Please do necessary test in your test OL 2007 before rolling it out to organization wide.
On a day to day work, some or the other time you must have come across the situation where you want to extract the reports like the list of disabled users from Active directory, the list of Active mailbox users in your exchange server etc. Most of us will search for some automated tool to extract the reports. But you do not need any such scripts to extract these reports; the CSVDE command will help you in getting the report.
For e.g. you need the report of all enabled user accounts in your domain, use the below command.
Open command prompt and execute it(note – modify the command with your domain details).
CSVDE -r "(objectClass=user)" -d "dc=ExchangeDictionary,DC=com" -s ExchDicDC01.ExchangeDictionary.com -l displayname,useraccountcontrol -f c:\UserList.csv
-r :- this place we will give the filter, here I have given the objectClass=user, so the command will only run against the user objects.
-d :- scoping the command, here I have scoped to the entire domain(dc=ExchangeDictionary,DC=com means the domain ExchangeDictionary.com ). If you want to execute against one OU, you can still do it. Replace this with Ou=”your OU Name”, dc=ExchangeDictionary,DC=com
You must have heard, or may be faced this situation. I thought of sharing a bit of information to you all, may this help you in troubleshooting such issues. Exchange is designed to write all transaction into log files first and then commit to the database whenever system allows. Transaction can be anything, starting from accessing mailbox and moving messages between folders, email sending, receiving and so on. So the increase in transaction log is nothing but the activity performed against the exchange databases. Now let us see the reason for unusual growth in transaction logs, and this results in exchange database increase sometimes. The reasons can be one of the following.
SMTP issues: SMTP issue can be due to the following situation
Increased mail flow
Store issues: This can be due to the following.
Corrupt mail stuck in the queue.
3rd party software accessing a particular mailbox
Misbehaving client, it can be a corrupted profile also.
Multi mailbox search is one of the features introduced with Exchange 2010. This feature is very useful when you need to perform discovery searches for some required contents within Exchange mailboxes in your organization. For example, if your company adhere to legal searches you can make use of this feature. Also this can be used for Internal email verification, HR monitoring like searching for confidencial emails in set of user's mailboxes etc.
Multi-Mailbox search uses the content indexes created by the exchange search. You can give the ECP(Exchange Control Panel) feature as an easy to use interface for non-technical people to do the multi-mailbox search. Role Based Access Control (RBAC) provides a default 'Discovery Management' management role group to delegate the discovery tasks to users, thus ensuring only required permission are been given. This way the administrator can ensure that the user cannot perform any organization changes.