+ Cincinnati + Louisville + Nashville + Columbus+ Detroit + Indianapolis

KiZAN Technologies

Cassie HendricksBryan Cornette and Eric Ross

Agenda 2:00 PM – Welcome & History2:05 PM – Exchange Migration2: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: How we approach migrating off of 2003 and mitigate the issues and risks of staying on an unsupported platform

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.

KiZAN? “I’ve heard of KiZAN from somewhere…

What does it mean? Isn't it a Japanese

word or something . .?”

Foundedin 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

Why KiZAN?

Practice Areas

System Center

& Desktop

Azure BusinessIntelligence

Office 365& Cloud

CustomApplication

Development

SharePoint

MicrosoftLync

Virtualization

MicrosoftExchange

Windows 8& Mobile

Development

CustomRelationshipManagement

Windows Server

KiZAN and Exchange

Bryan Cornette – Messaging Practice Lead Eric Ross – Messaging Consultant

• History of Exchange 2003• Exchange 2003 Support Discontinued• Typical Migration Pains• Question and Answer

Topics

Client Integration Manual configuration of clients versus automated configuration via autodiscover

History of Exchange 2003

Client IntegrationSince 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

Client Expectations

Client Integration

Client ExpectationsArchitecture Changes

Powershell

Permissions model

32 to 64 bit

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 ExpectationsArchitecture ChangesTransformation ofMobile Landscape

History of Exchange 2003

BES was the big player

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

• Extended support ended 4/8/2014

Support Discontinued

Support provided Mainstream Support phase Extended Support phaseCurrent Support as

of April 8, 2014

Paid support (per-incident, per hour, and others) X X  Security update support X X  

Non-security hotfix support XRequires extended hotfix

agreement, purchased within 90 days of mainstream support

ending.

 

No-charge incident support X  Warranty claims X  

Design changes and feature requests X  

Product-specific information that is available by using the online Microsoft Knowledge Base X X

 

Product-specific information that is available by using the Support site at Microsoft Help and

Support to find answers to technical questionsX X

 

•Client Issues•Migration Issues

Typical Migration Pains

Outlook 2013 is not supported on Exchange 2003Outlook

Client Issues

Outlook 2003 is not supported on Exchange 2013

Client licensing considerations

OutlookRedirection

Client Issues

Devices that use EWS not honoring the legacy redirect to Exchange 2003 from 2010

EAS redirection issues primarily Android devices

Outlook may not work correctly where customers are using WAN accelerators that do not support newer versions of ExchangePitfalls

Client Issues

Server side rules can become corrupt forcing users to recreate them

3rd 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

Users are disconnected during migration

Mailbox Migration Issues

Migration Issues

Extremely large mailboxes either in size or item count will NOT migrate without remediation

Double hop migration to 2010 or 2007 first then to 2013Migration

Options

Migration Issues

Resource forest with linked mailboxes

Office 365

Migration to 2010 better support than migration to 2013 Public Folders

Migration Issues

Scripting languages to perform workflows no longer supported as they were in 2003

Many organizations prefer traditional PF management as opposed to current

During migration verifying logs are truncated utilizing properly configured backup solution or circular logging

Pitfalls

Migration Issues

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?

•MAPI•Address Rewrites• 3rd Party Application Integration

Functionality No Longer Supported

KiZAN’s Current Offers and Packages

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.

Windows 8 & Mobile Development

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 2003Domain 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,5001,000 – 3,000 mailboxes: $5,000

3,001 – 10,000 mailboxes: $7,50010,000+ mailboxes: please call us

KiZAN Windows Embedded 8.1 Proof of Concept= $5,000

Optional KiZAN System Center 2012 R2 Configuration Manager= $3,000

Windows 8.1

• Planning• Cloud Identities only• 25 Mailboxes migrated to Office 365

Designed for those customers that need better understanding of the solution

Exchange Migration PackagesCloud/Office 365

Exchange 2010/2013$15,000

Platform Independent

$12,000

Exchange 2003/2007$17,000

A Day with an Architect$1,500

• 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

Please contact us if you are interested in any offers or would like more information!

Cassie Hendrickscassieh@kizan.com

502-410-5882

Session 2: July 15th

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