8/13/2019 Dell Prepare Windows 7 in Three Phases

1/5

Prepare for Windows 7 in Three Phases

Gartner RAS Core Research Note G00170151, Stephen Kleynhans, 1 October 2009, RA2 07182010

Many organizations are skipping Vista and looking forwardto Windows 7. This research provides the necessary steps toprepare for Windows 7 and ensure a successful migration with

adequate operating system (OS) support.Key Findings

Preparation is essential for a successful migration. Most organizations will require 12 to 18months to prepare for a Windows 7 migration.

Organizations that have tested or prepared for Vista and have good management systemsand processes could complete the preparation process in 12 months.

Complex environments will face additional issues and require more time.

Recommendations

Allocate sufficient time and resources to upfront activities to lower the costs duringmigration.

Although your planned migration may be more than a year away, dont delay the initiationof the preparation process.

Form a project committee that includes members from each major business unit, as wellas operational groups in the IT organization, to oversee the development of a projecttimeline that features high-level milestones and estimates required resources.

Establish a formal, comprehensive and workable testing methodology to ensure thatissues are identified and categorized.

Plan on piloting for a minimum of three months. The shorter the pilot, the more problemswill occur during the deployment.

8/13/2019 Dell Prepare Windows 7 in Three Phases

2/5

ANALYSIS The tepid corporate responseto Windows Vista indicatesthat, for most organizations,Windows 7 will be the firstmajor OS migration project in

more than six or seven years. As they start their projects,many organizations are unsurehow to approach the planningand testing process. Given thatproper preparation is essentialfor a successful migration,enterprises should allocatesufficient time and resources toupfront activities. For most, thiswill take between 15 and 18months, although some well-organized companies couldtrim the time to 12 months.More-complex environmentswill undoubtedly causeadditional issues that will needto be addressed and added tothe plan. Its important to get started early and regularly reviewtimelines and plans.

For the most part, we assume that organizations have not madeany significant progress with Vista preparations and migrations.Organizations that have done some preparation for Vista shouldfind that most of their efforts are directly applicable to Windows 7,so they will be able to reduce their overall timelines (see Figure 1).

1.0 Preparation and Education: Three Months

Organizations should establish a project committee and developan overall project timeline. The project committee should includemembers from each major business unit, as well as operationalgroups from the IT organization. The project timeline should includehigh-level milestones and estimates of required resources.

Companies must obtain a detailed inventory of the userenvironments, including hardware, software and processes.Without this, planning and testing will be hit-or-miss, based on ITperceptions, rather than reality. Although many companies have ageneral handle on the PCs in their environments, most have moredifficulty with the other components. A full inventory will include thefollowing areas:

1.1 PC Hardware Although organizations should primarily install Windows 7 on newequipment, having a complete inventory sizes up the problem andprovides guidance as to the order in which users are likely to bemigrated. Organizations that have skipped Vista will probably needto perform some forklift upgrades, and will find that a detailed PC

hardware inventory is even more essential. The inventory will alsohelp identify deviations from corporate standards, and shouldidentify where user data is being stored.

Along with basic configuration, age and model information, theinventory should also include more-detailed data (for example,BIOS levels, memory and disk space), as well as installedcomponents (for example, adapter cards and chipsets). TheWindows 7 Hardware Assessment tool can help identify potentialissues. For the most part, systems purchased since early 2007(machines that were released after the introduction of Windows

Vista) should have no problems running Windows 7, unless theywere poorly configured.

Decide which machines to upgrade based primarily on their ageand secondarily on their configurations. If PCs purchased in 2009and 2010 are chosen for upgrade to Windows 7 in 2011, theirconfigurations wont really matter. Unless your migration costs areextremely low, dont plan to upgrade any PC that has less than twoyears of useful life left before replacement.

1.2 Attached PeripheralsEven when PCs are replaced, attached devices are frequentlyretained. These may include monitors, specialized keyboards and

mice, external storage devices, printers or other items that requiresupporting drivers. Business-critical devices (i.e., essential to thecompletion of a business function) should be identified. Fortunately,most devices supported on Windows Vista carry that supportdirectly to Windows 7. This means that, for most organizations,only older legacy devices are likely to pose an issue for Windows 7.Device driver compatibility should be somewhat less of a problem

