KiZAN Technologies Cassie Hendricks Bryan Cornette and Eric Ross + Cincinnati + Nashville + Detroit + Louisville + Columbus + Indianapolis

Agenda

2:00 PM – Welcome & History 2:05 PM – Exchange Migration 2:45 PM – Questions & Wrap Up

Session 1:

The pains of migrating off of 2003 but the risk of staying on an unsupported platform Session 2 will be held July 15 of 2003 and mitigate the issues and risks of staying on an unsupported platform : How we approach migrating off

KiZAN?

“I’ve heard of KiZAN from somewhere… What does it mean? Isn't it a Japanese word or something . .?” KiZAN was derived from the Japanese word,

“Kaizen.”

It means “improvement” or “change for the better.” It refers to philosophy or practices that focus on continuous improvement of processes and management.

Why KiZAN?

Founded in 1991 Award Winner Gold certified Building Relationship

Founded in 1991 to help companies implement business solutions using Microsoft Technologies.

First Global Partner of the Year!

Workplace Flexibility Award Winner!

2012 and 2013 Heartland Partner of the Year!

Gold-Certified Microsoft Partner serving Indiana, Kentucky, Michigan, Ohio and Tennessee with clients in several other states We create “Raving Fans” by building relationships one at a time

Practice Areas

Azure Business Intelligence Custom Application Development Microsoft Lync Microsoft Exchange Custom Relationship Management System Center & Desktop Office 365 & Cloud SharePoint Virtualization Windows 8 & Mobile Development Windows Server

KiZAN and Exchange

Bryan Cornette – Messaging Practice Lead Eric Ross – Messaging Consultant

Topics

•

History of Exchange 2003

•

Exchange 2003 Support Discontinued

•

Typical Migration Pains

•

Question and Answer

History of Exchange 2003

Client Integration

Manual configuration of clients versus automated configuration via autodiscover

History of Exchange 2003

Client Integration Client Expectations

Since Exchange 2003, use of messaging platforms and user expectations have transformed The users perception of the need to have the full Outlook client in order to have complete functionality

History of Exchange 2003

Powershell

Client Integration

Permissions model

Client Expectations

32 to 64 bit

Architecture Changes

Moving from a high I/O space saving model to a low I/O model with higher disk space utilization

History of Exchange 2003

Client Integration Client Expectations Architecture Changes Transformation of Mobile Landscape

BES was the big player Availability of devices and features was limited in comparison to the options currently available

Support Discontinued

•

Extended support ended 4/8/2014 Support provided Mainstream Support phase Paid support (per-incident, per hour, and others) Security update support

X X

Non-security hotfix support

X

Extended Support phase

X X Requires extended hotfix agreement, purchased within 90 days of mainstream support ending.

Current Support as of April 8, 2014 No-charge incident support Warranty claims Design changes and feature requests Product-specific information that is available by using the online Microsoft Knowledge Base Product-specific information that is available by using the Support site at Microsoft Help and Support to find answers to technical questions

X X X X X X X

Typical Migration Pains

•

Client Issues

•

Migration Issues

Client Issues

Outlook Outlook 2013 is not supported on Exchange 2003 Outlook 2003 is not supported on Exchange 2013 Client licensing considerations

Client Issues

Redirection Outlook Devices that use EWS not honoring the legacy redirect to Exchange 2003 from 2010 EAS redirection issues primarily Android devices

Client Issues

Pitfalls Outlook may not work correctly where customers are using WAN accelerators that do not support newer versions of Exchange Server side rules can become corrupt forcing users to recreate them 3 rd party client based plugins. All plugins will need thorough testing due to server side design changes

Migration Issues

Cross forest migration can be painful from the amount of administrative effort involved utilizing native Exchange tools

Migration Issues

Mailbox Migration Issues Users are disconnected during migration Extremely large mailboxes either in size or item count will NOT migrate without remediation

Migration Issues

Migration Options Double hop migration to 2010 or 2007 first then to 2013 Resource forest with linked mailboxes Office 365

Migration Issues

Public Folders Migration to 2010 better support than migration to 2013 Scripting languages to perform workflows no longer supported as they were in 2003 Many organizations prefer traditional PF management as opposed to current

Migration Issues

Pitfalls During migration verifying logs are truncated utilizing properly configured backup solution or circular logging Migrating application relay. Often devices and applications are configured to send mail to the IP or name of a single Exchange server, and that server will eventually be decommissioned

Questions?

Functionality No Longer Supported

• • •

MAPI Address Rewrites 3 rd Party Application Integration

KiZAN’s Current Offers and Packages

Windows 8 & Mobile Development

Do you have a mobile strategy? Is your current mobile application not quite what you thought it would be? KiZAN's Windows 8 and Mobile Development team has a solution specified for your needs. Whether you have an application that needs work or you don't have an application at all, we can help you engage your customers wherever they are.

Domain Controller Upgrade Package

KIZAN will work with your staff to replace your existing domain controllers with a new Windows Server 2012 R2 domain controller. Domain/Forest Functional Level must be at a minimum of 2003

Domain Controller $600 With Certificate Services $900

Exchange Health Check Package

Already have an Exchange Server deployed?

KiZAN consultants can perform a detailed assessment and health check of your current environment and guide you to a solution.

Up to 1,000 mailboxes: $2,500 1,000 – 3,000 mailboxes: $5,000 3,001 – 10,000 mailboxes: $7,500 10,000+ mailboxes: please call us

Windows 8.1

KiZAN Windows Embedded 8.1 Proof of Concept = $5,000 Optional KiZAN System Center 2012 R2 Configuration Manager = $3,000

Cloud/Office 365

Exchange Migration Packages

Exchange 2010/2013 $15,000 Exchange 2003/2007 $17,000 Platform Independent $12,000 • • • • • • • • • • • Prepare Active Directory for Office 365 Establish and Configure Office 365 tenant Configure existing Exchange environment for Office 365 Migrate 25 mailboxes to Office 365 Provide 2 hours of admin and migration training 4 hours of migration support 20 Jabra Lync optimized devices 25 Brainstorm QuickStart guides of your choice Planning Cloud Identities only 25 Mailboxes migrated to Office 365 A Day with an Architect $1,500 Designed for those customers that need better understanding of the solution

Cassie Hendricks [email protected]

502-410-5882

Session 2: July 15

th How we approach migrating off of 2003 and mitigate the issues and risks of staying on an unsupported platform