|
Exchange 2007 SP3 and Schema Upgrade |
 |
 |
|
Written by Praveen
|
|
Sunday, 20 February 2011 00:48 |
|
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
|
|
|
Exchange 2010 and SBS 2008 |
|
|
|
Written by Praveen
|
|
Tuesday, 22 February 2011 00:09 |
|
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
|
|
Exchange 2007/2010 Transport Rules using Message Header Values |
|
|
|
Written by Praveen
|
|
Tuesday, 17 January 2012 12:24 |
|
Mostly we create Exchange Transport Rules Condition using the criteria’s like “when FROM address ...”, When recipient ...” “When user from inside/outside organization” etc. Recently I have come across to create a rule for filtering the emails from internet groups, and the from address will always shown as the primary email address of the sender which could be always well known internet domains like gmail.com, yahoo.com etc, not the news group domain name. Most of the company wanted the email traffic from those public domains, by restricting the email traffic which are send to common groups (news group, community groups and other non-business groups).
Note – I have taken the group emailing as an example, this can be applied to various requirement where you can find some common criteria on the email header of such emails.
To work with such request in transport rule, you can use the condition “When the message header matches text patterns”. Before we create any rule, let’s look at the header of one such email and decide on the parameter which can be used for filtering such emails (common criteria for all such emails).
Look at the part of a header; I have selected the “Reply-To” field to create the condition for the transport rule. You can see that the from address will be always(mostly) the sender address, hence the filteration is not that easy using the common conditions, as that can cause stopping the entire email from the common public email domain.
|
|
Last Updated on Tuesday, 17 January 2012 12:50 |
|
|
Interestingly, Exchange 2010 SP2 later this year! |
|
|
|
Written by Praveen
|
|
Thursday, 28 April 2011 21:39 |
|
I know we still have been testing on SP1 and its possibilities and capabilities. You do not have to wait for long time, now get ready and read more about the new features that we can expect in the next version of Exchange 2010 Service Pack (SP2). There is a blog from Tony Redmond about few enhancements in Exchange 2010 SP2, expected to release by end of this year. There are three major changes/additions of features in new service pack, which are,
- Address Book Policies (ABPs), also known as “GAL segmentation”
- Hybrid co-existence
- Device overload
In the entire above features, I feel the Address Book Policies (ABP) will be used widely. ABP also like the other policies (OWA, Active Sync), now administrator can decide what object in the GAL can be viewed by a user. As like other policies it also have the default policy which will allow the user to see the GAL without any filtrations. Now with the GAL Segmentation, you can create department, Location GAL etc. If you would like to more on this area, see the exchange team blog written by Kevin(Exchange's General Manager).
|
|
Released: Update Rollup 6 for Exchange 2007 SP3 |
|
|
|
Written by Praveen
|
|
Sunday, 29 January 2012 10:39 |
|
Microsoft Exchange CXP team released Update Rollup 6 for Exchange Server 2007 SP3.
Go through the below MS KB(Knowledge Base) article for the complete reference to the issues fixes by installing this Update Rollup 6.
Imp Note - Disable the Forefront Protection for Exchange before you start the upgrade. If you fail to do that, the Information Store and Transport service will not start after the upgrade process.
Download your copy of the Update Rollup 6 for Exchange Server 2007 SP3 here
|
|
Last Updated on Sunday, 29 January 2012 11:12 |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 1 of 11 |
