Transcript Migrating and Managing Exchange2007

Migrating & Managing Exchange 2007
John Hurley
Systems Engineer
Overview
• Overview of Exchange Migrator 7.0
– Challenges and Risks of Exchange 2007 Migration
– Introducing Exchange Migrator 7.0
• Architecture and Installation
– Hardware Requirements
– Software Requirements
– User Account Permissions
– Support Scenarios
– Installation
• Lab Walk-Thru
Migrating to Exchange 2007
•
Exchange migration (“transition”) is complicated due to
changes in Exchange 2007 architecture.
•
•
•
Administrative Groups
Routing Groups
Server Roles
1. Exchange 2007 does not support an in place upgrade. The upgrade
process involves deploying the new Exchange server 2007 and then
moving mailboxes and public folders over.
• As you move them over, you have to remove administrative groups
and configure routing group connectors for mail flow.
2. An Exchange 2007 organization cannot contain any Exchange 5.5
servers. The exchange organization must be in native mode
Manage: What tool to use to manage
mailboxes?
•
•
•
There is no longer any Exchange Management via Active Directory User
and Computer tool.
You have to use the Exchange Manager tools to manage the exchange side
and then go back to Active Directory Users and Computers to manage user
properties.
Helpdesk will now have to use three consoles to do their work.
–
–
–
•
Active Directory Users and Computers
Exchange Management Console
Exchange Management Shell
Our Exchange 5.5 dilemma is back!!!
Manage: What tool to use to manage
mailboxes?
• Not all exchange tasks are available via the gui.
• For example, something as easy as modifying exchange
mailbox permissions to give a manager read access to a
users mailbox is not available via the gui and is only
available via PowerShell.
5
Manage: What tool to use to manage
mailboxes?
• 32 bit version of the tools is now available from MSFT
• More then likely not as QE tested
• Requires Powershell, MMC 3.0, .net 2.0 which may
effect other application
• Granularity of delegation from the mailbox side has not
gotten much better from Exchange 200x days
6
Manage: Other management heartaches
•
Exchange 2003 mailbox management is done through the (ADUC)
Exchange 2007 mailbox management is done through the Exchange 2007
shell or the Exchange management console GUI. When you have coexistence, which tools to use on which objects? Here is a list of items to
remember:
– Exchange 2007 mailboxes must be managed with Exchange 2007 management
console or shell.
– Exchange 2007 mailboxes MUST NOT be managed with Exchange 2003 tools.
Note that this is not blocked, but mailboxes managed from Exchange 2003
ADUC will not be fully functional.
– Exchange 2003 mailboxes can be edited or removed with Exchange 2007 tools,
but cannot be created by Exchange 2007 tools.
– Exchange 2003 mailboxes can be managed with Exchange 2003 tools.
– Both Exchange 2003 and Exchange 2007 mailboxes can be moved (in either
direction) with the Exchange 2007 tools. Exchange 2003 move mailbox cannot
be used to move mailboxes to or from Exchange 2007 mailbox server.
Addressing Challenges and Risks
Moving to Exchange Server 2007
Transitioning to Exchange 2007
 New Exchange architecture
complicates the migration
process.
 Assuring uninterrupted service
levels of this critical IT service
can present complications.
 Native approach costly both in
terms of time and the level of
administrative effort required to
complete.
Announcing
Exchange Migrator 7.0
Administering Exchange 2007
 Administration requirement for
privileged accounts still introduces
unacceptable risk.
 New PowerShell interface
introduces steep new learning
curve for many administrators.
 Effective delegation of
administrative rights, combined
with activity audit, remains a
challenge.
Announcing Directory and
Resource Administrator 8.1
What is Exchange Migrator 7.0?
Pre-Migration
Planning
Performing the
Migration
Post-Migration
Processes
Simple, Project Based and Flexible Microsoft Exchange Migration
 Project Based:
 Define the scope of
the migration project
 Establish desired
migration options
 Synchronized GAL:
 Leverage Dirsync to
unify the GALs
between the source
and target
organizations
 Reporting:
 Migration status,
organization state and
conflict reports
 Look and Feel:
 Familiarity, Single
console/tool for all
supported scenarios
 Scenarios:
 Exchange 5.5 to
E2K/E2K3 intra-org or
inter-org
 E2K to
E2K/E2K3/E2K7 interorg
 E2K3 to E2K3/E2K7
