Six Steps to Continuous Application Readiness

A Comprehensive, Automated Approach to a Predictable Process for Preparing and Delivering Any Application to Any Device at Any Time

Introduction

Most organizations are looking to move to the Windows® 7 platform, driven by the impending end of support for Windows XP, along with compelling business reasons based on the functionality that the new operating system provides. Additionally, many organizations are looking to simultaneously deploy the latest virtualization technologies, such as application virtualization, to simplify application management and reduce costs.

Despite the business benefits of migrating to Windows 7 or implementing application virtualization, these transitions can be taxing on everyone. For IT, they create extra work, longer hours, and higher stress. For employees, customers, and partners, they can disrupt access to vital applications and services. For management, they often spell budget overruns and end-user complaints. For the enterprise as a whole, they can delay new strategic initiatives aimed at creating competitive advantages.

Why are so many organizations still held hostage by technology transitions? Because even though software deployments and OS migrations are among the riskiest functions of IT, and the list of application preparation requirements continues to grow: application discovery, cataloging, compatibility testing, remediation and conversion, packaging, virtualization, etc; most organizations do not have a continuous process for preparing and deploying applications in a reliable, consistent way. Technology transitions are approached as a point-in-time project.

What’s needed is an efficient way to automate technology transitions—a process that not only gets you through today’s migration smoothly but also prepares you for the next. This is continuous application readiness.

That means every transition, whether it’s the OS, a missioncritical application, or a datacenter consolidation, should be undertaken with the future in mind. In other words, “application readiness” is really about change readiness. The ultimate objective is to build a future-proof environment that adapts to both fast-changing technologies and everchanging business requirements with equal ease.

And that means application readiness should be approached as a continuous process. It should implement best practices and technologies to ensure consistency and optimal operations; it should leverage existing investments, such as packaging technology, wherever possible; it should automate each phase of the process; and it should standardize practices and procedures so that deployments are reliable and repeatable.

With those overarching goals in mind, it becomes possible to move from a reactive, project-oriented approach to a proactive, holistic approach to continuous application readiness.

Today, the critical need for application readiness is underscored by projects such as Windows 7 migrations and application virtualization. However, with most organizations updating, repackaging and deploying over 30% of their applications annually due to new versions, upgrades and patches, the requirement extends beyond the initial migration project into a need for business as usual application management.

This paper outlines the six key steps of a migration project, illustrates the major tasks within each phase, and explains how the Flexera Software™ solution can reduce the risk and cost of your application deployments by providing a consistent approach to continuous application readiness.

6 Steps to Continuous Application Readiness

Step 1:
Identify What’s Being Used (and What Isn’t)

The first step requires obtaining an accurate view of the applications that are deployed across the organization. This is a good time to look at the application inventory and take stock of what is actually being used, as opposed to what is deployed. Depending on the end users’ abilities to install applications locally, there may be applications that cannot be centrally monitored or managed, but could be crucial to the business and therefore must be identified.

Beyond identifying application installation, analyzing application usage provides a deeper level of insight as to which applications are actually used. It is critical to know what is being used and, more importantly, which applications are not being used.

The Flexera Software solution integrates with industry-leading systems management technology such as Microsoft® System Center Configuration Manager (SCCM) to extract both application and hardware information as a baseline for continuous application readiness.

From a software perspective, it can extract the full titles of applications, the application’s producer, version information, and application usage details from SCCM to get an enterprise view of application consumption. The inventory data from SCCM can then be exported for analysis.

Step 2:
Rationalize Applications to Cut Migration Costs

Operating system upgrades present a prime opportunity to rationalize the application estate and to address desktop application sprawl. With a clear view of both the deployed and used applications, you can verify the need to continue to support the applications or to consolidate applications to a reduced number of products and versions.

With the Flexera Software continuous application readiness approach, once the application inventory has been imported and catalogued, applications can be classified and sorted by type, so that duplicate versions and multiple vendors within each type can be identified and consolidated. The result is a list of the applications that will actually need to be moved to Windows 7—and significant cost savings for each application that does not need to be migrated (or supported in the future).

Based on Flexera Software engagements, estimates are that for each application removed from a migration project, savings can be between $3000 and $5000.

This application consolidation process then becomes a key element of continuous application readiness. It is undertaken not as a point-in-time activity, but as part of a regularly scheduled, ongoing process.

Step 3:
Assess Compatibility So You Know What to Migrate and/or Virtualize

Typically only 30 – 50% of applications that run on Windows XP will run on Windows 7 without requiring some modification. This makes it all the more important to perform application compatibility testing before upgrading. Doing so, will identify those applications that need to be fixed in order to run on Windows 7 and those with un-fixable compatibility issues that will need to be replaced or updated.

It’s difficult to know which applications will have compatibility issues, and thus which will require remediation to work on Windows 7. A manual approach of installing and testing each application on Windows 7 is extremely time consuming, and also it’s difficult to exhaustively test all features of the application to ensure they work. Many applications may initially appear to work– but over time, as features and functions in the application are used, compatibility issues may arise. This can cause unpredictable application performance and crashes in the production environment.

In addition to assessing application compatibility with Windows 7, organizations that are implementing application virtualization should also check for application suitability for their chosen virtualization technology as not all applications can be converted to run as virtual applications.

The Flexera Software solution provides a highly effective method to quickly identify applications that have compatibility issues, and provides detailed information on the location, and specifics of the issue. The solution is fully automated, able to assess hundreds or thousands of applications and gives a view of the overall application compatibility across the application estate for both 32-bit and 64-bit versions of Windows 7, as well as suitability testing for application virtualization if required.

This is an excerpt. Download the entire pdf: Six Steps to Continuous Application Readiness