2009 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction and distribution of this publication in any form without prior written permissionis forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy,completeness or adequacy of such information. Although Gartners research may discuss legal issues related to the information technology business, Gartnerdoes not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions orinadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.

Figure 1. The Three Phases of Preparation

Source: Gartner (October 2009)

InformationGathering

Three months

EngineeringTesting

Six to nine monthsPilot Testing

Six months

Getting ready will take 15 to 18 months.Don't wait get started now on the first steps.

Hardware Peripherals Applications Utilities Processes

IT staff Architects Developers Key team

members

Lab testing ofapplications

Set standards Create images

and test Develop processes

Alpha test Beta test Cross key

business events

8/13/2019 Dell Prepare Windows 7 in Three Phases

3/5

with Windows 7 than it was initially for Vista. Only a completeinventory of peripherals can expose potential problems. If yourplans include installing 64-bit Windows 7, expect to find morelegacy devices without suitable drivers. This will require budgetingfor their replacement, and adding time to allow for the additionalwork.

1.3 Applications A software inventory must include all applications and utilitiesinstalled on corporate PCs. Many software inventory tools exist,including Microsofts free Application Compatibility Toolkit (ACT)5.5. It is not sufficient to restrict testing to formally supportedapplications, because users opinions may differ significantly fromthose of the IT organization, resulting in substantial delays duringimplementation. All applications should be categorized into fourbuckets: business-critical, user-critical, support tools/utilities andall others. A weighting should be added that establishes each asbroadly deployed, narrowly deployed or specialized. All business-critical applications must be determined to work on Windows 7,while all user-critical applications must operate or have reasonable

workarounds. Because most support tools will require a newversion after an OS change, replacements or upgrades must beidentified for each utility.

1.4 Processes and Procedures Although not typically considered an asset, the processes andprocedures that an organization has created to make the userenvironment functional are likely to be affected by an OS change.Hence, its critical that organizations document all the processesassociated with outfitting their users. This should also include a listof policies, including group policy objects (GPOs).

During this initial phase, organizations should create a testingfacility/laboratory. It should include a representative sample ofsystems expected to be used with Windows 7 throughout theorganization. Although its impossible to have one of everything,any hardware combination used by more than 5% of the user baseor part of a business-critical function should be represented.

During this phase, key members of the technical team shouldbegin using Windows 7 (final code should be available to corporatecustomers in September 2009, or in August under programs suchas MSDN and Technet) as part of their daily routine, followed bymost IT staff. This leverages the most technically competent (andleast likely to be seriously impaired) employees to spot potentialproblems. It also serves as an informal training ground.

2.0 Development: Three to Six Months The replacement of the OS is an opportunity to update the userenvironment and implement best practices. As such, it is goodto survey the stakeholders (e.g., user groups, developers and ITsupport) to determine whether there are pain points or other issuesthat must be addressed. With this feedback and the completeinventory, four separate development areas must be addressed.

2.1 Windows 7 Administrative EnvironmentOrganizations already using Windows Vista should find that littlechange is required for Windows 7. For the most part, all GPOs andadministrative processes function the same for Windows 7 as theydo for Windows Vista, with a few additional options.

Organizations currently on Windows XP will require more-extensivechanges. Using Windows XP processes as a starting point,organizations must identify where Windows 7 5 administrationwill deviate. Organizations must examine the new features andcapabilities within Windows 7 and determine a response. Theywill also need to become familiar with new GPOs introduced withWindows 7, as well as those that came with Vista.

Determining the deployment techniques that will be used is acritical decision. Even organizations bringing in Windows 7 on newequipment need to review image distribution, software deployment,and migration processes for data and settings. Organizationsshould also familiarize themselves with newer options, such asapplication virtualization, which might be appropriate for some

applications.

Organizations also must identify the implications of leveraging newadministrative capabilities in Windows 7 and plan to address theseissues. This goes beyond changes to the administration tools builtinto the product; it extends to third-party tools that are l ikely torequire an update.

2.2 Windows 7 User Environment and StandardsOrganizations need to determine guidelines for hardwareselection. Although Microsoft has provided general hardwarerecommendations, these must be interpreted with respect tocorporate standards and procurement practices. Organizationsshould review our regularly updated hardware configurationrecommendations.

