Microsoft ended its support for Exchange Server 2003 in
April 2014, making many organizations to think about migrating to a supported
version.
It is possible to directly migrate from Exchange 2003 to
Exchange 2010 if you are looking for a legitimately simple migration. The
process is pretty alike to that of migrating from Exchange 2003 to Exchange
2007. This comprises having servers with the similar names and roles in
Exchange 2007 and Exchange 2010, but there are some insignificant differences.
Microsoft has given details about the particulars of what the migration process
involves in this TechNet entry.
If your organization has decided to migrate to Exchange
2010, here is what you need to know about Exchange2010. We will look at some of
the features and abilities your organization can anticipate after a migration
as well as ways to ensure a trouble-free migration.
Features bring
Exchange 2010 to the next level
If you are planning to migrate to Exchange Server 2010, your
organization can plan to use these five service offerings - Client access
connectivity, High availability and disaster recovery, New scalability and
performance enhancements, Protection and compliance and Integration with
Microsoft Office 2010. These offerings will give you options to improve a
number of your organization's competences, comprising performance, scalability and
disaster recovery.
Unified Messaging
receives a boost
Although Unified messaging was accessible in Exchange 2007,
Microsoft enhanced it in Exchange 2010. Organizations that need to implement Unified
messaging can take benefit of abilities such as voice message transcription and
directions for answering calls.
Exchange 2010
includes enhancements to high availability
One of the main enhancements in MS Exchange 2010 is how the
server can handle high availability. One specific feature as well as cluster
size modifications can make high availability an achievable goal for
organizations.
Forefront Protection
for Exchange 2010 deserves your attention
Microsoft incorporated upgrades in this version of Forefront
Protection as well as features that provide your organization choices in how it
keeps Exchange protected. Forefront Protection 2010 for Exchange Server is the
current generation and next advancement of antivirus and anti-spam protection.
OWA gets a new name
and additional features
If you are planning to migrate to Exchange 2010, you will
have to supplement some words to your OWA dictionary. Outlook Web Access turns
into the Outlook Web App, and the Options section of OWA has been converted into
Exchange Control Panel.
Clustering gets a change
One major amendment in Exchange 2010 is that the clustered
mailbox server has been eliminated. Admins now have to make a database
availability group as an alternative, which enables more flexibility as you form
site resiliency and high availability.
Multi-mailbox
searches and legal hold features are added
Exchange 2010 provides organizations the ability to integrate
two features: legal holds and multi-mailbox searches. But before employing
either feature, you should know which command lines you need to use and which
end users’ needs to be added
Considerations to
make before you migrate to Exchange 2010
Before migrating from Exchange 2003 to Exchange 2010, you
should understand the differences among the two Exchange Server versions so
that migration can take place successfully. Modifications to recovery,
archiving and storage are specifically significant to know.
Important parts to
remember about an Exchange 2010 migration
Planning for an Exchange 2010 migration can leave
organizations so busy that they forget to recognize these four vital parts of
the migration –
- Make sure all third-party products are compatible with Exchange 2010.
- Plan for coexistence
- Don’t forget about split DNS
- Be careful when repurposing old hardware
Are you now
officially migrating from Exchange 2003 to Exchange 2010 – Now what? Have you decided which method will you use to
migrate to Exchange 2010? If not, then read below to check the two methods to
carry out the migration process:
Method 1 :
Using Exmerge and Powershell Scripts : Use Exmerge, an inbuilt utility in
Exchange 2003 to Extract PST from Exchange 2003 and import the Extracted PST
into Exchange 2010 using powershell cmdlet New-MailboxImportRequest. If you
face any problem while using Exmerge and cmdlet and if the migration process
stops in between, then what will you do? In that case, follow the Method 2
given below:
Method 2: If
you are unable to migrate from Exchange 2003 to Exchange 2010, then a better
option would be to make use of any third party tool like Stellar Mailbox
Extractor for Exchange Server. This tool will directly import your offline EDB
of Exchange 2003 into Live Mailbox of Exchange 2010. Migration through this
tool can save you a lot of time and efforts.
0 comments:
Post a Comment