This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner audience or other authorized recipients. This presentation may contain information that is confidential, proprietary or otherwise legally protected, and it may not be further copied, distributed or publicly displayed without the express written permission of Gartner, Inc. or its affiliates.© 2011 Gartner, Inc. and/or its affiliates. All rights reserved.

Michael Silver

Preparing for the End of Windows XP; Is Windows 8 in Your Future?

By 2013, 60% of important ISV Windows applications will havea new release that is not supported running on Windows XP.

If You're Not Already Moving Off Windows XP, You're REALLY Late!

Reasons why ISVs will no longer support Windows XP for new

releases by 2013:• XP installed base will be under

5% by YE2013• ISVs want to minimize number of

Windows versions they support.• ISVs don't want to support a version of

Windows not supported by Microsoft• ISVs want to get users to upgrade (and

pay for) their latest software

Reasons why ISVs would continue to support Windows XP for new

releases by 2013:• If XP installed base stays high

- Weak economy prevents organizations from replacing PCs

- Windows 7 fails• If ISVs cannot react to Windows 7

changes• If Microsoft extends Windows XP

Extended Support

Win7 WinXP

The State of Windows 7 Migrations

2

Finished

Well under way

Just started/ starting

Huh?

• Windows 7 migration is the single biggest project for most organizations today

• Companies using this as a chance to improve processes and control

• Tying in Office migrations

• Some confusion about Windows 8 timing

Source: Gartner May 2011

Key Issues

1. What do you need to know about the new versions of Windows and Office?

2. How should organizations plan their migrations?

4

The Two Faces of Windows 8

Metro UIWinRT AppsNew “Start” menu

“Windows Desktop”Win32 Apps

Security ImprovementsWindows to Go

Hyper-V

Windows 8 SKUs

Pro

Enterprise

• ARM Devices• Microsoft controlled preloads• Limited Win32 Support• Includes Word, Excel, PowerPoint & OneNote

• Consumer SKU• Now includes Multilingual User Interface (MUI)• Consumer-oriented

• Business/Prosumer SKU• Now includes MUI and BitLocker• Includes Hyper-V

• Requires SA• Includes Windows to Go use rights, VDI access rights,

advanced VDI client technology, DirectAccess, Branch Cache, AppLocker

RT

Relative Success of Major vs Minor Versions of Windows in Enterprise

Plumbing Releases

Polishing Releases

Windows 8RT/Metro

2000 2001 2006 2009 2012?

?

Rel

ativ

e S

ucce

ss (i

llust

rativ

e)

Too difficult?

Migration fatigue?

A hit?

Windows“Desktop”

Difficult to move, but

pent up demand.

Short time till

successor.

Too difficultRecession

Bad reputation

Windows 7/8 Deployment

• Vista Orgs• BitLocker/Direct Access• MUI & BitLocker in

Professional SKU• SMB, mostly tablets

• Windows 8 Immature• XP Support Ends 8 April

2014 • Safety in Numbers

Skip Windows 7 for Windows 8?

Mix 7/8• Tablet Users• Migrate by Attrition (after XP eliminated)

Top Reasons to Move to Windows 7, not 8

• Support for Windows XP will end before you can fully deploy Windows 8

• Microsoft Custom Support is Expensive and money can be better spent moving to Windows 7

• New applications/versions won’t run on Windows XP

• ISVs support Windows 7, but not Windows 8 yet• Windows 8 Management and Security Support?• So many organizations are moving to Windows 7

and most will skip Windows 8 for PCs; there’s safety in numbers…

9

What is Office 2013?

• When will Office 2013 Ship?• When will it be deployable?• Will there be mobile device (e.g. iPad) apps and

how will they be licensed?• How successful will it be?• What should I do about

Office 2003?• What about SA?

(Related research: "Set Your Timeline to Plan for Office 2003 End of Life" [G00175659])

You are here