inter-org
 Multi-Console Support:
 Support for multiple
consoles connected to
a single EMA
database
 EMProfileUpdate:
 Automate MAPI
profile updates for
migrated users
 Coexistence:
 Synchronize mail
objects throughout
the migration process
 EMCLI:
 Schedule repetitive
tasks such as
synchronizing
mailboxes and public
folders so they run
automatically on a
scheduled basis
What’s New for Exchange Migrator 7.0?
• Migration Scenarios: Support for Microsoft Exchange 2007
– Migrate from Exchange 2000 to Exchange 2000/2003/2007 Inter-Org
– Migrate from Exchange 2003 to Exchange 2003/2007 Inter-Org
•
•
•
No direct migration from E5.5 to Exchange 2007. Must migrate E5.5 to Exchange 2000/2003
Intra-Org or Inter-Org then migrate from Exchange 2000/2003 to Exchange 2007 Inter-Org.
Still supports E5.5 to Exchange 2000/2003 Intra-Org and Inter-Org
Does not support E5.5 to E5.5 migrations. Leverage EM 2.3 for this scenario.
• Support for Microsoft SQL Server 2005
• Migration Recovery
– Ensures migration can restart where it left of in case of connectivity issues
• Wizard Driven Directory Synchronization
– Can specify scope of Sync by Entire GAL, project or OU
•
•
•
•
Flexible Mail Flow Options
Synchronize Mailbox Message Deletes
Support for Outlook 2007 Clients
SidHistory Migration
Performance Enhancements
Time to
complete (hrs)
19:12:00
Reduces migration time: Approximate
migration time of 3.75 minutes per mailbox,
where average mailbox size is 500MB
16:48:00
14:24:00
12:00:00
9:36:00
7:12:00
4:48:00
2:24:00
0:00:00
300 mailboxes averaging
508MB per mailbox
100 mailboxes averaging
310MB per mailbox
Performance Testing Results
Architecture and Installation
Hardware Requirements
• CPU
– Intel Pentium II computer, 350MHz or higher.
• RAM
– 256MB minimum
• Hard Disk Space
– Allow enough disk space to accommodate the Exchange
Migrator log files and the Exchange Migrator database.
13
1
Software Requirements
• Operating System:
•
•
•
•
Windows 2000 Server SP2
Windows 2000 Professional SP2
Windows 2003 Server
Windows XP Pro
• Database:
• SQL Server 7.0
• SQL Server 2000
• MSDE 1.0 or later. MSDE 2000 SP3 is provided.
14
1
Software Requirements Cont.
• Mail client:
• Exchange Migrator requires Outlook 2000 or later and the collaborative
data objects file (CDO.dll). In Outlook 2000 the support for collaborative
data objects is an advanced setup feature. Ensure you configure
Outlook with the Corporate or Workgroup service option. Outlook
2003/2007 for 2007 target.
• Web browser:
• Internet Explorer 5.0 or later
• Exchange Tools:
• Install the Exchange tools for the version of Exchange installed on the
target server. It is recommended to use the latest Exchange SPs when
possible. If migrating from Exchange 5.5 install the 5.5 tools from the
installation cd for the target server version.
15
1
Exchange Migrator Configuration 1
Exchange Migrator is commonly installed into either of two
configurations. In the first configuration you install Exchange
Migrator on the target server.
16
1
Exchange Migrator Configuration 2
In the second configuration, you install Exchange Migrator on a
separate computer from the source or target servers.
17
1
Installation Configuration Notes
• Both installation configurations offer about the same performance when
the console is connected to the source and target servers through a
fast network connection.
• When migrating data over a WAN, you may install EM on the target
server to reduce migration time.
• It is commonly recommended to install Exchange Migrator on the target
Exchange server for best performance.
• Exchange Migrator supports multiple consoles connected to a single
EMA database.
18
1
Permission Requirements
Create the EM migration user account in the target domain and give the following permissions:
•
SOURCE ENVIRONMENT
− Admin rights in the source domain
− Local administrator of Exchange server machine
− Full Exchange administrator
•
TARGET ENVIRONMENT
− Admin rights in the target domain
− Local administrator of Exchange server machine
− Full Exchange administrator (Exchange Organization Administrator)
•
EM CONSOLE MACHINE
− Local administrator
•
NOTE: These are non-restrictive access rights guarranteed to provide for a successful migration. See the user guide
for EM 7.0 when available for possible revisions.
EX. Exchange Full Administrator permissions at the Administrative Group level on the E2K/E2K3 server, View Only
Administrator at the Org level, and the ability to create top level public folders. Ability to create objects in target OU.
Exchange 5.5 Permissions Admin permissions on the Exchange 5.5 source site and configuration containers.
Reference NetIQKB2202 for detailed information around software and configuration requirements.
•
•
2
Database Permissions and
Considerations
•
•
•
•
•
If you use SQL Server, the SQL Server implementation must be case-insensitive
and support SQL (Mixed-Mode) authentication.
If you use SQL Server, you need the system administrators server role to create and
access the EMA database.
If you do not have SQL Server installed on the computer where you initially install
Exchange Migrator, Exchange Migrator will install SQL 2005 Express.
When installing a remote console of Exchange Migrator that uses a remotely
installed Exchange Migrator database, no database software is required on the
Exchange Migrator console computer. To install a remote console, you must have
installed Exchange Migrator on another accessible computer along with a database
server and the Exchange Migrator database.
If you use Exchange Migrator to migrate Exchange servers from an environment
using a character set other than the Latin1-General character set, ensure your
database server is set to use the appropriate sort and collation settings for the
environment.
20
2
Supported Email Clients and their
Operating Systems
•
•
•
•
•
•
•
•
•
•
•
Microsoft Outlook 98
Microsoft Outlook 2000
Microsoft Outlook XP
Microsoft Outlook 2003
Microsoft Outlook 2007
Windows NT SP 6a
Windows 98
Windows 2000 Professional
Windows 2000 Server
Windows XP
Windows 2003
21
2
Supported Migration Scenarios
• Migrate from Exchange 5.5 to Exchange 2000/2003 Intra-site, IntraOrg and Inter-org
• Migrate from Exchange 2000 to Exchange 2000/2003/2007 InterOrg
• Migrate from an Exchange 2003 server to Exchange 2003/2007
Inter-Org
22
2
Installing a Purchased License
• By defaut Exchange Migrator installs with a trial license, which
operates for 30 days from the initial installation.
– With this license, you can migrate up to 50 mailboxes, however, you can migrate
an unlimited number of distribution lists, contacts and public folders.
• To install a purchased license:
1. Start Exchange Migrator.
2. Click Exchange Migrator in the left pane.
3. On the View menu, click License Information >Upgrade License.
4. Browse to the folder containing the license key file and select it.
5. Click OK.
23
2
Installing Exchange Migrator
24
2
Exchange Migrator Console
25
2
5
General Best Practices
• Check mail flow before migrating
–
Ensure Source and target environments are up and running and email can be
successfully sent and replied-to between source and target before conducting the
migration
• Perform test migrations
–
–
Ensure expected results are obtained before rolling out the production migration
Undo test migrations in order to retain full license count for the production migration
• Recommended Migration Order
–
–
–
–
–
Synchronize Directory Between Source and Target
Migrate Contacts
Migrate Distribution Lists
Migrate Public Folders
Migrate Mailboxes
–
http://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB865
Basic Troubleshooting Steps
• Ensure configuration requirements are in place
– What are the software and configuration requirements for Exchange Migrator?
– http://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB2202
• Understand what the issue is and identify exactly when it occurs
and if it is reproducible on demand
• Review EMApplog.txt for possible errors
• Determine if the issue is a known issue with a known fix
– Check product release notes
– Review top 10 KBs
– Search the knowledge base
• Enable extensive logging for further investigation
DRA support for Exchange 2007
•
•
•
•
•
•
•
Provides a single easy to use interface to manage Exchange mailboxes during
migrations andday to day management activities of exchange environments.
• Removes the need to learn a new command line language, (i.e., PowerShell) to
manageExchange Server 2007.
• Customer workflows are enhanced with the delegation and automation that the
products provide to our customers when managing exchange environments.
• Delivers powerful automation capabilities, such as the transfer of a user between OUs
or a change in role, assuring that the individual is assigned to the correct distribution lists
and/or mail server.
• Enforce corporate policies, such as SMTP addresses, placement of mailboxes into the
correct mail store.
• Extends and manages the Exchange environment by providing an advanced security
model that controls and audits changes to users mailboxes.
• Ensures changes to key mailboxes are restricted only to higher level administrators
thus reducing the risk of changes to those high profile mailboxes i.e. CEO, CFO etc..
Lab Walk-Thru