Organizations are taking a serious look at Microsoft exchange Server 2007, which sits on the Microsoft Unified Communications platform. Despite its enterprise e-mail, shared calendars, contacts and voicemail integration with e-mail, some administrators are reluctant to adopt the technology, for fear of a lengthy and expensive migration process. But migrating email and data doesn’t have to be such an arduous task. Read on for our tips about how to avoid the most common Exchange migration headaches.
Headache #1: Cost
IT directors can anticipate the following costs when planning an Exchange 2007 implementation: software licenses for Exchange 2007 and any third-party vendor tools; any new equipment to support the migrated platform, including servers, networking equipment and power appliances.
Licensing and equipment costs need not be prohibitive. Prior to launching a migration project, check your license agreements, as you may already own an independent software license for Microsoft Exchange Server 2007 or it may be a part of the Microsoft Enterprise Agreement your organization already has in place.
Even with Exchange 2007’s requirement for 64-bit servers, equipment costs may be less then you budgeted. You may be surprised to learn that most of your organization’s current e-mail environment is already running on 64-bit hardware and that you can reuse it if you are careful to select an appropriate migration approach. If you do find that you require new hardware, consider a scalable solution that will make the most of your investment, such as a blade system.
Headache #2: Lack of Time and Resources
When your team is already buried eyeball deep in current projects and responsibilities, the prospect of undertaking a migration project can seem overwhelming. Tasks that will require IT staff time include: assessing current infrastructure; creating the technical architecture plan; preparing a proof of concept or pilot project for testing purposes and evaluating the results; writing a plan for product deployment; provisioning users and settings; and executing the migration while ensuring user functionality. Each of these tasks is equally important and complicated. But with the right third party tool for your migration project, none are impossible. Talk with the support team for the tool you have chosen and map out a migration plan of attack.
Headache #3: Lack of Experience
It’s a good idea to send any staff members that will be handling the migration to training prior to the project. Microsoft holds a number of on-campus sessions throughout the year that are worthwhile.
If sending staff long distances to training sessions isn’t in your budget for this year, there is an alternative: Microsoft Official Curriculum (MOC) courses were designed to help your staff understand the platform. MOC offers courses, workshops, clinics and seminars at Microsoft IT Academies located in cities around the world. So find one that’s close to you, and it’s a cost effective way for your team to learn the fundamentals about the Exchange 2007 platform.
Headache #4: Business Continuity Options
Researching and selecting which business continuity or disaster recovery options to implement with Exchange 2007 can be difficult.
You should first ignore the technical requirements and capabilities for each method and instead focus on your organization’s functional requirements and recovery situations. Only after you’ve defined your company’s uptime and recovery conditions should you compare these to the options that Exchange Server 2007 offers.
Pay attention to monetary requirements as you work through this process — you may need to cut your requirements if they exceed your budget or ask for a funding increase.
Headache #5: Downtime and Missed Messages
One of the biggest worries when migrating a mail system is downtime and missed e-mails. Proper planning is important to ensure there is no major or unexpected interruptions when redirecting internet e-mail flow and migrating user mailboxes.
If your organization communicates with customers and partners on a regular basis, you may want to consider upgrading or replacing internet facing servers early in the migration process. Inserting one or more Exchange 2007 Hub Transport or Edge servers into your internet e-mail flow is easy to do and helps guarantee that internet mail will be routed to Exchange once the mailboxes are migrated. Depending on your environment, it’s a good idea to learn about external DNS configuration and the forwarding logic of your gateway provider prior to this step.
Headache #6: Establishing Coexistence
The duration of a migration project is wholly dependent upon the size of the organization — it can take anywhere from a few weeks to a year to complete. Users need to be able to message one another and schedule appointments at all times, even while some accounts are on Exchange Server 2007 and others are still residing on the source messaging environment. All employees should see the same global address list, migrated or not.
Everyone should be able to continue work in the shared workspace; changes made to public folders should be visible to any user, regardless of whether he/she is located on the source or the target system. The two messaging environments must coexist effectively.
Coexistence requires synchronization in three key areas: directory, public folder and calendar. The two systems need to be exact copies throughout the migration project. Synchronization should be two-way so that whenever end users update one environment, the change is replicated in the other.
Third-party vendor tools can help with this part of the migration. Look for a product that can synchronize all Active Directory and Exchange data, such as public folders, calendar information and mailbox information.
Headache #7: Migrating from non-Exchange Platforms
Not all organizations are running previous Exchange platforms – some are working with non-Microsoft messaging systems, such as Novell GroupWise orIBM Lotus Notes. Migrations from these platforms to Exchange 2007 are challenging, but not impossible.
Some of the major differences between Exchange and other messaging platforms that can pose a problem are:
Headache #1: Cost
IT directors can anticipate the following costs when planning an Exchange 2007 implementation: software licenses for Exchange 2007 and any third-party vendor tools; any new equipment to support the migrated platform, including servers, networking equipment and power appliances.
Licensing and equipment costs need not be prohibitive. Prior to launching a migration project, check your license agreements, as you may already own an independent software license for Microsoft Exchange Server 2007 or it may be a part of the Microsoft Enterprise Agreement your organization already has in place.
Even with Exchange 2007’s requirement for 64-bit servers, equipment costs may be less then you budgeted. You may be surprised to learn that most of your organization’s current e-mail environment is already running on 64-bit hardware and that you can reuse it if you are careful to select an appropriate migration approach. If you do find that you require new hardware, consider a scalable solution that will make the most of your investment, such as a blade system.
Headache #2: Lack of Time and Resources
When your team is already buried eyeball deep in current projects and responsibilities, the prospect of undertaking a migration project can seem overwhelming. Tasks that will require IT staff time include: assessing current infrastructure; creating the technical architecture plan; preparing a proof of concept or pilot project for testing purposes and evaluating the results; writing a plan for product deployment; provisioning users and settings; and executing the migration while ensuring user functionality. Each of these tasks is equally important and complicated. But with the right third party tool for your migration project, none are impossible. Talk with the support team for the tool you have chosen and map out a migration plan of attack.
Headache #3: Lack of Experience
It’s a good idea to send any staff members that will be handling the migration to training prior to the project. Microsoft holds a number of on-campus sessions throughout the year that are worthwhile.
If sending staff long distances to training sessions isn’t in your budget for this year, there is an alternative: Microsoft Official Curriculum (MOC) courses were designed to help your staff understand the platform. MOC offers courses, workshops, clinics and seminars at Microsoft IT Academies located in cities around the world. So find one that’s close to you, and it’s a cost effective way for your team to learn the fundamentals about the Exchange 2007 platform.
Headache #4: Business Continuity Options
Researching and selecting which business continuity or disaster recovery options to implement with Exchange 2007 can be difficult.
You should first ignore the technical requirements and capabilities for each method and instead focus on your organization’s functional requirements and recovery situations. Only after you’ve defined your company’s uptime and recovery conditions should you compare these to the options that Exchange Server 2007 offers.
Pay attention to monetary requirements as you work through this process — you may need to cut your requirements if they exceed your budget or ask for a funding increase.
Headache #5: Downtime and Missed Messages
One of the biggest worries when migrating a mail system is downtime and missed e-mails. Proper planning is important to ensure there is no major or unexpected interruptions when redirecting internet e-mail flow and migrating user mailboxes.
If your organization communicates with customers and partners on a regular basis, you may want to consider upgrading or replacing internet facing servers early in the migration process. Inserting one or more Exchange 2007 Hub Transport or Edge servers into your internet e-mail flow is easy to do and helps guarantee that internet mail will be routed to Exchange once the mailboxes are migrated. Depending on your environment, it’s a good idea to learn about external DNS configuration and the forwarding logic of your gateway provider prior to this step.
Headache #6: Establishing Coexistence
The duration of a migration project is wholly dependent upon the size of the organization — it can take anywhere from a few weeks to a year to complete. Users need to be able to message one another and schedule appointments at all times, even while some accounts are on Exchange Server 2007 and others are still residing on the source messaging environment. All employees should see the same global address list, migrated or not.
Everyone should be able to continue work in the shared workspace; changes made to public folders should be visible to any user, regardless of whether he/she is located on the source or the target system. The two messaging environments must coexist effectively.
Coexistence requires synchronization in three key areas: directory, public folder and calendar. The two systems need to be exact copies throughout the migration project. Synchronization should be two-way so that whenever end users update one environment, the change is replicated in the other.
Third-party vendor tools can help with this part of the migration. Look for a product that can synchronize all Active Directory and Exchange data, such as public folders, calendar information and mailbox information.
Headache #7: Migrating from non-Exchange Platforms
Not all organizations are running previous Exchange platforms – some are working with non-Microsoft messaging systems, such as Novell GroupWise orIBM Lotus Notes. Migrations from these platforms to Exchange 2007 are challenging, but not impossible.
Some of the major differences between Exchange and other messaging platforms that can pose a problem are:
- Exchange 2007 uses Active Directory for its user directory; other manufacturers implement their own directories. Maintaining contact information, settings and user profiles are major issues to be taken into account.
- The certificate and encryption services that guarantee communication between users and external contacts are applied differently in alternate messaging platforms.
- Group policies and security models for login and management are different.
There are many solutions in the market that manage migrations from non-Microsoft platforms to Exchange 2007. Companies such as Transend andQuest Software all offer migration products that work with multiple messaging systems. The most important thing to look for in a migration tool is coexistence for migrated and non-migrated users, and a product that guarantees no lost data or downtime. Additional handy features include the ability to automate processes, handle parallel migrations and move archives. Reducing costs and saving staff time are nice functionalities as well.
Headache #8: Storage and Regulatory Compliance
It is critical to evaluate your current environment. Growing organizations often don’t have the mailbox storage quotas or e-mail retention policies needed to maintain database performance. Prior to the migration, assess your current processor, memory and storage use. Talk to legal or human resources to minimize any legal risk and remain compliant with all applicable regulations if you find that mailbox sizes are out of control.
Archiving e-mail before migrating is the best way to reduce the overall volume of e-mail data that needs to be migrated, which can end up saving your organization time and money. Besides lessening storage requirements in the new environment, archiving before you migrate reduces the risk of losing messaging data.
Headache #9: Public Folders
Information stored in public folders will also need to be migrated to the new Exchange environment. The Exchange Server 2007 Service Pack 1 has a new graphical interface for public folder migration and management that helps you easily push the public folder hierarchy from one server to others in the organization.
Rather than migrate all public folders to Exchange 2007, some organizations have decided to move them to SharePoint. Look for a tool that offers automated migration (both individual or on a bulk basis), scheduled migration, content synchronization, permission mapping and multiple migration job handling.
Headache #10: Third-Party Product Integration
Many times through the course of this article, we have suggested using a third-party tool to assist your migration project – modern messaging systems are almost never deployed without one. Third-party integration usually includes one or more of the following: backup agents, antivirus software, message archiving and fax integration. Check with your vendors for versions of their software that support Exchange 2007, as well as guidance for migrating their software.
Test the new versions of software to guarantee that it has the same functionality and that it can run parallel with the old version. If the product has an Outlook component, confirm that it can run with your new version of Outlook.
Source:hdvoice.tmcnet.com
No comments:
Post a Comment