Office 2003 extendedsupport ends

Prep/TestO15

Deploy O15

Office 15RTM? Mature?

Office 2003

Office in Office 365

Mail (Exchange)

Unified Communications

(Lync)Collaboration (SharePoint)

Office(Office Web Apps)

Office(Professional

Plus)Forefront

There are no Office functions in Office 365 that are not in Office Professional Plus 2010

Office in Office 365

Strengths• Compatibility with Microsoft

Office 2013 and earlier releases.

• Reduced cost versus Office 2013, in some situations.

• IT staff no longer have to manage Office productivity infrastructure.

• User-based licensing will reduce costs for users with multiple organization-owned devices.

Challenges• Office Web Apps has a small

feature set and high cost, compared with Office 2013.

• Nonperpetual licenses.• Organizations with existing

SharePoint implementations would need to outsource to Microsoft to license Office Web Apps via Office 365.

• Office Web Apps currently have no offline capability.

Key Issues

1. What do you need to know about the new versions of Windows and Office?

2. How should organizations plan their migrations?

App Compatability Solutions• Fix, repair, upgrade

- If you can — best, longest-lasting solution

• Replace- Defunct or in-house written applications

• Shim- Change the way Win7 treats the application- Short-term fix

• Remote- SBC — especially if you have RDS CALs/TS/Citrix already- BUT — apps may not work; only extends support one year

• Virtualize (remotely) — hosted virtual desktops- Especially if you are already planning this- Does not extend support life

• Virtualize (locally) using XP Mode or MED-V(Related Research: "XP on Windows 7: Temporary Relief for Migration Headaches, but No Cure" [G00201125])

Windows Migration Best Practices

• Plan UAC.• Allocate sufficient time to test and remediate

browser applications.• Understand ISV support.• Involve the users.• Set a (conservative) target end date.• Ensure you have an accurate inventory/usage.• Budget enough time for application testing.• Plan properly for 64-bit.• Avoid deploying too much XP Mode or MED-V.• Consider deploying with new office product.

(Related research: "Best Practices for Planning Windows 7 Deployment" [G00174371])

Windows/Office Migration Pitfalls

• Pilot is too short• No business plan• Don't measure progress and success• Continuous migrations with no breaks• Resources not dedicated to the project• Planning a forklift without zero/light touch• Project stuffing• One person is project manager and technical lead• Don't seek professional help early enough

(Related research: "Pitfalls to Avoid on the Road to Windows 7 and Office 2010 Migration" [G00174271])

Your Action Plan

Windows 8 Limit time spent to special projects until Win7 is deployed.

Windows XP Get off. Security support ends in April 2014.

Office 2003 Evaluate risk tolerance as it ages. Support ends April 2014.

Expect more demand. Plan for it.

Open Source Office Check ROI, and be selective.

Office 2007 Consider skipping unless you own licenses for Office 2007 and not for Office 2010.

Windows Vista Plan to switch to Windows 7 for new PC deployments.

Windows 7 Finish deployment in 2013.

Office 2010

Mac OS

Office 15

Try to delay new purchases to get O15, but you may still need to deploy O2010 to get O03 out before support ends.Quantify ROI of new features when they are announced.

Related Gartner Research "Creating a Timeline for Deploying Windows 7 and

Eliminating Windows XP"Michael Silver (G00213442)

"New World of Emerging Devices and Usage Paradigms Influences Features of Microsoft's Windows 8 "Stephen Kleynhans, Michael Silver (G00230313)

"Windows 8 Changes Windows as We Know It" Michael Silver, Stephen Kleynhans, David Smith, Neil MacDonald t(G00225445)

"2011 Client OS and Office Survey”Michael Silver (G00232431)

"The Benefits Side of a Windows 7 Business Case"Michael Silver, Stephen Kleynhans (G00200733)

For more information, stop by Gartner Solution Central or e-mail us at solutioncentral@gartner.com.