1 / 14

NHSmail: Technology Refresh

NHSmail: Technology Refresh. 26 th February 2008 Mike Dolan NHSmail Migration Manager. NHSmail: Technology Refresh. Why? What? How? When? Who?. Why?.

jeffryc
Download Presentation

NHSmail: Technology Refresh

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NHSmail: Technology Refresh 26th February 2008 Mike Dolan NHSmail Migration Manager

  2. NHSmail: Technology Refresh • Why? • What? • How? • When? • Who?

  3. Why? There are grounds for doubt that the NHSmail strategic objectives can be met without a significant refresh of service functionality and integration capability By undergoing a Technology Refresh, transitioning the core platform technology to Microsoft Exchange 2007, NHSmail significantly enhances the likelihood of meeting its financial targets, development objectives and providing users with a satisfactory functionality and usability experience Solution

  4. What?(1) • Business continuity lead – 155,000 active user accounts + 20,000 Generic Mailboxes. • What users can do now they can do on the new platform • Continuing dual data centre design • Secure Exchange 2007 platform with push mobile email • 500 server build to support 500,000 users from day one • Taking advantage of 64-bit technology and the 5 server roles of Exchange 2007

  5. 64bit – why? • Addressable Memory • 32-bit = 232 = 4 GB maximum memory • 64-bit = 264 = 18 Exabyte maximum memory • Current hardware restricts memory to 512 GB • Microsoft Windows currently restricts memory to 18 TB • Exchange use of memory -Store Cache • Reduces disk Input/Output per second • With 32-bit • As memory runs out  decreased # of users / server = increased # of servers = increased cost / user • With 64-bit • As memory runs out add memory (cheap) not servers (not cheap) • More users/Server, 30K to start 50k design goal

  6. What?(3)Server Roles Offer greater business continuity than Exchange 2003 as roles split across servers Mailbox Server Client Access (CAS) Hub Transport Edge Transport Unified Messaging (Not in initial Release) Breakout Roles (one or more of the 5 roles above, but used for a specific task)

  7. Hub Transport Server Edge Transport Server Client Requests Client Access Server DB Cache ( Ram ) Mailbox Server Mailbox Store ( Disk )

  8. Enhanced DR capability with CCR & SCR Clustered Continuous Replication(DataCentre1) Standby Continuous Replication (DataCentre2)

  9. What?(6) • Full push mobile support out of the box for 200+ devices via Microsoft Active Sync • Single Domain AD forest to support single email domain • National Directory • Fax & SMS Gateway • User and LOA administration functionality • Online training resource via Microsoft NHS Resource Centre

  10. What?(7) User Access • Thin Client Portal access based on Outlook Web Access (premium and light) with admin screens developed by C&W • OWA Premium requires IE 6.0 or 7.0 non IE browser users will use OWA light(*) • Outlook Client Access will be by Outlook Anywhere • Outlook 2007 will leverage maximum features of Exchange 2007 but Outlook 2003 is also supported (hot fix*) • Users of clients below Outlook 2003will gain more functionality from OWA • IMAP and POP access for other clients (*) functionality differences can be found at http://technet.microsoft.com/en-us/library/aa997437.aspx http://technet.microsoft.com/en-us/library/bb684897(EXCHG.80).aspx

  11. How?(1) Migration of Existing Users No entirely disruption-free option However should bear in mind 70-80% of users will have to experience a refresh to their web portal access and associated training requirement. Main concern and risk is around the thick client users reconfiguration and associated network impacts of data transfer to new client profiles

  12. How?(3) Migration Current Design • Sync and Cutover approach • Copy data over a period of time production Exchange platform • Final sync and cutover on weekend • OWA access only post cutover, client deployment via Auto discover for Outlook 2007 and configuration scripts for Outlook 2003 • Client deployment over 1 week to mitigate risks to N3 network • IMAP access to non system accounts restricted initially

  13. When? • In detailed design phase now, this will drive out the detailed plan for testing, which will in turn drive go live date • Cutover currently planned for late summer 2008 (no Programme Board agreed date as yet). • Server Orders placed • Model Office being built • Development of additional admin tools to complete by June 2008 • Online training available at least one month prior to go live • Enabling milestones: SynQ 2.7 released mid march 2008 (works with Outlook 2007 and Vista); ESR connector pilot in March 2008.

  14. Who? • Communications processes begun via all user Emails and LOA bulletins. • Migration approach will require LOA input to deployment planning for thick client users • Also looking to engage with Trusts wish to migrate to the service as a result of the move to Exchange 2007

More Related