Microsoft Exchange 2010 Upgrade Seminar March 2010


Published on

Very detailed how-to for upgrading to Microsoft Exchange 2010

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Microsoft Exchange 2010 Upgrade Seminar March 2010

  1. 1. Exchange 2010 Upgrade Rich Platt Sr IT Architect March 10, 2010
  2. 2. Agenda • Requirements • New Features • Routing & Topology • Installation • Coexistence and Migration • Wrap-up
  3. 3. Microsoft Exchange Roadmap • • Optimize for Software + Services Deliver e-mail archiving solution 2009 • Better protect communications • Manage inbox overload • Microsoft hosted enterprise messaging solution • Centralized, Web-based configuration and admin 2008 • Financially backed service level agreements SP1 • Public Folder access in Outlook Web Access • Standby Continuous Replication (SCR) 2007 • Additional Exchange ActiveSync Policies • Unified Messaging and more efficient collaboration • Outlook experience from desktop to mobile 2006 • Performance and scalability optimization
  4. 4. Exchange 2010 Hardware Requirements • Production environment – Intel Xeon Pentium 4 64-bit processor – AMD Opteron 64-bit processor • Minimum 4GB of RAM per server – Several GBs more likely • 1.2 GB disk space on installation drive – 200 MB on system drive
  5. 5. Exchange 2010 Server Requirements • Microsoft Windows Server 2008 SP2 • Microsoft Windows Server 2008 R2 supported • Microsoft .NET Framework 3.5 SP1 • Windows Remote management 2.0 • Windows Power Shell v 2.0 • 2007 Office System Converter: Microsoft Filter Pack (Mbx role only) • NTFS File Systems throughout – system, binaries, logs, databases, other Exchange Server 2007 files
  6. 6. Exchange 2010 Hardware Virtualization • Windows Server 2008 with Hyper-V technology • Windows Server 2008 R2 with Hyper-V technology • Microsoft Hyper-V Server 2008 • Microsoft Hyper-V Server 2008 R2 • VMware vSphere 4.0
  7. 7. Exchange 2010 Virtualization Guest Machine • Is running Microsoft Exchange 2010. • Is deployed on the Windows Server 2008 with SP2 or Windows Server 2008 R2 operating system. • Doesn't have the Unified Messaging server role installed. • Virtual disks must be fixed, dynamically expanding disks are not supported • Using Database Availability Groups with hyper-visor based clustering, migration or virtualization high availability is not supported. • Making snapshots of Exchange 2010 virtual guests is not supported • Virtual processors used by all guest machines on a host should follow a 2:1 virtual CPU ratio (2 virtual CPUs per 1 logical core)
  8. 8. Processor Configuration Table Role Minimum Recommended Maximum Recommended Edge Transport 1 x Processor Core 2 x Processor Cores 4 x Processor Cores Hub Transport 1 x Processor Core 4 x Processor Cores 8 x Processor Cores Client Access Server 1 x Processor Core 4 x Processor Cores 4 x Processor Cores (CAS) Unified Messaging 1 x Processor Core 4 x Processor Cores 4 x Processor Cores Server (UM) Mailbox Server 1 x Processor Core 4 x Processor Cores 8 x Processor Cores Multi Role (Hub, CAS, 1 x Processor Core 4 x Processor Cores 4 x Processor Cores UM, Mailbox)
  9. 9. Memory Configuration Role Minimum Recommended Maximum Recommended Edge Transport 2GB/Server 1GB/Core (2GB 16GB/Server minimum) Hub Transport 2GB/Server 1GB/Core (2GB 16GB/Server minimum) Client Access Server 2GB/Server 1GB/Core (2GB 8GB/Server (CAS) minimum) Unified Messaging 2GB/Server 1GB/Core (2GB 4GB/Server Server (UM) minimum) Mailbox Server 2GB/Server 2GB + 5MB/mailbox: 32GB/Server Variable based on user profile Multi Role (Hub, CAS, 2GB/Server 4GB +2MB to 8GB/Server UM, Mailbox) 5MB/Mailbox: Variable based on user profile
  10. 10. Operational Efficiency Optimized for performance and scalability • EDB Database rewritten, sequential data writes and reads • Provides an additional 70% I/O improvement over Exchange 2007 • Can use Type II SATA drives, up to 300 I/Os per drive • Supports 10GB production mailbox and 100GBs archive mailboxes • Standard Edition – Provides 5 Datastores per server • Enterprise Edition – Provides 150 Datastores per server
  11. 11. Exchange 2003 – HIGH IOPS Storage bound by high IOPS • Small, fast, expensive drives • Poor disk space utilization • SAN required for high availability Storage Area Network
  12. 12. Now: Larger Capacity & Fewer Spindles • Requires less drives to support current user load • More users per spindle • Can use Type II SATA or SCSI drives SCSI / SATA Drives
  13. 13. Deployment Flexibility Greater Range of Storage Options Through Performance Enhancements Storage Area Direct Attached Direct Attached JBOD SATA Network (SAN) w/ SAS Disks w/ SATA Disks (RAID-less) • 70% reduction in IOPS • Smoother IO patterns E2K3 • Resilience against corruption E2K7 E2010 Read IOPS Write IOPS
  14. 14. New Features
  15. 15. Enabling New Functionality • Database Availability Groups – Up to 16 mailbox replicas – Each mbx datastore have different replication settings and different retention policies • Compliance – Keep more mail in the datastore • No PST, archive for long term on the server – Search across multiple mailboxes and archives
  16. 16. Exchange Management Console 1. Tree Segmented into 4 work centers (Recipients, Servers, System, Toolbox) 2. Result Pane Rich list of objects 3. Work Pane Child objects of result pane object, only used by Servers & System nodes 4. Action Pane Tasks for selected object(s) and node (work center)
  17. 17. Exchange Server 2010 Roles Exchange Exchange Edge Transport Perimeter Intranet Windows Server Windows Server Exchange Role Exchange Roles Client Hub Access Transport Edge Transport Unified Mailbox Messaging
  18. 18. Mailbox Server Role • Traditional Role – Hosts mailboxes and PFs (if present) • Can communicate with multiple hubs – But not in other sites, only in same site • Traditional Cluster no longer needed, uses DAG • MAPI access is provided by Client Access Server
  19. 19. Unified Messaging Server Role • Messaging Services (Voice and fax) – Outlook Voice Access • E-mail, voice mail, calendar, contacts – Call Answering • Outlook • Outlook Web Access – Automated Attendant
  20. 20. Client Access Server Role • Provides client access for – Outlook Web Access, POP3, IMAP4, RPC/HTTP, ActiveSync, MAPI – Proxies or redirect connections to other Client Access servers • Proxy to Mailbox co-located preferred to ‗random‘ selection • Provides Auto Connect functionality for Microsoft Office Outlook 2007 • Provide OAB – Provide access to SharePoint sites and file for Microsoft Outlook Web Access (OWA) and Active Sync connections – Performs re-direct and proxy functions to other Client Access Servers • Locate at least two Client Access Servers in each site that contains Mailbox Servers
  21. 21. Client Access and Mixed Exchange • Client Access Server – Maintains legacy access Exchange Server 2003 Back End server • Legacy OWA user experience • You cannot use an Exchange Server 2003 Front End server to connect to an Exchange Server 2010 Mailbox Server
  22. 22. Outlook Web App (OWA) • OWA premium for IE, • Side by side calendar Firefox, and Safari view • Conversation view • Message tracking • Ignore/Move • SMS Sync conversation • Favorites folders • Virtual list view • Advanced search • Presence • Archiving • Instant messaging • Distribution group • Nickname cache creation • UM card • IRM • Calendar sharing • Delegate access
  23. 23. Hub Transport Role • Processes message for delivery across the organization • Routing predictability • Application of policies • Ensure Hub Transport Role in every site that has Mailbox Servers – Even when two users on the same database exchange e-mail, Hub Server is engaged • Connectivity to Exchange Server 2003 via Connectors
  24. 24. Hub Transport Improvement • MailTips • Shadow Redundancy • End-User End-to-End Message Tracking • Transport Rules integrate with AD RMS • Provides the ability to measure end-to-end latency
  25. 25. Edge Transport Role • Edge Transport Role must be on dedicated server – All other roles may be co-located – May be co-located with ISA Server function • Edge Transport (always connects to Hub) – Use standalone server (can be on domain-joined server) – Not generally connected to AD Forest – Wizard config for Edge/Hub connection (EdgeSync) – Requires AD Application Mode (ADAM) • ADAM installed during Edge Server install – Used for storage of recipient/configuration info • Org data and ADAM data in synch via EdgeSync • Hashed recipient lists, routing info
  26. 26. Edge Transport Functions • Executes Message Hygiene Agents • Address Rewrite agent (example below) – Enable-TransportAgent -Identity "Address Rewriting Inbound agent" – New-AddressRewriteEntry -Name "Swap" - InternalAddress ―richp@xyz.local" -ExternalAddress ―" • Connection Filter agent • Recipient Filter agent • Sender Filter agent • Sender ID agent • Content Filter agent • Protocol Analysis agent
  27. 27. Topology • Exchange Server 2010 topology is based on AD sites – Many organizations can rely on default – Especially if existing RG design based on AD sites – May use AD Sites to regulate access to DCs/GCs – Exchange routing table is subset of site topology • Note that all mail routing is Direct Relay – Direct Relay is Hub-to-Hub – Inter-site relay uses SMTP – Intra-site relay uses MAPI • Therefore, every site with Mailbox servers – Requires at least one Hub Server role • Co-located Hub servers have higher precedence – No i/b optimization of Hub selection (co-located scenario)
  28. 28. Exchange Enterprise Topology Enterprise Network Phone system (PBX or VOIP) Edge Transport Hub Transport Routing & AV/AS Routing & Policy External SMTP servers Mailbox Unified Messaging Storage of Voice mail & Mobile mailbox items voice access phone Client Access Web Client connectivity browser Web services Outlook Line of business (remote user) application Outlook (local user)
  29. 29. Continuous Availability Simplified Mailbox High Availability and Disaster Recovery with New Unified Platform San Jose New York Mailbox Mailbox Mailbox Server Server Server DB1 DB1 DB1 Replicate databases Recover DB2 DB2 DB2 to remote datacenter quickly from DB3 DB3 DB3 disk and DB4 DB4 DB4 database DB5 DB5 DB5 failures • Evolution of Continuous Replication technology • Easier than traditional clustering to deploy and manage • Allows each database to have 16 replicated copies • Provides full redundancy of Exchange roles on as few as two servers • Capabilities of CCR and SCR combined into one platform
  30. 30. Continuous Availability Limit User Disruption During Mailbox Moves and Maintenance E-Mail Client Users remain online while their mailboxes are moved between servers  Sending messages  Receiving messages Client Access Server  Accessing entire mailbox Administrators can perform migration and maintenance during regular hours Mailbox Server 1 Mailbox Server 2
  31. 31. Exchange 2010 Management • New Exchange Management Console features • Exchange Control Panel (ECP) − New and simplified web based management console − Targeted for end users, hosted tenants, and specialists • Role Based Access Control (RBAC) − New authorization model − Easy to delegate and customize − All Exchange management clients (EMS, EMC, ECP) use RBAC • Remote PowerShell − Manage Exchange remotely using PowerShell v2.0 − Note: No more local PowerShell, it's all remote in Exchange 2010
  32. 32. Installation
  33. 33. Installation Prerequisites • Windows Server Active Directory Forest – Schema Master DC must have Windows 2003 SP1 – GC servers running Windows 2003 or higher – AD Domain Functional Level Windows 2003 Server-native or higher in all domains – A GC in the domain into which you are installing • Forest Functional Level Windows Server 2003 or higher • No Exchange 5.5 servers in the organization (if migrating) • No Exchange 2000 Servers in the organization • Co-existing with Exchange 2003, you‘ll need the /PrepareLegacyExchangePermissions switch – Gives Exchange 2003 Recipient Update Services (RUSes) permissions to write to the Exchange Information and Personal Information property sets • Forest Preparation using SETUP/PrepareAD – Occurs automatically during normal SETUP
  34. 34. Permissions • Install using account that is member of: • Local Administrator on the server • AD Enterprise Administrator • AD Domain Administrator • Exchange Permissions • Admin on Exchange Organization object
  35. 35. Unattended Installation • Setup.exe /console • /roles:<roles to install> – ClientAccess (CA, C);TansportHub(TH, T); Mailbox (MB, M); UnifiedMessaging (UM, U) • /mode:<setup mode> – Install, Upgrade, Uninstall, RecoverServer • /targetdir:<folder> • /DomainController • /prepareAD • /prepareSchema • /prepareLegacyExchangePermissions
  36. 36. Validating Exchange Server 2010 Installation • After installing Exchange Server 2010 • Run get-ExchangeServer from PowerShell • Displays all installed server roles • Check Event Viewer for • Events 1003 and 1004 in application log • Run ExBPA • Check Help Files for additional tasks
  37. 37. Deploy Supporting AD Infrastructure • Upgrade/replace existing DCs and GCs where necessary • Recommend deploying Windows 2008 x64 for AD • Use 64-bit hardware (recommended) – Orgs with more than 20,000 objects will benefit – Also orgs with DIT >3 GB will benefit from increased address space (assuming sufficient physical memory) • Consolidation hand-in-hand with 64-bit • One 64-bit GC (dual CPU, 14 GB memory) can handle the workload of 11 32-bit GCs to support 20,000 Exchange Server mailboxes • 11GB DIT: 350,000 objects • Database caching occurs during normal e-mail activity – no prior loading
  38. 38. Order of installation 1. Install Client Access Server Role 2. Install HUB Transport Server Role 3. Install Exchange Mailbox Server Role
  39. 39. Routing & Topologies
  40. 40. Active Directory Sites Are Routing and Service Discovery Boundary • Automatic discovery for all Exchange services within an Active Directory site • AD Topology Service • Mailbox Submission • Hub Transport • Client Access • Routing decisions based upon AD site topology
  41. 41. Edge Transport • Transport Role which resides in perimeter network • Not AD-joined—will use ADAM / AD LDS • EdgeSync Service replicates subset of recipient information via one- way push and maintains send/receive connectors with Hub Transport – Subscription based replication – Hashed version of organization recipients – Safe Sender List aggregation • Port 25 is only inbound port/connection
  42. 42. Coexistence Routing • Exchange 2010 Routing Engine – Understands cost calculation for Exchange 2010 (AD Site Links) and legacy versions (RGC Costs) – Attempts to keep messages routed across versions in Exchange 2010 Routing Group as long as possible and will choose to exit the routing group at a legacy server which has lowest legacy path cost possible – Optimizes path within the Exchange 2010 routing group based upon AD Site Topology • Legacy Exchange 2003 will see all Exchange 2010 servers as a single routing group—no cost associated with traversing the Exchange 2010 routing group from a legacy perspective • Requires RGC between legacy Exchange 2003 and Exchange 2010
  43. 43. Things to Keep in Mind • Exchange 2003 connector restrictions are not honored • Exchange Server 2010 transport only provides SMTP protocol • Must have RGC connectors in a legacy Exchange 2003 environment • Must have IP-based Site Links in AD • Choose an approach that will reduce duration of transition • Determine Public Folder requirements
  44. 44. Public Folders and Routing • Exchange 2010 Servers ignore Exchange 2003 RGCs— rely upon AD Site topology for referrals
  45. 45. Coexistence and Migration
  46. 46. Getting there from here • Determine business benefit of Exchange 2010 – Whistles and bells aren‘t (normally) enough • Select appropriate hardware – Processor – Memory – Storage • Plan storage – Understand requirements for DAGs, transport logs, etc. – Leverage reduced IOPS • Understand the server roles
  47. 47. In-place • In-place upgrade? – None – Database changes in Exchange 2010 even between Exchange 2007 and Exchange 2010 – 64-bit architecture change – 4k pages (2003) to 8k pages (2007) to 32k pages (2010) – No streaming store as was in Exchange 2003 x64 x86
  48. 48. Existing Org (2003 or 2007) • Installed Exchange 2010 in existing organization – Transport • RGCs created at time of install (or later) • Internet entry/exit points decided – Directory • Nothing (much), same organization – Free/Busy • PFs can be hosted on Exchange 2010 • Microsoft Office Outlook 2007 uses CAS role for availability • Outlook 2007 posts to PF server for prior Outlook versions – Migration • Use console (EMC) or PowerShell (EMS)
  49. 49. Coexistence with Exchange Server 5.5 • No coexistence with Exchange Server 5.5 • Complete upgrades to Exchange Server 2003 (recommend latest SPs) • All Exchange Server 5.5 servers must be decommissioned • Exchange org must be in Native Mode • Exchange Server 5.5 migrations only possible via Inter- Organizational migrations
  50. 50. Coexistence with Exchange Server 2000 • No coexistence with Exchange Server 2000 • Complete upgrades to Exchange Server 2003 (recommend latest SPs)
  51. 51. Installing Exchange Server 2010 into Existing Exchange 2003 Organization • Legacy organization auto detected during installation • Little integration at the management level – Exchange Server 2010 ESM v. Exchange Server 2003 ESM – AG: Exchange Administrative Group <random ID> – RG: Exchange Routing Group <random ID> • Legacy mailboxes are displayed in Exchange Server 2010 ESM
  52. 52. Migrating from Exchange 2007 • Exchange 2007 must have SP2 installed • First install Exchange 2010 CAS server role • Second install Exchange 2010 HUB Transports server role • Finally install Exchange 2010 MBX server role • Use Exchange 2010 Tools for migrating from E2007 to E2010 • Users do not need to log off
  53. 53. Intra-Org Migration Process Move mailboxes • Intra-org migration and PFs to Exchange 2010 • Introduce Exchange Exchange 2003 Organization 2010 servers into existing Exchange 200x Org Create RGC • Ensure RGC created for Exchange 2003 • Ensure message flow between Exchange 2007 & Exchange 2010 HUB • Move mailbox CAS MBX/PF Introduce Exchange 2010 Servers
  54. 54. Migrating Users • Options – Move Mailbox Wizard – Move-Mailbox command • Move-mailbox <alias> -TargetDatabase <name> – Example • Move-mailbox carrie -targetdatabase "Mailbox database" – Restrictions • Cannot use E2003 Move Mailbox Wizard to move mailboxes from Exchange Server 2010 to Exchange Server 2003 servers • Cannot use Exchange Server 2003 Move Mailbox Wizard to move mailboxes from Exchange Server 2003 to Exchange Server 2010 servers
  55. 55. Move Mailbox Preparation • Required permissions – Exchange Recipient Administrator – Exchange Server Administrator – Member of Local Administrators group • For source and target server • Transaction logs • Single instance storage • User mailbox cleanup
  56. 56. • Event Viewer • 1006 • 9354 • 1007 • Migration Logs
  57. 57. Typical transfer rates using Microsoft Move Mailbox Wizard • Typical 2GB to 4 GB per parallel migration transfer rate per hour. • Default is 4 Parallel Migrations per move mailbox, can be configured for up to 32 Parallel migrations per mailbox move
  58. 58. What Impacts Your Rate of Migration? • Source hardware: The bus architecture of source legacy servers may reduce the data transfer rate • Migration software: The typical data transfer rate using migration software (Move Mailbox Wizard) does not typically exceed 2-4 GB/hour data transfer rate • Backup requirements (need to backup source for contingency plans) • Scheduled and unscheduled maintenance periods • User disruption tolerance • Blackout periods/holidays/vacations • Hierarchical indecision • Surprises
  59. 59. What About Delegate Access? • It works regardless of the location of the user mailbox • It works regardless of where it was configured – ―Send As/Receive As‖ on Security tab in ADUC – ―Full Mailbox‖ access rights on Exchange Advanced tab – ―Send on behalf of‖ in Exchange General, Delivery Options – Delegation configuration in client • Depending on the client, F/B information will come from different location • Moving forward, use Exchange 2007 management tools to configure administrative delegation
  60. 60. What about Exchange 2003 ―Resource Accounts‖? • Migrate over as ―shared‖ accounts – And continue to work as expected • ―Auto-accept‖ remains enabled – Exchange 2003 and Exchange 2010 mailboxes can schedule against it • Consider using Exchange 2010 resource account feature – Room – Equipment
  61. 61. • Auto-Accept settings retained and operational • For bulk conversions use: Get-Mailbox <filter> | Set-Mailbox –type:Equipment/Room • Does not disable AD Account set-mailbox -identity “Georgia" -type:Room
  62. 62. Query Based Distribution groups (now DDGs in Exchange 2010) Upgrade with cmdlet in EMS Set-AddressList with –ForceUpgrade:$True Non-Universal Distribution Groups (Global) Can manage properties in Exchange 2010 but should be converted Conversion via Management Console or Management Shell Set-Group -IsUniversalGroup:$true Can only create Universal Distribution Groups in Exchange 2010 Expansion Server should be Exchange 2010 Hub Transport
  63. 63. • Identify all recipients with this issue via LDAP query: (&(objectclass=*)(mailnickname=* *))
  64. 64. • Display Name has leading or trailing whitespace – Trim the invalid whitespace from the displayname with a cmdlet Get-Mailbox | Foreach { Set-Mailbox $_ –DisplayName $_.DisplayName.Trim() }
  65. 65. Public Folders • No requirement to have a public folder store in a native Exchange 2010 – …Assuming all clients are Outlook 2007 • PF features that have been removed – NNTP access – IMAP4 PF access – Non-MAPI TLHs
  66. 66. Client Experience: OWA • Legacy OWA • Clients will see the OWA version of their mailbox store • Exchange 2010 OWA experience • Requires Exchange 2010 CAS and Exchange 2010 Mailbox server
  67. 67. Client Experience: Free/Busy • Outlook 2007 users query Autodiscover service to obtain URL for the Availability service – Availability service retrieves free/busy information directly from the calendar in Exchange 2010 – Availability service queries public folder data for legacy user free/busy data • Legacy Outlook as well as Outlook 2007 clients running on Exchange 2003 mailboxes will use PFs for the F/B information
  68. 68. • Storage Limits can keep you from migrating Move-Mailbox –MailboxSizeLimitOptions PreserveSource • Hidden accounts stay hidden • Accessing shared calendars works regardless of where mailbox resides • Consider impact to applications that use current property sets • Migration transparent to end user • Increase number of move-mailbox threads • Max of 30, default is 4, EMC uses 4 Move-Mailbox –MaxThreads 6
  69. 69. • Deleted Items not moved during move-mailbox • Cannot have space in alias for address list conversion • Active sync policy is automatically applied when you migrate the user
  70. 70. Third-Party Tools TrendMicro, McAfee, Symantec, GFI, Kasperski, Sophos, Antivirus F-Secure Secure Messaging nCipher, RSA, Check Point FAX Gateway Fenestrae, GFI, Captaris, BNS Group Mobility Middleware RIM, Good Technology Migration: Public folder data to Quest, Tzunami Sharepoint Migration: Exchange Version(x) Quest to Exchange 2007 NetApp, Hitachi, CommVault, Symantec, DoubleTake, Storage: Backup, Disaster Computer Associates, UltraBack, F5, Teneros, Azaleos, Recovery, H/A Cemaphore, Xiotech, Mimosa, HP Data Protector CommVault, EMC, Symantec, Hummingbird, Mobius, Compliance: Archiving Overtone, Atempo, AXS-One, HP RISS Compliance: Content Filtering IXOS, Zantaz, Meridio Management Quest, NetIQ, Computer Accosiates, HP Newsgator (RSS), nCipher (User Provisioning), K2 Line of Business Applications (Workflow)
  71. 71. Decommissioning Legacy Exchange • Move/remove all mailboxes • Upgrade address lists and OABs • Move public folder tree to the Exchange 2010 admin group • Move/remove connectors • De-install all Exchange 2003 servers • Delete empty containers (RG, PF) • Remove the Exchange 2003 Admin tools • Schedule update of address list and address list policies for once a day
  72. 72. Removing the Last PF Store • Must be an Exchange Organization Administrator as well as member of Local Administrators group on Mailbox server • Ensure there are no legacy Exchange servers in the organization • Ensure you do not require replication of F/B to legacy clients (Only Outlook 2007 clients) • Ensure you no longer need PF‘s for organizational forms or the use of public folders for collaboration • Verify you have no OABs configured for PF distribution
  73. 73. Upgrading Final Thoughts • Intra-org migration is straightforward – Still requires planning and testing • PowerShell is your friend – Bulk operations are a snap – You will learn to love it • Don‘t forget to check out scripts folder! • Move-mailbox works inter-org too! – Inter-org migrations need more planning – Do you need third-party migration tools? – Don‘t forget the Big Four • Especially DLs, delegates, reply-ability, etc.
  74. 74. Best Practices • Determine why you are moving to Exchange 2010 – What problems are you solving • Think through server and storage configuration • Manage like with like – Exchange 2003 objects with ESM – Exchange 2007/2010 objects with EMC/EMS • Encourage clean-up prior to migration • Prepare effectively and pilot extensively • Utilize HP Sizer for Microsoft Exchange 2010 to obtain ballpark HW config information for servers and storage
  75. 75. HP Tiered Solutions for Exchange 2010
  76. 76. About Works Computing • Founded in 1994 • Privately held company • Steady year over year growth in both revenue and head count • Hewlett-Packard‘s largest Enterprise Partner in the Region • Core competency's are in Unified Communications, Virtualization, Business Continuity, Database Infomratics, Networking, Managed Services • State of the art demo lab and training facility
  77. 77. Our approach to Exchange 2010 Upgrades • Assess the environment • Design and Plan the proposed solution with estimated hardware/software needs and high-level project plan • Develop step-by-step procedures for implementing and migrating to the new environment; Develop detailed project plan • Integrate/Implement the new environment • Pilot the new environment, typically up to 25 users with varying skill sets and across multiple sites • Rollout environment into production • Hands-on workshop training covering the new environment • Project closure, debrief of the project
  78. 78. Where to go from here • Try Exchange 2010 in our Lab • Design & Planning Workshops • Sizing & Performance Workshops • Administration & Management Workshops • Proof-of-concept Workshops
  79. 79. Q&A
  80. 80. Thank you for attending