Companies must also revisit the question of lockdown for theiruser environments, given the improvements in this area providedwith Windows 7. Again, organizations that have skipped Vistaare likely to have more to do to prepare for a more locked-downenvironment, but even organizations running Vista will need todecide if any changes are required, based on the new user accountcontrol levels in Windows 7.

2.3 Image Development The final and most-critical piece of the development processinvolves the creation of an initial master build for a corporate user

environment. This will include all the common elements includedin a corporate desktop PC (for example, major applications,management utilities, security, and anti-malware tools andcommunication tools). It will be used for initial application testing,user pilot testing and as the basis for further customized builds.

8/13/2019 Dell Prepare Windows 7 in Three Phases

4/5

2.4 Infrastructure impactsWindows 7 adds a number of new networking and operationalcapabilities such as Direct Access, Branch Cache or FederatedSearch, which could have server dependencies and significantnetworking impacts. These will require additional planning andeducation to determine whether they are compatible with your

infrastructure and, if so, how to properly integrate them into theenvironment. For example, the BranchCache feature may improveyour software distribution capabilities, but the content that usersaccess must be on Windows Server 2008 R2.

3.0 Establish a Testing Program: Six to NineMonthsOrganizations must establish a formal, comprehensive andworkable testing methodology to ensure that issues are identifiedand categorized (for example, impact, scale/scope of issue andrisk assessment). Unfortunately, most companies lack formalassessment processes, which results in inadequate and inefficienttesting (for example, poor allocation of resources, insufficient testscenarios and incomplete regression). This slows the migrationand drives up costs. Beyond providing assurance that the new OSwill function for users, a well-designed testing process serves asa critical learning mechanism and development tool by identifyingthe shortcomings of the proposed environment and driving thedevelopment of workable solutions. Once the migration is underway, a formalized testing methodology will help organizationsmanage system images, application rollouts, service packs andother major initiatives that will emerge.

Establishing a testing methodology requires setting appropriategoals in the context of business objectives for exploiting Windows7s capabilities. Organizations must decide early what successfultesting means for different stakeholders. Although most thinkof testing purely for compatibility purposes, that is only oneobjective, particularly given the compatibility improvements duringthe past decade. Testing provides derivative value in trainingand experience; impact analysis of images, support processesand changed configuration options; and design, including theidentification of opportunities for optimization provided by newfeatures of the OS. A key requirement for testing is documentationto ensure that information gleaned from the process is recordedand followed up.

Before the new environment is rolled out, three types of testingmust be performed: basic application testing, image testingand environment testing. Application testing involves testingapplications functionality with the new OS. Image testingincludes testing a complete collection of applications and tools,ensuring compatibility of the image with hardware platformsand implementation tools. Environment testing evaluates thesupportability of the new environment, including the processes formanagement, administration and technical support. It also includesusability testing, gauging users reactions to the new environmentand making necessary tweaks to ensure that it fits their needs.

3.1 Lab TestingIt is impossible to test all combinations of hardware and softwarewithin any major organization. Most large enterprises can paredown the number of permutations by finding common systempatterns. For configurations that cannot be represented in thelaboratory, unless some business-critical external force is at work,

a test in production methodology will generally suffice, assumingthat high-level testing has been performed on similar configurations.

The way PC activation works for volume license customerschanged between Windows XP and Windows Vista (and, byextension, Windows 7). During testing, enterprises should ensurethat they are familiar with the volume activation options and includethem in testing scenarios.

Application testing can be conducted concurrently with initialhardware testing. For each product, a formal checklist of testparameters and goals should be created, containing five sections:

Installation: Does the application install cleanly or are tweaksrequired?

Basic functionality: Does it start up, and do major functionswork?

Advanced functionality: Do specialized or rarely usedfunctions, such as macros, perform?

Interoperation and interaction: Does the application coexistwith others, do communication and data interchange functionsstill work, and has the user interface changed?

Performance: Does the application behave differently, and havehardware requirements changed?

Regression testing (that is, testing against previously discoveredproblem scenarios) is critical to ensure steady progression to arelease candidate. Test scenarios should be built using help-deskrecords and notes from previous testing exercises. Reintroducingold problems will severely damage the IT organizations credibilityand turn an otherwise successful implementation into a failure.During testing, any anomaly or change from the current versionmust be recorded. This implies that the tester is somewhat familiarwith the current environment.

