Articles

Articles (76)

I already have shared a script for migrating user mailbox into linked mailbox during the cross forest migration scenario in one of my previous posts, see here. Sometime(I faced all the time) during this process you would have observed that after the creation of linked mailboxes all manually configured limit, mailbox features are set back to the default. I have created two small of power shell command combination to import the features and the limits from a csv file. Set the limit, follow this Mandatorily, we need to extract the each mailbox limit details from exchange data before the linked mailbox conversion. This step is to get the existing values into a csv file, you may use the simple power shell command pated below to export the current data, Get-Mailbox  -ResultSize 3000 | select UserPrincipalName,IssueWarningQuota,ProhibitSendQuota,ProhibitSendReceiveQuota, MaxSendSize,MaxReceiveSize,RecipientLimits | Export-Csv C:\LimitDetails.csv The output file will be like, Remove the file line starts…
I know we are all talking about the new features of Exchange 2010 for a while now. Recently Microsoft has given a quick view about the exchange 2010 feature comparison with Exchange Server 2007 and Exchange Server 2003. The comparison have been split into three major feature categories, which are Protection and Compliance, Anywhere Access and Flexible and Reliable. Hope you all would be interested to have a look, see here. What's New in Exchange Server 2010? Comparing the features will really help us to take a decision on "whether to go for it or not"! -Praveen
In case of cross forest migration, most of us will plan the mailbox and account migration together to avoid complexity. However, there are situations where we plan to go one by one (all the user account migration first and then the mailbox migration). In my case, I chose to do the user account migration due to some dependency to the new forest and keep the User Mailboxes still in the source forest (existing forest). As you all know, we have to create linked mailboxes in this scenario and the process would be, Note – The source forest has Exchange 2007 Servers Org. Disabled the user account in source forest (Use ADUC) Disable the user mailbox(Disable-Mailbox cmdlet) Run the Clean-MailboxDatabase against the DB to quickly show the diconnected mailboxes in EMC Connect the mailbox as Linked Mailbox. Imagine you have many users to be migrated, definitely the activity going to eat…
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). ----------------------------------------------------------------------------------------------------- Event Type:        Warning Event Source:    MSExchangeSA Event Category:                OAL Generator Event ID:              9341 Date:                     7/6/2011 Time:                     4:28:07 PM User:                     N/A Computer:          OAB-HeloED Description: The parent Legacy Exchange DN container value '/O=ExhangeDictionary/OU=HeloED/cn=Recipients' was not found during generation of the differential update file for offline address list '\Global Address List'.  This will force clients using this offline address list to do a full download of the offline address…
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…
We all are well aware about the mailbox movement tasks in different versions of exchange. When compared to the previous versions of Exchange, Exchange 2010 SP1 gives you more featured mailbox MoveRequest cmdlet. @ A Glance changes in Exchange 2010 SP1, Soft delete the mailbox in the source mailbox in the source database. MoveRequest cmdlet has been updated to support moving archives to separate database. 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. …
I understand that there are so many companies still using the exchange 2003 as their messaging solution and are in process of migration to Exchange 2007 or 2010. There could be chances of rebuilding the servers on various reasons and will have to re-do the OWA URL redirection and other respective tasks. Recently I also had encountered to do the same for one of my Exchange 2003 organizations and thought of sharing you the technical details, because it took me some time to figure out various ways out to do the settings.  I have mentioned 2 sections here; one is to redirect the https://mail.exchangedictionary.com request to https://mail.exchangedictionary.com/exchange. Second section will guide you to configure the HTTP traffic redirection to HTTPS.Simplify the OWA URL: The steps below will help you to redirect the HTTPS request that is sent to the root of the Web server to the Exchange virtual directory. Open…
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. Exchange 2010 Installation Guide 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. -Praveen  
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: Windows Server 2003 SP2 with Windows Installer 4.5 installed Windows Server 2008 with Windows Installer 4.5 installed Windows Server 2008 SP2
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. Ref - http://msexchangeteam.com/archive/2011/02/01/457903.aspx -Praveen
Page 5 of 6
theme by reviewshub