Deeper functionality testing is likely to require the participation of

a user or a developer to create a formal script. IT groups shouldprioritize the application testing order based on the breadth ofdeployment, with the most widespread handled first. This willspeed up the process of shifting to full image design and testing.Companies should also consider the ability to run applications in areduced-rights user environment.

8/13/2019 Dell Prepare Windows 7 in Three Phases

5/5

One difference between Windows 7 testing and previous versionsis the availability of richer and more mature testing tools. AcressosInstallshield and Symantecs Wise Installer include capabilitiesto detect and mitigate conflicts between applications and theOS. Microsofts ACT 5.5 has emerged as a solid tool for findingpotential issues with application and device compatibility. It canbe run on Windows XP systems to help triage the testing effort,enabling organizations to better allocate resources during testingand remediation. Customers should download and familiarizethemselves with the ACT.

The Microsoft Deployment Toolkit (formerly known as the BusinessDesktop Deployment Toolkit) has also been expanded to includemore tools and best practices. Testing tools that continually lookfor incompatibilities with new versions of Windows, as well asService Packs, are available from such vendors as App-DNA andChangeBASE.

Two areas of special concern for testing that might be overlookedare testing browser-based applications for compatibility withIE8 and testing applications in a 64-bit environment. With Vista,customers reported the most serious and often most difficultto remediate compatibility problems with IE6-targeted Webapplications failing under IE7. This situation is unlikely to improvewith IE8 in Windows 7. We strongly recommend that customersbegin this phase of testing as early as possible, becauseremediation efforts may require recoding or adding virtualizationto their environments. On the 64-bit front, it is likely that, by 2011,some users may require 64-bit support for their environments.

Adding a 64-bit test environment will identify potential issues early,and, although it will add some additional effort, it will not seriouslycomplicate the testing process.

Once application testing is well under way, attention must beturned to the development and testing of system images. Thistesting includes the same five categories as for applications,with particular attention given to interaction and installation.Image testing requires matching images to particular hardwareconfigurations, and is likely to demand the largest effort. Devicedrivers for legacy peripherals must also be validated, especiallyif youre implementing 64-bit. Once the first few images arecompleted, subsequent ones will require a minimum of three daysto create, followed by a day or more of testing.

The final area is the testing of internal processes. Many well-established procedures and policies will need fine-tuning or outrightreplacement with Windows 7. Particular attention should be givento migration processes, moves/adds/changes and ongoing supportprocesses (for example, software distribution and system backup/ recovery).

4.0 The Pilot Test Phase: Three to Six MonthsOnce formal lab testing is done, pilot testing should begin. Pilotingmoves the testing out of the lab and exposes real users to the newenvironment. Most pilots should consist of at least two phases.

The first should test basic builds, establish training needs, gaugegeneral user reaction and enable IT staff to exercise their new

Windows 7 skills. This pilot should be limited to a small group ofusers (fewer than 50) that does not perform mission-critical (orhigh-profile) activities, and should optimally last for 45 to 90 days.

Following this, a second, broader pilot extends the first by fieldtesting installation and support processes within a production(but still closely monitored) environment. The broad pilot shouldoptimally run an additional 45 to 90 days to ensure that the pilottests extend across several different business process cycles (forexample, month-end and quarter-end). For most organizations,a three- to four-month piloting period will be sufficient; however,those with more-complex environments, or those that encountersignificant problems in early testing, may need to run for the full sixmonths.

In many cases, organizations may be tempted to cut back onpiloting to speed the overall timeline. Although both phases of thepilot could be completed in as little as two months, shortening thepilot period increases the likelihood that some underlying issueswill not be encountered until the production rollout phase, whenmaking repairs is more disruptive.

Once the piloting process has been completed, the preparationprocess is effectively completed. Organizations can then conductstaged rollouts of the OS to their user populations. Critical to alltesting and piloting is ensuring that a suitable feedback mechanismis in place.

5.0 Bottom Line A formal testing process significantly smoothes the Windows 7migration path by enabling companies to spot potential problems,adjust designs to better leverage new features and build experiencewith the nascent platform.